Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Default configuration file #31

Open
cjeanneret opened this issue Dec 20, 2016 · 1 comment
Open

Default configuration file #31

cjeanneret opened this issue Dec 20, 2016 · 1 comment

Comments

@cjeanneret
Copy link

Hello,

The default configuration file shouldn't be in a location default user can't write. You should:

  • create ~/.config/tuntox directory
  • push the configuration file

All of that by default, else people just won't use it because it requires arguments for nothing — in addition, doing as proposed above meets the current usage for many other apps.

Cheers,

C.

@gjedeer
Copy link
Owner

gjedeer commented Dec 23, 2016

I kind of like that the client mode ToxIDs are ephemeral by default, it was by design.

Server mode is where storing the configuration is needed, but there are 2 use cases:

  1. Ephemeral server ran from command line, in which case you don't even need to write the config
  2. Server ran by init on startup, in which case you want it to use /etc like every other program, not ~/.config.

I saw someone packaged it for Arch and Ubuntu and I think packagers are who should worry about creating a new user account for tuntox and /etc/tuntox owned by that user.

Maybe I'm missing some important use case here, so your comments are welcome.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants