This might seem a bit stupid, but I got bitten by this today - I was under the
impression the command is required to make the changes visible in the running
app (despite the section above saying it isn't). Hopefully this helps any
potential contributor to get their mind sorted better than mine.
- 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
Introduces a section about the docker-compose development environment.
I have also tried to shorten the guide, by moving some things to the wiki,
so it's not too overwhelming for new contributors.
* Write a paragraph that informs contributors about the openID test
accounts that are available and provide instructions on how to
enable them in development (#1315) in CONTRIBUTING.md
* Add missing environment variable for openID logins via openSUSE
(OSEM_SUSE_KEY, OSEM_SUSE_SECRET) in dotenv.example
