||8 months ago|
|app||8 months ago|
|bin||8 months ago|
|config||8 months ago|
|db||8 months ago|
|lib||8 months ago|
|log||8 months ago|
|public||8 months ago|
|storage||8 months ago|
|test||8 months ago|
|tmp||8 months ago|
|vendor||8 months ago|
|.browserslistrc||8 months ago|
|.dockerignore||8 months ago|
|.gitattributes||8 months ago|
|.gitignore||8 months ago|
|.ruby-version||8 months ago|
|Dockerfile||8 months ago|
|Dockerfile.development||8 months ago|
|Gemfile||8 months ago|
|Gemfile.lock||8 months ago|
|LICENSE||8 months ago|
|Procfile||8 months ago|
|README.md||8 months ago|
|Rakefile||8 months ago|
|babel.config.js||8 months ago|
|config.ru||8 months ago|
|docker-compose.yml||8 months ago|
|docker-entrypoint.sh||8 months ago|
|package.json||8 months ago|
|postcss.config.js||8 months ago|
|proc-start||8 months ago|
|yarn.lock||8 months ago|
Sharedlists is a simple rails driven database for managing multiple product lists of various suppliers.
docker-compose run --rm app bundle docker-compose run --rm app rails db:setup
Creating a user
To access sharedlists, you'll need to create a user (and I guess you want admin access).
docker-compose run --rm app rails c > u = User.new(email: 'email@example.com', password: 'secret') > u.admin = true > u.save! > exit
You can create more users within the web interface.
Either fetch the image, or build it:
docker pull sharedlists:latest # or docker build --tag sharedlists:latest --rm .
Then set environment variables
DATABASE_URL and run:
docker run --name sharedlists_web \ -e SECRET_KEY_BASE -e DATABASE_URL -e RAILS_FORCE_SSL=false \ sharedlists:latest
To run cronjobs, start another instance:
docker run --name sharedlists_cron \ -e SECRET_KEY_BASE -e DATABASE_URL \ sharedlists:latest ./proc-start cron
If you want to process incoming mails, add another instance like the previous,
To put this all together, you may want to wrap this in docker-compose. See the foodcoops.net setup for a real-world example.
To use shared suppliers from this sharedlists instance from within Foodsoft, you need
to configure the
config/app_config.yml. Don't forget to grant the Foodsoft database user
SELECT access on sharedlists'
Articles in the database can be updated regularly. There are currently two options to do this automatically.
Some suppliers distribute article lists via FTP. You can use the rake task
sync_ftp_files in order to download and parse those article
lists. First, you need to enable FTP synchronization for a certain supplier by
activating the checkbox Synchronize FTP files. Fill out all corresponding form
fields. In particular, make sure to adjust the file filter (regular
expression) such that it matches the files of interest; non-matching files are
ignored. The two supported file formats and sensible choices for a corresponding
file filter are shown in the following table.
|file format||example file filter|
Some suppliers send a regular email with an article list in the attachment. For this, an
email server needs to be run using the rails task
On production, you may want to run this on localhost on an unprivileged port, with a
proper MTA in front that
does message routing.
To enable this for a certain supplier, tick the checkbox Update articles by email. Then select a file format to use for importing, and the supplier's email address from which the email is sent. If you only want to import mails with a subject that contains a certain text (e.g. Articles in week), fill in the subject field as well.
What email address does the supplier need to send to? Users will find this after initial creating and saving the supplier after Send to.
This needs setting up of the environment variable
MAILER_DOMAIN, on which you receive the
mails. It is allowed to prefix the address, you may want to set the prefix in
This is useful when you're running a mail server in front to route mails.