Formatting

website/content/pro/docker.md

@@ -11,11 +11,13 @@ This executor needs a recent version of docker to be available and configured in
 To run a docker job create a job config with the docker executor as in this example:
 
 ```json
+{
   "executor": "docker",
   "executor_config": {
     "image": "alpine", //docker image to use
     "volumes": "/logs:/var/log/", //comma separated list of volume mappings
     "command": "echo \"Hello from dkron\"", //command to pass to run on container
     "env": "ENVIRONMENT=variable" //environment variables to pass to the container
   }
+}
 ```

website/content/pro/elasticsearch.md

@@ -9,11 +9,13 @@ The output logs of the job execution will be stored in the indicated ES instace.
 ## Configuration
 
 ```json
+{
   "processors": {
     "elasticsearch": {
       "url": "http://localhost:9200", //comma separated list of Elasticsearch hosts urls (default: http://localhost:9200)
       "index": "dkron_logs", //desired index name (default: dkron_logs)
       "forward": "false" //forward logs to the next processor (default: false)
     }
   }
+}
 ```

website/content/pro/email.md

@@ -22,13 +22,15 @@ Then configure each job with the following options:
 Example:
 
 ```json
+{
   "processors": {
     "email": {
       "provider": "provider1",
       "emails": "team@mycompany.com, owner@mycompany.com",
       "onSuccess": true
     }
   }
+}
 ```
 
 By default the email procesor doesn't send emails on job success, the `onSuccess` parameter, enables it, like in the previous example.