Skip to content

Conversation

javiermtorres
Copy link
Contributor

What's changing

The whole DB URL is passed through the environment. This allows a custom DB to be used without any changes.

How to test it

Start the lumigator image using the provided URL, and removing the postgresql service from the docker compose. SQLite should be used instead locally in the lumigator image.

Related Jira Ticket

LUMI-86

Additional notes for reviewers

I already...

  • added some tests for any new functionality;
  • updated the documentation.

@javiermtorres javiermtorres force-pushed the LUMI-86-main branch 4 times, most recently from 7d68c4d to 17830b8 Compare September 27, 2024 08:02
Copy link
Contributor

@agpituk agpituk left a comment

Choose a reason for hiding this comment

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

I think we should remove postgres dependencies from the docker-compose and simplify the variables as well

@agpituk
Copy link
Contributor

agpituk commented Sep 30, 2024

I think we should remove postgres dependencies from the docker-compose and simplify the variables as well

Also, can we add local.db to .gitignore?

@javiermtorres
Copy link
Contributor Author

Also, can we add local.db to .gitignore?

Hm. I don't know what's the policy here. The idea is that the user will place the db file wherever they see fit, so the mounted local.db could end up outside the tree, or even be called something else. So I wouldn't add such a particular file name to .gitignore :-/

Use a relative SQLite db file as default in compose.
Leave postgres env vars.
@javiermtorres javiermtorres merged commit 7fae0f8 into main Oct 9, 2024
2 checks passed
@javiermtorres javiermtorres deleted the LUMI-86-main branch October 9, 2024 11:15
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