Fixes #29281 - Forcefully remove dynflowd.service
The dynflowd.service was removed in Foreman 2.0 by just dropping the.service file which meansthe service keeps running.
add version dependency also to foreman-service
Don't build libsass with native CPU code tuning
Refs #29144 - Use systemd socket activation
This gives reliable service restarts since systemd keeps the socketopen. bundle exec needs to be called with --keep-file-descriptors sincesystemd passes these in. The replacement is changed since the servicenow uses /usr/share/foreman/bin/rails which doesn't need replacing....
Bump version to 2.1-develop
Refs #28068 - Drop old dynflowd service
Now that foreman-dynflow-sidekiq is in place, there's no more need forthe old dynflowd.
Note that the old dynflowd had a sysvinit script but the new one onlyworks with systemd. This is because it uses multiple instances and this...
Refs #28068 - Include dynflow-sidekiq.rb
This file is needed to start dynflow-sidekiq@.service since it'smentioned as a --require path.
Fixes #28068 - foreman dynflow-sidekiq service as default
Bump version to 2.0-develop
add "--no-audit" to npm install
View revisions
Also available in: Atom