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

Remove LAGO_ prefix from encryption env vars #210

Closed
wants to merge 1 commit into from

Conversation

atwalsh
Copy link

@atwalsh atwalsh commented Sep 20, 2024

Remove LAGO_ prefix from active record encryption env vars.

I had to remove this prefix to get Docker deploy working for the API.

https://github.com/getlago/lago-api/blob/0be7efbea6bb41b8d80990dc6d7f4fe82cc345a2/config/application.rb#L30-L32

@vincent-pochet
Copy link
Contributor

Hey @atwalsh tank you very much for pointing this mismatch between the code and the documentation.

I have opened two pull requests to fix this.
We would like to avoid changing the documented environment variables as they are currently in use in the docker-compose file from the main Lago repository (https://github.com/getlago/lago/blob/main/docker-compose.yml#L61).

@atwalsh
Copy link
Author

atwalsh commented Sep 23, 2024

@vincent-pochet sounds good! Will close this for now.

@atwalsh atwalsh closed this Sep 23, 2024
@atwalsh atwalsh deleted the patch-1 branch September 23, 2024 14:37
vincent-pochet added a commit to getlago/lago-api that referenced this pull request Sep 24, 2024
## Context

This PR is related to getlago/lago-doc#210

A mismatch was reported by a user between the environment variable
defined on https://doc.getlago.com/guide/self-hosted/docker and the one
used in the API application.

## Description

This PR makes sure that the API application is using the environment
variables defined in the documentation without breaking the setup for
users using the docker-compose.yml file from the main Lago repository
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.

2 participants