Deployment notes

Jan edited this page Jan 31, 2018 · 9 revisions

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.

Docker

This is currently the recommended deployment method. Foodsoft's SETUP_DOCKER document explains the details. You can also learn from the foodcoops.net setup that is currently being setup (work in progress, though).

Shared and dedicated hosting

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)

There also an ansible role if you need automated setup.

Turnkey Linux Foodsoft appliance

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.

On sending mail

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). Read more here.

Howto deploy the Foodsoft on a german shared webhosting service

You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Press h to open a hovercard with more details.