CLI Command Line Arguments #1035

New Issue

2017-08-02T21:15:11+02:00

Lvl4Sword commented

2017-08-02 21:15:11 +02:00

(Migrated from github.com)

Daemon command line argument
Portable Mode command line argument
BITMESSAGE_HOME environment variable

Daemon and Portable Mode should be command line arguments. This allows other programs to use the CLI much easier.

- [ ] Daemon command line argument - [ ] Portable Mode command line argument - [ ] BITMESSAGE_HOME environment variable Daemon and Portable Mode should be command line arguments. This allows other programs to use the CLI much easier.

f97ada87 commented

2017-09-27 15:45:50 +02:00

(Migrated from github.com)

Hi Lvl4Sword,

The "portable mode" option in the QT client is misleadingly represented as a checkbox in the UI but it doesn't map to a true/false setting anywhere in the program. What that checkbox does, behind the scenes, is an ACTION, not a setting: it relocates the configuration, keys and data files from the program directory (portable mode) to the user's home directory (non-portable mode), or the other way round.

How would a "portable mode" command-line argument work, and how would it be different from setting BITMESSAGE_HOME to the program directory?

Hi Lvl4Sword, The "portable mode" option in the QT client is misleadingly represented as a checkbox in the UI but it doesn't map to a true/false setting anywhere in the program. What that checkbox does, behind the scenes, is an ACTION, not a setting: it relocates the configuration, keys and data files from the program directory (portable mode) to the user's home directory (non-portable mode), or the other way round. How would a "portable mode" command-line argument work, and how would it be different from setting BITMESSAGE_HOME to the program directory?

sp2004c commented

2018-01-26 12:35:11 +01:00

(Migrated from github.com)

true, one can set BITMESSAGE_HOME , does not even have to be an extra line in a bash script. Same effect.

This repo is archived. You cannot comment on issues.