-
Notifications
You must be signed in to change notification settings - Fork 283
Installation
We have many different ways to install OneBody, based on your expertise/needs. Choose your own path:
| Method | Difficulty | Time Needed | Advantage |
|---|---|---|---|
| [[Debian/Ubuntu Package | Install Debian/Ubuntu Package]] EXPERIMENTAL | Easy | ~ 10mins |
| DigitalOcean (automated) | Easy | ~ 10mins | Just two clicks |
| [[Amazon EC2 (AMI) | Amazon AMI]] | Easy | ~ 5mins |
| [[OVF (VirtualBox/VMWare) | Virtual Appliance]] | Easy | ~ 5mins* |
| [[Manual | Manual Installation]] | Advanced | ~ 1hr |
| [[Capistrano | Deployment with Capistrano]] | Advanced | ~ 20mins |
*not counting the time to download the file
If you're not sure which way to go, or if you have any trouble, join the Slack chat or post to the Google Group and ask for help!
OneBody needs to be installed on a server with at least 1 GB of memory and enough free disk space to accommodate your community's needs. We recommend at least 1 GB of disk space per 100 users, but your needs may be different. (The user database is usually quite small, but documents and photos can take up a lot of disk space, so plan accordingly.)
Unfortunately, OneBody cannot be installed on "shared hosting" due to the very specific software requirements. You'll need a dedicated server or Virtual Private Server (VPS) to get everything running. We recommend DigitalOcean, Amazon EC2, or your own in-house hardware.
Based on how you chose to install OneBody, there is a different method for how you should go about upgrading your installation.
| Installation Method | How to Upgrade |
|---|---|
| DigitalOcean, Amazon EC2, OVF, Manual | instructions for manually upgrading |
| Capistrano |
cap deploy :-) |
Alternatively, if you'd rather install OneBody from a fresh download (using any of the techniques at the top of this page), you can then Upgrade by Copying Data from your old install to the new one.