If the reply_email_domain configuration is set the messages plugin will use unique Reply-To addresses for every email. They contain enough information to reconstruct the message context and a hash to avoid user forgery and spam. A mail transfer agent must be configured to call the new rake task foodsoft:parse_reply_email for incoming mails. The rake task requires the receipt of the mail in the RECIPIENT variable and the raw message via standard input. An example invocation would look like: rake foodsoft:parse_reply_email RECIPIENT=f.1.1.HASH < test.eml |
||
---|---|---|
app | ||
bin | ||
config | ||
db | ||
doc | ||
lib | ||
plugins | ||
public | ||
script | ||
spec | ||
tmp | ||
vendor | ||
.dockerignore | ||
.gitignore | ||
.travis.yml | ||
.yardopts | ||
CHANGELOG.md | ||
Dockerfile | ||
Gemfile | ||
Gemfile.lock | ||
LICENSE.md | ||
README.md | ||
Rakefile | ||
VERSION | ||
config.ru | ||
docker-compose.yml |
README.md
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, and automate deployment. This section is very much a work in progress.
License
GPL version 3 or later, please see LICENSE for the full text. Some bundled third-party components have other licenses.
Thanks to Icons8 for letting us use their icons.