-
Notifications
You must be signed in to change notification settings - Fork 4
II.2. Server commands
Quit the application (process.exit(0); is used).
Print brief command help.
Set a configuration option (current config file will be overwritten). If value is not specified, you will be prompted to enter it.
Example:
ololord.js> set system.workerCount 2
OK
Print a configuration option.
Example:
ololord.js> get system.workerCount
Value for 'system.workerCount': 1
Remove a configuration option (current config file will be overwritten).
Example:
ololord.js> remove system.workerCount
OK
Show for how long the server has been running. The format is <days> <hours>:<minutes>:<seconds>.
Example:
ololord.js> uptime
0 days 19:12:55
Register a superuser. You will be prompted to enter a password or a password SHA-1 hash (recognized automatically), and then a list of IP addresses. These addresses are used to prevent the deletion of your posts by an administrator or a moderator (accidentally or intentionally).
Example:
ololord.js> add-superuser
Enter password:
*************
Enter superuser IP list (separate by spaces): 127.0.0.1 192.168.0.1
OK
Removes a superuser from the databas. You will be prompted to enter a password or a password SHA-1 hash (recognized automatically).
Example:
ololord.js> remove-superuser
Enter password:
*************
OK
Closes all workers (existing connections are closed) and reloads the templates (including the template partials). After that, opens workers for connections again. Useful when you update some partials or add new one(s).
Closes all workers (existing connections are closed) and rerenders all posts. After that, regenerates the cache. Then opens workers for connections again. Useful when there have been changes in the parser and you want to update existing posts. If board is specified, only posts on this board will be rerendered.
Closes all workers, preventing incoming connections. Existing connections are closed.
Opens workers for connections if closed.
Closes all workers (existing connections are closed) and rerenders all posts. After that, regenerates the cache. Then opens workers for connections again. Useful when cache bugs are detected. It's easier to just restart the application, though.
Rebuilds post search index. Useful if the index was corrupted due to editing DB manually, or some bug.