Web-based software to manage a non-profit food coop (product catalog, ordering, accounting, job scheduling).
Web-based software to manage a non-profit food coop (product catalog, ordering, accounting, job scheduling).
A food cooperative is a group of people that buy food from suppliers of their own choosing. A collective do-it-yourself supermarket. Members order their products online and collect them on a specified day. And all put in a bit of work to make that possible. Foodsoft facilitates the process.
If you’re a food coop considering to use foodsoft, please have a look at the wiki page for foodcoops. When you’d like to experiment with or develop foodsoft, you can read how to set it up on your own computer.
More information about using this software and contributing can be found on the wiki.
If you’d like to see what is currently bring prioritised for development, check our roadmap. If you’d like to influence the roadmap, please join our monthly community call. As of March 2023, Foodsoft has limited development capacity but we are trying to build this up once more. For now, we try to prioritise what we work on, in order to focus our efforts. If your proposed changes are waiting for some time without review, please join the community call to discuss.
Foodsoft development needs your help! If you want to hack/triage/organise to improve the software, please consider joining our monthly community calls which are announced on this forum thread. In these calls, we check in with each other, discuss what to prioritise and try to make progress with development and community issues together.
Get foodsoft running locally,
then visit our Developing Guidelines
page on the wiki.
Get a foodsoft dev-environment running in the browser with Gitpod
Follow these instructions to complete setup from within the Gitpod workspace.
Setup foodsoft to run in production, or join an existing
hosting platform.
Foodsoft is licensed under the AGPL
license (version 3 or later). Practically this means that you are free to use,
adapt and redistribute the software, as long as you publish any changes you
make to the code.
For private use, there are no restrictions, but if you give others access to
Foodsoft (like running it open to the internet), you must also make your
changes available under the same license. This can be as easy as
forking the project on Github and
pushing your changes. You are not required to integrate your changes back into
the main Foodsoft version (but if you’re up for it that would be very welcome).
To make it a little easier, configuration files are exempt, so you can just
install and configure Foodsoft without having to publish your changes. These
files are marked as public domain in the file header.
If you have any remaining questions, please
open an issue or open a new
topic at the forum.
Please see LICENSE for the full and authoritative text. Some
bundled third-party components have other licenses.
Thanks to Icons8 for letting us use their icons.