I'm slowly getting back, hope you all had a good time during
holidays. If you're still away, enjoy!
In the meantime, I've worked on getting sharedlists ready to
support features used in foodcoop-adam. If you'd like to review,
feel free at foodcoops/sharedlists
And I've put together what I think would be a picture of a full
setup. It looks like we're going for a virtual server in the cloud
running nothing but SSHd and Docker. Then there are Docker
instances for Foodsoft (fsmain) and Sharedlists (sharedlists).
Supporting services are a web front-end (for ssl and redirecting
to the right app), database, redis and a mail server (to route
emails, and perhaps also to send them).
In the future, there will also be two Docker instances of the
foodcoop-adam fork of Foodsoft (with different sets of plugins),
for customizations several Dutch foodcoops are using (which I am
in the slow process if migration to the foodcoops version of
Next to that, we use external services like Github (code,
configuration and documentation), we'll need a DNS provider, and
currently have Nabble for communication.
What do you think?
p.s. I just realized that I forgot Travis CI, for testing,
perhaps also for parts of deployment? Something to add later. I
think this file could end up in a foodcoops-global repository, or
so, containing the configuration files necessary for this
infrastructure. It might as well contain the documentation.
Ideally, then, changes to the repository could be auto-deployed.