Deployment

Orbited has two general modes, "Development mode" and "Deployment mode".

Development Mode

In development mode you simply run the orbited daemon directly with the command "orbited" and it looks for the orbited.cfg in a variety of places. Orbited ships with a number of demos and tests to let you check whether Orbited is working and to get a feel for how it works. Once orbited is started you can access the demos and tests by going to http://localhost:8000/static/ (or http://[address]:8000/static/ if you're not running it on localhost) in a browser. If you're not running on localhost, remember to edit the access section of orbited.cfg to allow connections from the address.

Deployment Mode

One of the most popular cross-platform ways to deploy Orbited is with GNU screen. Some Orbited developers have been known to use God.rb. Here's a great tutorial about deploying Orbited as a Windows Service. There are a number of other distribution-specific ways to daemonize a process, including upstart and start-stop-daemon. Look at your distro's documentation to find the best way.

Cross-Subdomain Deployment

We live in a world of firewalls and restrictive proxies. Thus, web applications are generally not deployable anywhere other than port 80. Here are a few ways to deploy cross-subdomain, sharing port 80 among various servers running on the same box:

HAProxy Highly-configurable proxy and node-balancer.

dez_reverse_proxy Extremely minimal proxy.

If you favor a cross-subdomain or cross-port deployment, you MUST include

<script> document.domain = document.domain; </script>

in your html file at the top of your <head>. If you do not, NOTHING WILL WORK.

Ubuntu (upstart)

As root.

Add an upstart script to /etc/event.d . We'll call our script /etc/event.d/orbited . Here are the contents of such a script:

exec /usr/bin/orbited --config=/etc/orbited.cfg
start on startup

This script assumes you've set up your Orbited Configuration at /etc/orbited.cfg This script will also start orbited at startup. http://upstart.ubuntu.com/ has more information about writing upstart scripts.

Now you should be able to do run: start orbited or stop orbited

(to check if its running execute status orbited or initctl list )