RAILS_RELATIVE_URL_ROOT is used only for asset pipeline.
To namespace your rails routes you need to wrap
run MyApp::Application with
map in your config.ru:
map ENV['RAILS_RELATIVE_URL_ROOT'] || "/" do
Locate the section for your github remote in the
.git/config file. It looks like this:
[remote "origin"] fetch = +refs/heads/*:refs/remotes/origin/* url = email@example.com:joyent/node.git
Now add the line
fetch = +refs/pull/*/head:refs/remotes/origin/pr/* to this section. Obviously, change the github url to match your project's URL. It ends up looking like this:
This is a very simple git workflow. It (and variants) is in use by many people. I settled on it after using it very effectively at Athena. GitHub does something similar; Zach Holman mentioned it in this talk.
Update: Woah, thanks for all the attention. Didn't expect this simple rant to get popular.
|var parser = document.createElement('a');|
|parser.href = "http://example.com:3000/pathname/?search=test#hash";|
|parser.protocol; // => "http:"|
|parser.hostname; // => "example.com"|
|parser.port; // => "3000"|
|parser.pathname; // => "/pathname/"|
|parser.search; // => "?search=test"|
|parser.hash; // => "#hash"|
|parser.host; // => "example.com:3000"|
|# You don't need Fog in Ruby or some other library to upload to S3 -- shell works perfectly fine|
|# This is how I upload my new Sol Trader builds (http://soltrader.net)|
|# Based on a modified script from here: http://tmont.com/blargh/2014/1/uploading-to-s3-in-bash|
|S3KEY="my aws key"|
|S3SECRET="my aws secret" # pass these in|
I've been using this technique in most of my Ruby projects lately where Ruby versions are required:
.rbenv-versioncontaining the target Ruby using a definition name defined in ruby-build (example below). These strings are a proper subset of RVM Ruby string names so far...
rvm --create --rvmrc "1.9.3@myapp") and edit the
environment_id=line to fetch the Ruby version from
Today I learned about another Ruby manager, rbfu, where the author is using a similar technique with