die regionale gartenkooperative

We implement a "specific" web solution to organize all the work on a farm as a group of about ~400 persons.

Following instructions work for MacOS.

This should do it for your local setup:

    export ORTOLOCO_DATABASE_ENGINE=django.db.backends.sqlite3
    export ORTOLOCO_DATABASE_NAME=db.sqlite

    export ORTOLOCO_AWS_KEY_ID=
    export ORTOLOCO_AWS_KEY=
    export ORTOLOCO_AWS_BUCKET_NAME=

    # Optional, nur wenn emails von lokal gesendet werden sollen:
    export ORTOLOCO_EMAIL_HOST=smtp.gmail.com
    export ORTOLOCO_EMAIL_PASSWORD=YOUR_GMAIL_APP_PASSWORD
    export ORTOLOCO_EMAIL_USER=YOUR_EMAIL@gmail.com
    export ORTOLOCO_EMAIL_WHITELISTED_1=A_SECOND_WHITELISTED_EMAIL@gmail.com # optional

In case the gmail credentials refuse to work, it might be that Google is blocking the logging because is it comming from an unknown location. This can easily be the case if using e.g. c9.io. Try the solutions listed in this Gmail Help document. The first three of them are listed here for reference:

• If you've turned on 2-Step Verification for your account, you might need to enter an App password.
• Sign in to your account from the web version of Gmail at https://mail.google.com. Afterwards try accessing your messages in your mail app again.
• If you're still having problems, visit http://www.google.com/accounts/DisplayUnlockCaptcha and sign in with your Gmail username and password. If necessary, enter the letters in the distorted picture.

cd ortoloco

sudo easy_install pip
sudo pip install virtualenv
virtualenv --distribute venv
source ./venv/bin/activate
pip install --upgrade -r requirements.txt

NOTE: All requirements are not easily installable on Mac OS X. If you encounter some issues (i.e. EnvironmentError: mysql_config not found or pg_config executable not found) you might run instead:

pip install --upgrade -r requirements-mac.txt

wich removes following packages from the requirements:

MySQL-python==1.2.5
django-toolbelt==0.0.1
psycopg2==2.5.1

NOTE: You might be able to install "brew install mysql" and "brew install postgresql" and "brew install pg" instead (before)

You can (probably) be guided through the steps above with make createdb. If that doesn't work, read on...

In ortoloco/settings.py, comment out all non-django apps (my_ortoloco,static_ortoloco, south, photologue). Then run following command:

./manage.py syncdb

Here you will be asked to create a superuser for the local dev app. Reply yes and create a test superuser named e.g. admin with the (indeed very secure) password admin. The output should look similar to the following:

(...)

Creating tables ...
Creating table django_cron_job
Creating table django_cron_cron
Creating table auth_permission
Creating table auth_group_permissions
Creating table auth_group
Creating table auth_user_groups
Creating table auth_user_user_permissions
Creating table auth_user
Creating table django_content_type
Creating table django_session
Creating table django_site
Creating table django_admin_log

You just installed Django's auth system, which means you don't have any superus
ers defined.
Would you like to create one now? (yes/no): yes
Username (leave blank to use 'ubuntu'): admin
Email address: admin@example.org
Password: <admin>
Password (again): <admin>
Superuser created successfully.
Installing custom SQL ...
Installing indexes ...
Installed 0 object(s) from 0 fixture(s)

Reactivate the outcommented apps above and run following commands:

./manage.py syncdb
./manage.py migrate

With make savedb you can easily make a snapshot of the current local database file (if using SQLite), and restore it (i.e. the last db snapshot file) with make restoredb.

You might want to look at the Makefile for more details.

When the database structure changes, you must perform a new migration:

./manage.py schemamigration loco_app --auto
./manage.py migrate loco_app

You might be guided through these steps with make migratedb.

Run following command to launch a server on http://localhost:8000:

./manage.py runserver

You might run this with make, which will additionally open the URL on your browser.

Use following command to create a super user, if not yet available:

./manage.py createsuperuser

Hint: the super user used in the db on slack is name ´super´, password ´super´.

The first time you try to login with the initial admin user you will encouter an error like User has no Loco. To create a Loco for this user, you have to activate a secret 😄 URL in url.py and call it from the browser:

• http://localhost:8000/my/createlocoforsuperuserifnotexist

Afterwards, you might have to logout with following URL:

• http://localhost:8000/logout

./manage.py changepassword admin

First read this: https://github.com/lanyrd/mysql-postgresql-converter

Then import the data into the heroku-db (find the values here: https://postgres.heroku.com/databases/ortoloco-database) psql -U -d -h -f path/to/postgres.sql

You can trigger a DB backup on the web interface of heroku at

• Live: https://postgres.heroku.com/databases/ortoloco-heroku-postgresql-rose#snapshots
• Dev: https://postgres.heroku.com/databases/ortoloco-dev-database#snapshots

Or you can trigger it directly from the command line with

make heroku_create_db_backup_dev
# or for the live app
# make heroku_create_db_backup_live

For reference, this make target executes following commands:

heroku pg:backups --app ortoloco-dev capture

You can read more about it in the heroku doc about Postgres backups.

In the case that a migration must be executed on a Heroku app (live or dev), you can execute following make target, which previously creates a DB backup with the target described above:

make heroku_migrate_db_dev
# or for the live app
# make heroku_migrate_db_live

For reference, this make target executes following commands:

heroku run --app ortoloco-dev python manage.py syncdb
heroku run --app ortoloco-dev python manage.py migrate

You can read more about it in the heroku doc about Django.

To copy the last backup from the production DB (i.e. heroku app ortoloco) into the dev app (i.e. heroku app ortoloco-dev) execute

make heroku_refresh_db_dev

For reference, this make target executes following commands:

SOURCE_APP=ortoloco
TARGET_APP=ortoloco-dev
heroku pg:backups restore $(heroku pg:backups public-url --app $SOURCE_APP) DATABASE_URL --app $TARGET_APP

See: Importing and Exporting Heroku Postgres Databases with PG Backups

To download the last backup from the production DB (i.e. heroku app ortoloco) execute

make heroku_download_last_db_backup

For reference, this make target executes following commands:

HEROKU_APP=ortoloco
HEROKU_LAST_BACKUP_ID=$(heroku pg:backups --app ${HEROKU_APP} | grep Completed | head -1 | sed "s/\(\S\S*\)\s.*/\1/")
HEROKU_LAST_BACKUP_PUBLIC_URL = $(heroku pg:backups public-url --app ${HEROKU_APP} | cat)
curl "${HEROKU_LAST_BACKUP_PUBLIC_URL}" --create-dirs -o git-untracked/.heroku_db_backups/${HEROKU_APP}/$(date +"%Y%m%d%H%M%S")_${HEROKU_LAST_BACKUP_ID}.bak

You can read more about it in the heroku doc about Postgres backups.

Obviously, you need the rights to do this, then:

heroku git:remote -a ortoloco-dev -r heroku-dev
git push heroku-dev master

On live you do this (see heroku doc):

heroku git:remote -a ortoloco -r heroku-live
git push heroku-live live:master

If e.g. the migration 0028 and 0029 are the same, delete the first one and run:

./manage.py migrate my_ortoloco 0028 --fake --delete-ghost-migrations

Or direct on the heroku dev application:

heroku run --app ortoloco-dev python manage.py migrate my_ortoloco 0028 --fake --delete-ghost-migrations

And then run a normal syncdb and migrate.

For further reference: http://stackoverflow.com/a/8875541