Add a link to the full configuration

Remove optional configuration
Add post-install.txt
This commit is contained in:
j.guyon
2018-02-21 12:10:59 +01:00
parent 6f9b01aa71
commit 6201b89685
2 changed files with 13 additions and 19 deletions
@@ -1,23 +1,11 @@
# See full configuration at
# https://github.com/J-Mose/CommandSchedulerBundle/blob/master/Resources/doc/index.md#4---available-configuration
jmose_command_scheduler:
# Default directory where scheduler will write output files
# This default value assume that php bin/console is launched from project's root and that the directory is writable
# if log_path is set to false, logging to files is disabled at all
# Scheduler will write output files here. set false to disable it.
log_path: "%kernel.logs_dir%"
# This default value disables timeout checking (see monitoring), set to a numeric value (seconds) to enable it
lock_timeout: false
# receivers for reporting mails
monitor_mail: []
# set a custom subject for monitor mails (first placeholder will be replaced by the hostname, second by the date)
monitor_mail_subject: cronjob monitoring %s, %s
# to send "everything's all right" emails to receivers for reporting mails set this value to "true" (see monitoring)
send_ok: false
# Namespaces listed here won't be listed in the list
# Add namespace you don't want to see its Command in the scheduler.
excluded_command_namespaces:
- _global
- scheduler
@@ -29,6 +17,3 @@ jmose_command_scheduler:
- router
- doctrine
- debug
# Doctrine manager
doctrine_manager: default
@@ -0,0 +1,9 @@
<bg=blue;fg=white> </>
<bg=blue;fg=white> What's next for JMoseCommandSchedulerBundle ? </>
<bg=blue;fg=white> </>
* <fg=blue>Configure</> your application:
1. Secure your route by adding <comment>- { path: ^/command-scheduler, role: ROLE_ADMIN }</> in your security config.
2. Set the single-entry point in crontab : <comment>* * * * * php /your_app/bin/console scheduler:execute</>
* <fg=blue>Schedule</> your commands at <comment>http://your-app/command-scheduler/list</>