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

Log in info safe on character.json file vs .env? #2265

Open
sonatonagems opened this issue Jan 13, 2025 · 2 comments
Open

Log in info safe on character.json file vs .env? #2265

sonatonagems opened this issue Jan 13, 2025 · 2 comments
Labels
bug Something isn't working

Comments

@sonatonagems
Copy link

Just a quick question about the safety of inputting our login information for social media platforms on the files. Is it safe to input them on the character.json file under "secrets", or is it better to have them in the .env?

What if you are running more than one character? Is there a way to add 2 different login info for the same platform (e.g twitter, or discord) in the .env and have them be assigned to different characters.json?

@sonatonagems sonatonagems added the bug Something isn't working label Jan 13, 2025
@user23406
Copy link

I have same problems, I want to add Twitter accounts in the .env and assign them to different characters. now I have to solve this question by myself

@ggindev
Copy link

ggindev commented Jan 15, 2025

I have same problems, I want to add Twitter accounts in the .env and assign them to different characters. now I have to solve this question by myself

Sure, you can add more variables for the additional characters in the .env and then reference them in the character file like so:

...
    "secrets": {
      "TWITTER_TOKEN": "${CHARACTER8_TWITTER_TOKEN}", 

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants