Skip to content

Commit

Permalink
Update README.md
Browse files Browse the repository at this point in the history
  • Loading branch information
Irytacja committed Sep 18, 2020
1 parent 3300a5a commit 1b2bd15
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -243,7 +243,7 @@ If this is your first time installing, please read the [Configuration](#configur
| `secret_key` | For multi-server setups (see below) all your servers must share the same secret key. Any randomly generated string is fine. |
| `job_memory_max` | The default maximum memory limit for each job (can also be customized per event and per category). |
| `http_port` | The web server port number for the user interface. Defaults to 3012. |

| `ip` | Te web server IP for the user interface or slave<>master comunication. Defaults to first eth* |
Now then, the only other decision you have to make is what to use as a storage back-end. Cronicle can use local disk (easiest setup), [Couchbase](http://www.couchbase.com/nosql-databases/couchbase-server) or [Amazon S3](https://aws.amazon.com/s3/). For single server installations, or even single primary with multiple workers, local disk is probably just fine, and this is the default setting. But if you want to run a true multi-server cluster with automatic primary failover, please see [Multi-Server Cluster](#multi-server-cluster) for details.

With that out of the way, run the following script to initialize the storage system. You only need to do this once, *and only on the primary server*. Do not run this on any worker servers:
Expand Down

1 comment on commit 1b2bd15

@Irytacja
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've added undocumented config option

Please sign in to comment.