-
Notifications
You must be signed in to change notification settings - Fork 19
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
VATSIM_CORE_API_TOKEN Env Variable not being properly read. #1081
Comments
Sorry, but I can't give you support on almost year old version (v4) when v6 is now the current one. Please update to v6 and let me know if the issue still persists. |
Oh! (Might want to update the docs :P) Updating. And yeah, the variable name changed that's why. |
Can you link me to the docs where it told you to download to v4? I'll correct it |
Sure! It's on the following pages: https://docs.vatsca.org/controlcenter/latest/getting-started/ https://docs.vatsca.org/controlcenter/latest/installation/ |
If Also try to call Call all the commands inside the container. |
Ran both commands inside the container but the issue remains. |
I don't understand why this wouldn't work for you unless the key is actually invalid or maybe an v1 key. Everything works on my end here. Confirm this key of yours can be called in the |
I personally do not use Docker on production, but what about this? https://docs.vatsca.org/controlcenter/latest/getting-started/#add-the-docker-compose-file. Environment is specified in docker-compose file in this example. I do not know how @hatoriganzo configured CC, but can't be this problem? You can also specify .env file using https://docs.docker.com/compose/how-tos/environment-variables/set-environment-variables/#use-the-env_file-attribute But I am just guessing and throwing some stuff that came up to my mind |
Also, @hatoriganzo, did you check that you have latest image? From my experience, sometimes I must explicitly rebuild the image otherwise old tag is installed (v4 instead v6). Something like |
Since @hatoriganzo already did tinker and |
Yeah I'm starting to think the key is the issue. It was just given to me from the dev team but I'll inquiry with them. Do you know any endpoint in the API that REQUIRES the key so I can properly test? |
Confirmed 6.0.6 |
I found out why.. Because the API calls the subdivision call instead of division😅😅
If you change this to the division call instead? |
Changed the code and. 🥁 It worked |
Marking as closed as related to #1080. |
Environment
CC Version: ghcr.io/vatsim-scandinavia/control-center:v4
Host type: Docker Compose running on Portainer
Describe the bug
VATSIM API V2 token is not being read when configured per documentation as the VATSIM_CORE_API_TOKEN environment variable in the dockercompose.yml.
How to reproduce
Steps to reproduce the behavior:
Expected behavior
Working user page
Screenshots
Additional context
After some tracking, I noted the config variable is being assigned in config/vatsim.php line 15.
Running php artisan tinker in the container I noticed the ENV variable is properly set but the config property stays null. Works with other variables assigned the same way tho.
The text was updated successfully, but these errors were encountered: