After bitching and complaining, I've put my almost-complete-capistrano-tasks on GitHub to start maintaining.
I created the tasks to help setup my VPS in as little time possible since I really don't want to be doing sysadmin stuff anymore. Been there, done that a few years ago. I'm done with it. So I created a few capistrano tasks that will take a bare-bones vanilla VPS and set it up to host rail(s) applications.
Originally, I had nginx install and setup as part of it, but ended up deleting it at the last moment before putting it on GitHub. I don't want to deal with Nginx if I don't have to since I really love Apache -- especially with Passenger (mod_rails) now!
So that's the first order of business is to add the http-server setup ASAP! Other than that, just some overall cleaning up will be done and documentation since the tasks were hacked out in as little time as possible to setup my server.
Enjoy and please contribute ;) I'll be making it available as a gem ASAP too since it is usable in its current state, just not pretty -- yet.
http://github.com/cgrusden/capistrano-server-assembly/tree/master
Having an issue pushing to GitHub or other git repos?
After going through all the correct setup steps to put your open-source project on RubyForge or GitHub you try to do a git-push and then receive errors when trying to git-push.
So the question is, did you add your public key (if you created a new one for git'ing) to your authentication agent via ssh-add?
$ ssh-add ~/.ssh/my_public_key
Done.
ssh-add documentation here
So the question is, did you add your public key (if you created a new one for git'ing) to your authentication agent via ssh-add?
$ ssh-add ~/.ssh/my_public_key
Done.
ssh-add documentation here
Removing unwanted new files from your SVN working copy
So you have a project in SVN. You create a few new files and decided you just want to delete them via the commandline real quick.
projectroot$ svn st | grep '?' | awk '{print $2}' | xargs rm
projectroot$ svn st | grep '?' | awk '{print $2}' | xargs rm
mod_rails : RAILS_ENV fun
When hosting multiple Rails applications using the new mod_rails for Apache, all of the RAILS_ENV variables will default to 'production'.
The way you can change what environment your Rails applications run in is by adding/modifying the following line in your httpd.conf:
RailsEnv staging
This is really the only inconvenience that I've found so far with mod_rails. Surely someone will allow for the RailsEnv variable to be located inside a VirtualHost block.
The way you can change what environment your Rails applications run in is by adding/modifying the following line in your httpd.conf:
RailsEnv staging
This is really the only inconvenience that I've found so far with mod_rails. Surely someone will allow for the RailsEnv variable to be located inside a VirtualHost block.
Apache+mod_rails(passenger)
Wow, this is HOT.
I have been using a shared VPS for hosting my rails/PHP applications and using NGinx to do so. Yesterday I told myself I wanted a better solution if there was one. So on my VPS, I installed Apache and mod_rails (Passenger) in a matter of minutes and had all my sites back up with ease.
I'm glad to be back on Apache, even though most of the configuration and performance tuning I've long become rusty on since alot of new features have come out for Apache.
The fun will continue.
I have been using a shared VPS for hosting my rails/PHP applications and using NGinx to do so. Yesterday I told myself I wanted a better solution if there was one. So on my VPS, I installed Apache and mod_rails (Passenger) in a matter of minutes and had all my sites back up with ease.
I'm glad to be back on Apache, even though most of the configuration and performance tuning I've long become rusty on since alot of new features have come out for Apache.
The fun will continue.
Subscribe to:
Posts (Atom)
