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

Environment variables not being read by generate_docker-compose.sh #1

Open
thebaldgeek opened this issue Jun 14, 2021 · 3 comments
Open

Comments

@thebaldgeek
Copy link

thebaldgeek commented Jun 14, 2021

Is there any way to edit generate_docker-compose.sh with the require variables?

I have set the environment variables as directed. When I read them back $ echo $WEATHERFLOW_COLLECTOR_THREADS 4 they are set. When I read them back as set | less I can see them:

TERM=xterm
UID=1000
USER=beno
WEATHERFLOW_COLLECTOR_IMPORT_DAYS=365
WEATHERFLOW_COLLECTOR_THREADS=4
WEATHERFLOW_COLLECTOR_TOKEN=aaaaaa56-bbbb-43e6-9e28-21bbac7c86d4

Regardless, the generate_docker-compose.sh returns the error:

./generate_docker-compose.sh

import_days=
loki_client_url=
perf_interval=
threads=
token=
WEATHERFLOW_COLLECTOR_IMPORT_DAYS variable not set. Defaulting to 365 days
WEATHERFLOW_COLLECTOR_LOKI_CLIENT_URL was not set. No default being set
WEATHERFLOW_COLLECTOR_THREADS was not set. Setting defaults: 4
WEATHERFLOW_COLLECTOR_PERF_INTERVAL environmental variable not set. Defaulting to 60 seconds
Missing authentication token. Please provide your token as a command parameter.

Same result with 'bash ./generate_docker-compose.sh'

Can I edit the generate_docker-compose.sh script to have the required variables?

Thanks for your time.

@lux4rd0
Copy link
Owner

lux4rd0 commented Jun 14, 2021

Hello there! Yeah - I saw that I left a little line that pushes the API token back into the script.

I did release a brand new version just now... That simplifies things a fair amount. Can you try downloading v3.2.2 and see if that helps out?

Also - your token that you have listed - is that your real token? When I try to see what happens with it says "unauthorized," - so either it's not a real key or something else is weird.

@thebaldgeek
Copy link
Author

Far out! This is amazing!
You have clearly spent a lot of time on this since I last downloaded it and got it running.
Major good job and thanks so much for sharing.

So yes, the new version had the fix I needed, followed the readme.md and it all just worked (tweaked the versions on all commands of course). Everything got pulled down and it just came up seamlessly.
Thanks for the update/fix and I am looking forward to seeing the data fill out (I have an original Sky and Air, and some data is not showing up yet, but I think it did this last time I ran the docker).

@lux4rd0
Copy link
Owner

lux4rd0 commented Jun 15, 2021

Here's a quick snapshot of what I'm testing against - it's a mix of Tempest, Skys, and Airs - depending on how they're connected to a hub as I group by station. But yeah - if you want to share a key I can test it with you. I've been fortunate to have a few more Tempest users test out the AIO and they had it showing data in a few minutes. However - it's always a fun way to test things out. Also - if there are updates to the steps, please let me know and I'll update the docs to reflect a FAQ. :)

multi-current_conditions

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