Improving foodsoft! Railsupgrade, BNN Import/Export, Usability stuff https://prototypefund.de/project/weiterentwicklung-von-foodsoft/
Find a file
2023-03-30 15:30:59 +02:00
.github/workflows Add RuboCop 2021-03-02 09:12:19 +01:00
app prepare for plugin import 2023-03-28 17:03:24 +02:00
bin introduce importmaps 2023-02-10 12:24:42 +01:00
config move BigDecimal.new to BigDecimal() 2023-02-17 13:16:28 +01:00
db rails up to 7.0and ruby to 2.7.2 2023-01-17 16:35:04 +01:00
doc replace apivore with rswag 2023-01-17 16:07:54 +01:00
lib/tasks rails up to 7.0and ruby to 2.7.2 2023-01-17 16:35:04 +01:00
plugins add basic functionality of plugin 2023-03-30 15:30:59 +02:00
public apple icons to stop 404s (#130, PR #889) 2022-01-12 17:19:38 +01:00
script Update Crowdin settings 2022-11-14 21:38:52 +01:00
spec rails up to 7.0and ruby to 2.7.2 2023-01-17 16:35:04 +01:00
tmp Ignored tmp, rubymine project files and other stuff. 2011-05-06 19:55:34 +02:00
vendor introduce importmaps 2023-02-10 12:24:42 +01:00
.dockerignore Improve Docker setup (PR #497) 2017-10-01 13:57:36 +02:00
.gitignore Add support for ActiveStorage (PR #852) 2022-01-31 08:44:53 +01:00
.gitpod.yml One-click development environment via Gitpod.io (browser-based VSCode with cloud backend) 2022-05-27 17:18:17 +02:00
.rubocop.yml Add RuboCop 2021-03-02 09:12:19 +01:00
.rubocop_todo.yml replace apivore with rswag 2023-01-17 16:07:54 +01:00
.ruby-version rails up to 7.0and ruby to 2.7.2 2023-01-17 16:35:04 +01:00
.yardopts update documentation generation 2014-06-23 17:51:20 +02:00
CHANGELOG.md Bumped new version: 4.7.1 2020-12-30 11:44:47 +01:00
config.ru Bundle update rubocop and auto correct style issues 2022-05-27 23:10:07 +02:00
crowdin.yml Update Crowdin settings 2022-11-14 21:38:52 +01:00
docker-compose-dev.yml fix docker-compose 2023-02-02 10:14:26 +01:00
docker-entrypoint.sh Add a script to read all databases with a prefix from the database server 2022-05-27 23:10:07 +02:00
Dockerfile improve dockerfile caching 2023-02-09 17:22:38 +01:00
Dockerfile-dev rails up to 7.0and ruby to 2.7.2 2023-01-17 16:35:04 +01:00
Gemfile prepare for plugin import 2023-03-28 17:03:24 +02:00
Gemfile.lock prepare for plugin import 2023-03-28 17:03:24 +02:00
LICENSE.md Switch license to AGPL (fixes #496, PR #513) 2017-11-10 17:02:35 +01:00
proc-start Update doc line 2017-10-27 23:23:46 +02:00
Procfile Use ActiveJob instead of Resque directly 2021-03-08 12:30:58 +01:00
Rakefile Auto correct rubocop style issues 2022-02-20 16:28:54 +01:00
README.md Update link to forum (PR #963) 2022-12-12 15:15:54 +01:00
VERSION continue development after release 2020-12-30 16:53:53 +01:00

Foodsoft

Build Status Coverage Status Docs Status Code Climate Docker Status Documentation

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.

Get a foodsoft dev-environment running in the browser with Gitpod

Open in Gitpod

Follow these instructions to complete setup from within the Gitpod workspace.

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 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.