You can host any public or your private Ruby project at Jelastic using the GIT or SVN version control system. It will be properly deployed to the Jelastic Cloud with all the required submodules and dependencies, exported from your remote repository.
So, to do this, follow the given instruction:
1. Click the Add project button for the application server in your environment.
2. In the Add project dialog box, choose your version control system (Git or SVN) and fill in all required fields:
- for Git
- URL to your project (http, https, git or ftp link)
- Branch of your project
- Deployment type of your environment (Production, Development or Testing)
- for SVN
- URL to your project (http, https or svn link)
- Login and Password of your repository (if this is required)
Deployment type of your environment (Production, Development or Testing)
In case the Git repository you would like to access is private, put a tick to the Use authentication checkbox. You’ll see an additional section expanded, where you can enter your authentication data.
Firstly, choose the Access type you are going to use for connecting to your remote repository (Password or SSH key). Depending on the chosen option, fill in the following fields:
Also, you can configure some additional options:
- Ticking the Check and auto-deploy updates checkbox will enable an automatic periodic re-deployment of your 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 your project’s updates.
- The Checkout now option (ticked by default) is used to indicate whether you’d like to deploy your project just after its addition or to do this later. If this option is disabled, your 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 --hard command. 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 your project, hosted at Jelastic Cloud. 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 you don’t know exactly what you are doing.
Finally, select 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 your app in a new browser tab.
4. If there were any changes made in your source code:
- you can apply them manually when required by selecting the Update from SVN/GIT icon
they will be applied automatically if you have enabled the auto-deploy updates option previously