a3defc5463
Custom fields of an ordergroup can set financial_transaction_source to true, to act as an source for a new collection of FinacialTransaction. A typical usecase would be a variable membership fee, which will be stored in a custom field on the ordergroup. When a new membership period begins a collection with all membership fees can be created with one click. |
||
|---|---|---|
| app | ||
| bin | ||
| config | ||
| db | ||
| doc | ||
| lib | ||
| plugins | ||
| public | ||
| script | ||
| spec | ||
| tmp | ||
| vendor | ||
| .dockerignore | ||
| .gitignore | ||
| .ruby-version | ||
| .travis.yml | ||
| .yardopts | ||
| CHANGELOG.md | ||
| config.ru | ||
| crowdin.yml | ||
| docker-compose-dev.yml | ||
| docker-entrypoint.sh | ||
| Dockerfile | ||
| Dockerfile-dev | ||
| Gemfile | ||
| Gemfile.lock | ||
| LICENSE.md | ||
| proc-start | ||
| Procfile | ||
| Rakefile | ||
| README.md | ||
| VERSION | ||
Foodsoft
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.
Developing
Get foodsoft running locally, then visit our Developing Guidelines page on the wiki.
Deploying
Setup foodsoft to run in production, or join an existing hosting platform.
License
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 contact the mailing list.
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.