How to use Git to deploy to your site

Git is already available on your site. There is no setting to switch on. Your primary site user can push over Git as soon as the site is created — just open the Git tab to get your repository URL and credentials.

Steps

  1. Log in to the Everleap Control Panel at cp.everleap.com.
  2. From the top menu click Shared Sites.
  3. On the Shared Cloud Sites Overview page, click Manage next to the applicable site.
Site Overview page showing the Site Tools panel with FTP, Web Deploy and Git tabs
  1. On the Site Overview page, find the Site Tools panel and click the Git tab.
  2. The Git page opens and shows everything you need to connect.
The Git page showing Git Information with the repository URL, username, password note and Manage Additional Users link

Your Git Details

FieldValue
Repository URLhttps://<site-id>.scm.el-alt.com/<site-id>.git
Username<site-id>\<your customer ID>
PasswordSame as your FTP password

Each site on a Multi-Site plan has its own site ID, so each site has its own repository URL and username. The exact values for your site are shown on the Git page.

Setting Up Your Local Repository

After installing Git, run these commands to initialise your local repository:

cd /c/path/to/application
git init
git add .
git commit -m "initial commit"

Pushing Your Application to Everleap

Add the Everleap repository as a remote and push. Replace the URL with the Repository URL shown on your Git page.

git remote add mywebsite https://1234-99.scm.el-alt.com/1234-99.git
git push mywebsite master

You will be prompted for the username and password shown on the Git page.

Giving Other People Git Access

Click Manage Additional Users on the Git page to grant Git deployment rights to additional users. Permissions are set per site and per protocol — see the related article below for the full procedure.

Notes

  • Your primary site user already has permission to deploy with Git; no extra setup is required for that account.
  • Git credentials are the same as your FTP credentials and are separate from your Control Panel login.
  • Additional users do not get Control Panel access — only the deployment protocols you grant them.

Related Articles