diff options
author | Azul <azul@riseup.net> | 2013-12-22 15:58:21 +0100 |
---|---|---|
committer | Azul <azul@riseup.net> | 2013-12-22 15:58:21 +0100 |
commit | 8c83e7a78385da8d15d274ee86f126a27f4763c7 (patch) | |
tree | c0a2e322b8f1bff68ba439e80e770f5fd3a2a15e /Readme.md | |
parent | 12dbeefe693e5432416ec8019368e591c526736b (diff) |
Version 0.3.1 with new flags --run-once, --rerun and --overwrite-security0.3.1
--run-once will exit once all current changes have been processed
--rerun will process all users again even those that were processed before
--overwrite-security will overwrite security for user databases even
if it has been set before.
Diffstat (limited to 'Readme.md')
-rw-r--r-- | Readme.md | 31 |
1 files changed, 22 insertions, 9 deletions
@@ -34,23 +34,36 @@ From gem: Running -------------------- -Run once: - - tapicero --run-once - This will create per user databases for all users created since - the last run. - Run in foreground to see if it works: tapicero run -- test/config/config.yaml - browse to http://localhost:5984/_utils + create a new record in the users database + observe /var/log/syslog or the logfile you specified -How you would run normally in production mode: +Run as a deamon: tapicero start tapicero stop -See ``tapicero --help`` for more options. +Run once and then exit: + + tapicero --run-once + This will create per user databases for all users created since + the last run and then exit. + +Flags +--------------------- + +--run-once: + process the existing users and then exit + +--rerun: + also work on users that have been processed before + +--overwrite-security: + write the security settings even if the user database already has some + +Combining these flags you can migrate the security settings of all existing per user databases. Configuration |