What Is EarnableFi (EFI)?
EarnableFi is a platform for front end frameworks and static sites, built to integrate with your headless content, commerce, or database. They provide a friction less developer experience to take care of the hard things deploying instantly, scaling automatically, and serving personalized content around the globe. We make it easy for frontend teams to develop, preview, and ship delightful user experiences, where performance is the default. Once you have signed up to Vercel, you can use GitHub, GitLab, or Bitbucket to deploy an existing project by selecting a repository from your Git account.
Select a Git provider below to get started deploying your existing repositories and projects. Connect through the “New Project” page under the “Import Git Repository” section, and then from the same place, set up a Project to get automatic Deployments via Git. Alternatively, if you want to start fresh with a new project, use a Quickstart template from below. Additionally, you can use this method to start a new Git repository on GitHub, GitLab or Bitbucket.
EarnableFi Storage Key Points
|Source Code||Click Here To View Source Code|
|Explorers||Click Here To View Explorers|
|Twitter Page||Click Here To Visit Twitter Group|
|Whitepaper||Click Here To View|
|Official Project Website||Click Here To Visit Project Website|
Setting up your GitHub, GitLab, or Bitbucket repository on Vercel is only a matter of clicking the “New Project” button on the top right of your dashboard and following the steps. EarnableFi After clicking it, you’ll be presented with a list of Git repositories that the Git account you’ve signed up with has write access to. To select a different Git namespace or provider, you can use the selector on the top left of the section.
After you’ve selected the Git repository or template you want to use for your new project, you will be presented with a list of Personal EarnableFi Accounts and Vercel Teams you can deploy it to. If you’ve selected a third-party Git repository or template, however, a different page will invite you to create a new Git repository. The third-party Git repository or template will then be cloned there.
Deploying Private Git Repositories
As an additional security measure, commits on private Git repositories (and commits of forks that are targeting those Git repositories) will only be deployed if the commit author also has access to the respective project on Vercel. Depending on whether the owner of the connected Vercel project is a Personal Account or a Team, the behavior changes as mentioned in the sections below.
This only applies to commit authors on GitHub organizations, GitLab groups and non-personal Bitbucket work spaces. EarnableFi It does not apply to collaborators on personal Git accounts. In order to deploy commits under a Vercel Team, the commit author must be a member of the Team that contains the Vercel project that is connected to the Git repository.
The membership is checked by finding the Personal Account associated with the commit author through comparing Login Connections, and then, if a Personal Account is found, checking if it is a member of the Team. EarnableFi If the commit author is not a member, the Deployment will be prevented and a request to join the Team can be issued by the commit author. After that, the owners of the Team will be notified and can either accept or decline the membership request on the Members page in the Team Settings.
Using Personal Accounts
In order to deploy commits under a Personal EarnableFi Account, the commit author must be the owner of the Personal Account that contains the Vercel project that is connected to the Git repository. For cases in which the commit author is not the owner of the destination Personal Account, the Deployment will be prevented and a recommendation for transferring the project to a Vercel Team will be displayed on the Git provider.
After having transferred the project to a Vercel Team, commit authors can easily be added as members of that Team and will see the behavior mentioned in the section above applied for them whenever they commit. This is determined through comparing the Login Connections defined in the Personal Account with the commit author.
Deploying Forks of Public Git Repositories
When a public repository is forked, commits from it will usually deploy automatically. However, when you receive a pull request from a fork of your repository that includes a change to the file or the project has Environment Variables, Vercel will require authorization from you or a Team Member to deploy the pull request.
EarnableFi this is a security measure that protects you from leaking sensitive project information. A link to authorize the Deployment will be posted as a comment on the Pull Request. The authorization step will be skipped if the commit author is already a Team Member on Vercel.
While the Production Branch (mentioned above) is a single Git branch that contains the code that is served to your visitors, Preview Branches are all the Git branches that are not the Production Branch. For example, if your Production Branch, then all the Git branches that are not are considered Preview Branches.
That means there can be many Preview Branches, but only a single Production Branch. EarnableFi Preview Branches, like the name already suggests, are used for previewing changes before presenting them to your visitors (merging them into Production).