![]() ![]() One example of this would be the FCKEditor folder that contains all the necessary code to generate a rich text editor. This is a folder that shares content across releases. Shared foldersĪdvanced users might wish to use the Shared folder feature of Capistrano. I can easily and quickly roll back if there are any problems. I simply type one line on the command line and git does the heavy lifting for me. I no longer have to track which files have changed and manually transfer them using FTP when a client is ready to deploy. Since moving to Capistrano for deployment I’ve saved a massive amount of time. The latest greatest version of your website is published. Updates the symlink in current to the new release.Copies the release to a new release in /releases.Checks this against the remote cache and updates if necessary.Fetches the latest commit from your git repository.And deployĭeploying an ExpressionEngine website is now just a case of cap deploy Set the relevant paths and setting, save the file and you are done. Set :deploy_to, "/var/www/vhosts/#"ĭesc "This is here to overide the original :restart" Set :repository, "ssh://:/var/git/foo.git" We need to edit the /config/deploy.rb file. Great - so now we’ve got a Capified folder structure and the source code in Git. You can find more information on setting up a bare git repo here. (I assuming you have a bare git repo to push your commit to somewhere). We are going to add the whole thing to git. So now we’ve got a folder structure and our source code in the right folders. The latter is the one we are interested in - we’ll come back to that when we configure deployment. This creates two files Capfile and config/deploy.rb. Then when you are in the directory run the following command: capify. Optionally you can add a README file for other developers to get quick information on the project. So now my site folder structure looks like this:. Then we also need to create a folder called config. For Capistrano to be able to do the magic we need to move all public files to a folder called public. ![]() For my development I normally have all my ExpressionEngine files in one folder. In order to prepare ExpressionEngine for use with Capistrano we need to shift our folder structure around a tiny bit. SSH shared keys are set up between local and remote keys.Capistrano is installed on your local machine.Ruby is installed on your local machine.Secondly I’m assuming that you are comfortable working with the shell (in this case bash). This article does not support Windows although you might be able to get it working using Putty. Firstly that you are working on a POSIX compliant operating system. I’m going to make a few assumptions in this article. Last updated Saturday, Deploying ExpressionEngine with Git and Capistrano A tutorial on how to publish an ExpressionEngine website using Git and Capistrano.Įstimated reading time: 4 minutes Table of contents Deploying ExpressionEngine with Git and Capistrano | George Ornbo ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |