Home

This repository is for the configuration of the future foodcoops.net infrastructure. The global operations team manages this to keep the systems running smoothly. Of course the core software would be Foodsoft with sharedlists, but other software may become available in the future as well.

Getting ready for launch

Our first aim would be to get everything ready for launch, to replace the existing app.foodcoops.net which is ending. Relevant tasks are and can be put in this milestone.

Communication

Happens through the foodsoft-global-ops mailing list and this repository's issues and wiki (which you're reading now).

Setup

This is very much a work in progress. See this mail thread.

• wwwfront provides https and redirects to different containers based on url (which foodsoft version or sharedlists)
• db stores the data
  • one username/password for each container
• redis is used by different notifiers
  • remember to use different queue names for different instances
  • could also use one instance per foodsoft instance
• mta handles mail
  • directs received mail to one of the foodsoft or sharedlists instances (based on email address / domain name)
  • would make sense to also handle sending mail (the green line in the diagram is now for receiving mail)
  • may need to adapt foodsoft + sharedlists to handle adding an email address prefix done
• fsmain
  • main foodsoft instance running foodcoops/foodsoft fork
  • (in the future this will also run a mail server for handling replies, this is currently in beta by @paroga)
• sharedlists
  • single sharedlists instance
  • cron for bnn ftp sync
  • mail server for updating of articles for Dutch suppliers