Difference between revisions of "Daemon"
Jump to navigation
Jump to search
(cleaned the article) |
|||
| Line 1: | Line 1: | ||
| − | PyBitmessage can be run in deamon mode by adding this line to your keys.dat file under [bitmessagesettings]: | + | PyBitmessage can be run in deamon mode by adding this line to your [[keys.dat]] file under <nowiki>[bitmessagesettings]</nowiki>: |
daemon = true | daemon = true | ||
| − | In this mode, PyBitmessage doesn't require Qt. You will then need the [ | + | In this mode, PyBitmessage doesn't require Qt. You will then need the [[API]]. If you do not yet have a keys.dat file because you have not yet run Bitmessage, run it. It will create the keys.dat file for you then exit if it cannot find PyQt. |
| − | + | == Control == | |
| + | The client can only be controlled via the API, so it is important to set the API values too in the Settings file. | ||
| + | |||
| + | == Example == | ||
| + | Example Daemon for using Bitmessage via a console: [https://github.com/Dokument/PyBitmessage-Daemon Bitmessage Daemon (GitHub)] | ||
Revision as of 11:26, 13 June 2013
PyBitmessage can be run in deamon mode by adding this line to your keys.dat file under [bitmessagesettings]:
daemon = true
In this mode, PyBitmessage doesn't require Qt. You will then need the API. If you do not yet have a keys.dat file because you have not yet run Bitmessage, run it. It will create the keys.dat file for you then exit if it cannot find PyQt.
Control
The client can only be controlled via the API, so it is important to set the API values too in the Settings file.
Example
Example Daemon for using Bitmessage via a console: Bitmessage Daemon (GitHub)
