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

API token handling clarification #139

Merged

Conversation

outlyer-net
Copy link
Contributor

I've modified the README to, as best as I can, clarify the handling of NIGHTSCOUT_API_TOKEN, which proved confusing for me and other newcomers.

Would close #104 and #113

@timoschlueter timoschlueter changed the base branch from main to release/2.6.1 May 17, 2024 05:45
@@ -68,7 +68,7 @@ docker run -e LINK_UP_USERNAME="[email protected]" \
-e LINK_UP_TIME_INTERVAL="5" \
-e LINK_UP_REGION="EU" \
-e NIGHTSCOUT_URL="nightscout.yourdomain.com" \
-e NIGHTSCOUT_API_TOKEN="librelinku-123456789abcde" \
-e NIGHTSCOUT_API_TOKEN=$(echo -n "foo-bar-baz" | sha1sum | cut -d ' ' -f 1) \
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Instead of "foo-bar-baz" we should use the same example token value ("librelink...") as in all the other parts to keep the documentation consistent.

@outlyer-net
Copy link
Contributor Author

Sure, I just used the foo-bar-baz hashing for consistency with the Local variant, whatever works best.

@timoschlueter timoschlueter merged commit 441664f into timoschlueter:release/2.6.1 May 27, 2024
1 check failed
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

Successfully merging this pull request may close these issues.

Better documentation for NIGHTSCOUT_API_TOKEN
2 participants