osem-fcy/bin/osem-init.sh

#!/bin/bash
# Setup the app if it isn't already setup
bundle exec rake db:bootstrap
# Start the app
foreman start -p 3000
Introduces openSUSE based docker-compose environment 2018-09-05 22:49:57 +02:00			`#!/bin/bash`
Docker cleanups - Put docker-compose.yml into version control, no need to make this an example file and complicate things. - Start the docker dev-env osem on port 3000. Just as our documentation says and how we do it in vagrant. - hardcode CONTAINER_USERID so you don't have to have an docker-compose.override.yml if your UID is 1000. - Rename web service/container to osem for clarity in the logs - Keep assets also in a volume in production - warn a bit more prominently about docker-compose.override.yml 2018-09-12 22:38:07 +02:00			`# Setup the app if it isn't already setup`
Put database.yml into the code base It works by default, we have a mechanism to configure it (dotenv.example) and we want to be a 12factor app, right? Let's do this... 2018-09-18 22:58:34 +02:00			`bundle exec rake db:bootstrap`
Docker cleanups - Put docker-compose.yml into version control, no need to make this an example file and complicate things. - Start the docker dev-env osem on port 3000. Just as our documentation says and how we do it in vagrant. - hardcode CONTAINER_USERID so you don't have to have an docker-compose.override.yml if your UID is 1000. - Rename web service/container to osem for clarity in the logs - Keep assets also in a volume in production - warn a bit more prominently about docker-compose.override.yml 2018-09-12 22:38:07 +02:00			`# Start the app`
			`foreman start -p 3000`