A HTTP proxy that lets you map subdomains to git branches for site testing
The developer of this repository has not created any items for sale yet. Need a bug fixed? Help with integration? A different license? Create a request here:
Map subdomains to git branches for switching live codebases on the fly. It's a Rack application that acts as a HTTP proxy between you and your web application for rapid testing.
First, you will need to install the gem:
gem install divergence
Then, since divergence is a rackup application, you will need to initialize it somewhere by running:
This copies all of the necessary files into the current folder for you.
You have to do this manually for now. Hopefully in the future, Divergence will be able to automatically handle the DNS setup. All you need to do is create an A record with a wildcard subdomain that points to your testing server IP.
All configuration happens in
config/config.rb. You must set the git repository root and the application root before using divergence.
You will probably want divergence to take over port 80 on your testing server, so you may have to update the forwarding host/port. Note, this is the address where your actual web application can be reached.
A sample config could look like this:
Divergence::Application.configure do |config| config.git_path = "/path/to/git_root" config.app_path = "/path/to/app_root" config.cache_path = "/path/to/cache_root"
config.forward_host = 'localhost' config.forward_port = 80
config.callbacks :after_swap do restart_passenger end
config.callbacks :after_cache, :after_webhook do bundle_install :path => "vendor/bundle" end
config.callbacks :on_branch_discover do |subdomain| case subdomain when "release-1" "test_branch" when "release-2" "other_branch" end end end
Divergence lets you hook into various callbacks throughout the entire process. These are defined in
config/callbacks.rb. Most callbacks automatically change the current working directory for you in order to make modifications as simple as possible.
The available callbacks are:
There are also some built-in helper methods that are available inside callbacks. They are:
You can automatically keep the currently active branch up to date by using a Github service hook. In your repository on Github, go to Admin -> Service Hooks -> WebHook URLs. Add the url:
Now, whenever you push code to your repository, divergence will automatically know and will update accordingly.
To start divergence, simply run in the divergence directory you initialized:
This will start up divergence on port 9292 by default. If you'd like divergence to run on a different port, you can specify that as well:
divergence start --port=88
There is also a
--devflag that will run divergence in the foreground instead of daemonizing it.
On many systems, running on port 80 requires special permissions. If you try starting divergence, but get the error
TCPServer Error: Permission denied - bind(2), then you will need to run divergence with sudo (or as root). If you use RVM to manage multiple Ruby versions, then you can use
Make sure, if you're using Git over SSH, that you have your repository's host added to your known hosts file for the root user.
Divergence currently does not support HTTPS on its own; however, you can still use HTTPS in combination with a load balancer if you enable SSL termination.
Git supports a much wider range of characters for branch names than URLs support. To get around this limitation, simply replace any invalid URL character with a
-and Divergence will find the branch you're looking for automatically.
git checkout -b my-new-feature)
git commit -am 'Add some feature')
git push origin my-new-feature)
Licensed under the Apache 2.0 License. See LICENSE for details.