How should I Deploy Node.js Project Via GIT SVN

Deploying Node.js Project via GIT/SVN

With Cloudjiffy I can host any public or my private Node.js project at the CloudjiffyCloud using GIT/SVN.

To deploy project from the remote repository, follow the instruction below:

1. Click the Add project button for the application server in my environment.


2. In the Add project dialog box choose the appropriate tab with my version control system (Git or SVN) and fill in all required fields:

  • for Git

    • URL to my project (httphttpsgit or ftp link)
    • Branch of my project

  • for SVN

    • URL to my project (httphttps or svn link)
    • Login and Password of my repository (if this is required)

I can deploy just one Node.js project to my environment, so the Path for my application (i.e. context) will be ROOT by default and can’t be changed.


In case the Git repository I would like to access is private, put a tick to the Use authentication checkbox. I’ll see an additional section expanded, where I can enter my authentication data.

Firstly, choose the Access type which I am going to use for connecting to my remote repository (Password or SSH key). Depending on the chosen option, fill in the following fields:

  • enter my Git account credentials (Login and Password) for the Password access type
  • type my Git account Login and choose the appropriate private SSH key from the Select key drop-down list for the SSH key access type (more details on SSH authorization for GIT see here) 



Also, I can configure some additional options:

  • Ticking the Check and auto-deploy updates checkbox will enable an automatic periodic re-deployment of my project from the repository, which is only performed if the repository contains new code changes. Use the Check every (min) option to define the required frequency of my project’s updates.
  • The Checkout now option (ticked by default) is used to indicate whether I’d like to deploy my project just after its addition or to do this later. If this option is disabled, my repository’s configurations will be saved for a further deployment, which can be initiated by the auto-deploy feature (if it is enabled) or by selecting the Update from GIT button next to the added project.
  • The active by default Auto resolve conflict option represents an analogue of the git reset --hardcommand. It is used to prevent the occurrence of merge conflicts while a further project updates, which can take place if the same file was modified in both remote repository and my project, hosted at CloudjiffyCloud. If such an issue arises, this contradictory file will be updated according to its repository version (which is considered as the correct one), discarding the locally made changes.

    Note: Please DO NOT disable this option if I don’t know exactly what I am doing.

Finally, click Add at the bottom of the frame.

3. That's all! After the deployment process is finished, click the Open in browser button next to the environment in order to display app in a new browser tab.


Was this article helpful?

mood_bad Dislike 0
mood Like 1
visibility Views: 16707