Merge pull request #286

jmose/command-scheduler-bundle/2.0/config/packages/scheduler.yaml

@@ -0,0 +1,19 @@
+# See full configuration at
+#     https://github.com/J-Mose/CommandSchedulerBundle/blob/master/Resources/doc/index.md#4---available-configuration
+jmose_command_scheduler:
+
+    # Scheduler will write output files here. set false to disable it.
+    log_path: "%kernel.logs_dir%"
+
+    # Add namespace you don't want to see its Command in the scheduler.
+    excluded_command_namespaces:
+        - _global
+        - scheduler
+        - server
+        - container
+        - config
+        - generate
+        - init
+        - router
+        - doctrine
+        - debug

jmose/command-scheduler-bundle/2.0/config/routes/scheduler.yaml

@@ -0,0 +1,3 @@
+jmose_command_scheduler:
+    resource: "@JMoseCommandSchedulerBundle/Resources/config/routing.yml"
+    prefix:   /

jmose/command-scheduler-bundle/2.0/manifest.json

@@ -0,0 +1,8 @@
+{
+    "bundles": {
+        "JMose\\CommandSchedulerBundle\\JMoseCommandSchedulerBundle": ["all"]
+    },
+    "copy-from-recipe": {
+        "config/": "%CONFIG_DIR%/"
+    }
+}

jmose/command-scheduler-bundle/2.0/post-install.txt

@@ -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</>