Allow finer control over the specification of the
time after shift start where signup is still allowed.
The new config field is multiplied by the shift duration,
and the result added to the start time to determine the
time when signup is closed.
The existing signup_post_minutes is just added to the time
calculated by this new feature.
The feature is useful when the signup should be allowed
not just a few minutes after shift start but for a larger part
of the shift (like for half of the shift).
With the previous option it would not make sense to allow a late signup
longer than the shortest shift of the event.
This is a follow-up to a50dd9cae0
Signed-off-by: Michael Weimann <mail@michael-weimann.eu>
migrate buttons and badges
Signed-off-by: Michael Weimann <mail@michael-weimann.eu>
upgrade bootstrap, fix devtool
remove postcss-preset-env
remove npm-run-all
add theme info to design
add theme configs for 2-15
make all themes compile
fix node env in script
refactor theme config
make all themes basically working
fix sass 3rd party warnings
replace slash div by math.div
* correct the yaml synctax for the docker file
* create an extra env file for the optional config stuff
* modify the default config to respect the set env vars
Signed-off-by: Christian Heusel <christian@heusel.eu>
We now have `signup_advance_hours` in the configuration that
only allows signup for shifts so many hours in the future.
A notice is displayed in the shift view for shifts in the
far future, together with an info notice on when signup for
that shift will be possible.
In addition, we now have a new shift state `NOT_YET` for this
purpose so we do not have to abuse `SHIFT_ENDED` anymore for
`signup_requires_arrival` as well.
msquare