There is currently no top-level selector for views that is conference-specific,
so all conferences on one OSEM instance end up sharing all the same CSS.
In order to allow individual conferences to have unique CSS, a class for the
current conference is applied to the <body> tag, and an scss template provided with
an example of conference-specific CSS.
The current codebase will end in a 500 APPLICATION ERROR if Conference#short_title isn't found... this should be a 404 NOT FOUND INSTEAD, which will be handled if we raise ActiveRecord::RecordNotFound.
Supercedes https://github.com/openSUSE/osem/pull/2031 .
Note:
* "Questions" modals have been dropped from this view; questions are no
longer asked on registration, since Surveys(PR#1100) were added.
It constantly fails with "Mysql2::Error: This connection is in use by...".
Might be because of database cleaner? But until we can get this stable,
rip it out again.
Replaced by a matrix based on test type
- 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
We don't have a Vagrant setup for centos, why would we need a centos
bootstrap?
Also use the rake taks setup:bootstrap to configure the app so we only
have one place where this is done.
Copying this to .env.production used to enable all kinds of things with example
data. Now you can copy it and OSEM will use it's defaults until you explicitely
change them here.
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.
