-
Notifications
You must be signed in to change notification settings - Fork 146
Deployment notes
As the production docs mention, documentation is not very abundant. This wiki page gives some pointers.
If you'd like to run Foodsoft in production, you most likely want to start a food cooperative or are already part of one. You've seen Foodsoft, and are ready to start using it. Read about the options. This page is about running Foodsoft yourself.
Some different options are discussed here, then there are some general remarks to think about.
This is currently the recommended deployment method. Foodsoft's SETUP_PRODUCTION document explains the details. You can also learn from the foodcoops.net setup and preliminary vokomokum setup.
We maintain an Ansible role if you need automated setup. You can use this role for single coop and multi coop installations.
There is a recipe available on git.coopcloud.tech/coop-cloud/foodsoft. More info on coopcloud.tech.
Foodsoft is also being run on a webserver without a virtual machine. This could be on a shared host (like Dreamhost, like this), or a dedicated physical or virtual server. A good option is Passenger with RVM (see, for example, foodcoop-adam's install guide)
To run Foodsoft on a virtual machine, you can use the Turnkey Linux Foodsoft appliance (install help). This is relatively easy, but currently only provides an older version of Foodsoft.
Foodsoft needs to send emails (at the very least, to reset passwords). With all the spam-combat-techniques, it can be challenging to run your own internet-facing mail server, it may be easier to use your internet access/service provider's (or Google, if you use GMail).