Originally created by @brunofacca on GitHub (Feb 3, 2017).
Thanks fo the great gem!
The documentation only explains how to start crono from the command line. I'd like to have it autostarted with a Rails project instead of creating a Linux init script or something. Can it start automatically when Rails is started? Do we need to create an initializer? What are the consequences of running as a daemon vs. not running it as a daemon?
Again, thank you.
Originally created by @brunofacca on GitHub (Feb 3, 2017).
Thanks fo the great gem!
The documentation only explains how to start crono from the command line. I'd like to have it autostarted with a Rails project instead of creating a Linux init script or something. Can it start automatically when Rails is started? Do we need to create an initializer? What are the consequences of running as a daemon vs. not running it as a daemon?
Again, thank you.
@plashchynski commented on GitHub (Mar 7, 2017):
Hello @brunofacca
you can start it using [foreman](https://github.com/ddollar/foreman)
With a Procfile like:
web: bundle exec puma -C config/puma.rb
crono: bundle exec crono
then:
`foreman start`
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @brunofacca on GitHub (Feb 3, 2017).
Thanks fo the great gem!
The documentation only explains how to start crono from the command line. I'd like to have it autostarted with a Rails project instead of creating a Linux init script or something. Can it start automatically when Rails is started? Do we need to create an initializer? What are the consequences of running as a daemon vs. not running it as a daemon?
Again, thank you.
@plashchynski commented on GitHub (Mar 7, 2017):
Hello @brunofacca
you can start it using foreman
With a Procfile like:
then:
foreman start@brunofacca commented on GitHub (Mar 8, 2017):
Thank you @plashchynski