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

XMR: private API should be configured each time we start the container using the ENV variables #2853

Merged
merged 1 commit into from
Jan 14, 2025

Conversation

dasgarner
Copy link
Member

@dasgarner dasgarner commented Jan 14, 2025

fixes xibosignageltd/xibo-private#901

Instead of only setting the private API configuration option on installation, we set it each time the container starts. The setting is not visible to users, so should be configured from the environment variable anyway.

@dasgarner dasgarner requested a review from PeterMis January 14, 2025 13:59
@dasgarner dasgarner self-assigned this Jan 14, 2025
@dasgarner
Copy link
Member Author

@qaxlyka I do not believe it will be possible to QA test this change - running any of the automated test suite would be sufficient to prove the container still runs.

@qaxlyka
Copy link

qaxlyka commented Jan 14, 2025

Hi @dasgarner i dont know yet what im doing, i was just looking around to understand how it works. Might have done something I didn't mean during that time 😅

@dasgarner
Copy link
Member Author

TEST: login.cy.js END

Copy link

@dasgarner
Copy link
Member Author

@qaxlyka no problem, I ran an automated test which proves the container still works after my changes. That's all we need for this one. Thanks!

@dasgarner dasgarner merged commit be0bb71 into develop Jan 14, 2025
2 checks passed
@dasgarner dasgarner deleted the bugfix/kopff_xmr_upgrade branch January 14, 2025 16:25
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.

3 participants