Simplifying FAST Deployments on Your Staging Server
We’re currently in the process of improving our build system and overall deployment process for customers. In saying that we’re publishing two modified files for use ONLY ON YOUR STAGING SERVER. We realize that deployments have been a hassle and require some “tribal knowledge” about our systems. With that being said, please check our blog frequently as we’ll be updating you on our progress. The improved process means that you’ll have direct access to your build system as well as a much easier way to get deployments out to your staging and production servers.
These two files that will make staging deployments a breeze (we hope). You’ll need to place these files in your Rails project, but we don’t recommend checking them into your FAST code repository. Save them locally and you can always come back here to download them. They will become obsolete in the coming weeks and we’ll provide you with proper deployment files for both your staging and production servers. The first file is a modified deploy.rb file that you need to place in your Rails config directory. Simply rename your existing deploy.rb and place the following in its place. Make sure to remove the .txt extension.
Modified Rails Deployment File
Inside this file you’ll need to modify lines 1 and 2 with your appropriate SVN login credentials. You’ll also need to modify lines 20-22 with your appropriate FAST subdomain and SVN branch name. If you don’t know what these are then you should contact our support team ((JavaScript must be enabled to view this email address)). The other file you’ll need to replace is a modified database_procs.rb file that also lives in your Rails config directory. Just download, remove the .txt extension, and there’s no need to modify anything.
Modified Database Procedures File
With these two files in place, and the changes to deploy.rb mentioned above, you’ll be able to issue the following command to deploy to your staging sever:
cap staging deploy
You’ll be prompted for your FAST server password, which you can find in your welcome email. That should do the trick and please feel free to post in the dev forums or contact support if you have any problems.