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

Separate account from base configs #4781

Closed
mjmadsen opened this issue Aug 26, 2016 · 4 comments
Closed

Separate account from base configs #4781

mjmadsen opened this issue Aug 26, 2016 · 4 comments

Comments

@mjmadsen
Copy link
Contributor

mjmadsen commented Aug 26, 2016

We should have an account file with just the following:
{ "auth_service": "", "username": "", "password": "", "location": "", "gmapkey": "", "encrypt_location": "", "config_location": "" }

Then the config_location is our base settings. We update the configs a whole lot and if you have multiple bots, that can be a lot of editing if you want to change default values.

Though, I still yearn for allowing us to enter a series of accounts we automatically switch between every so often. Decisions implementing this could make that easier or possibly harder.

Feedback welcomed.

@solderzzc
Copy link
Contributor

yes, very needed. Since the merging of work config and account config, I've done much work on the copy between configuration files.

@alexyaoyang
Copy link
Contributor

Agreed, having an account file will make things a lot easier for both new users and old. Your idea of switching between series of bot accounts might be easier with the live update code.

@solderzzc
Copy link
Contributor

It can't be real! #4793 works as charming

@mjmadsen
Copy link
Contributor Author

Awesome. Thanks you @rawgni

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

No branches or pull requests

3 participants