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

initContainer for more independent builds #345

Merged
merged 2 commits into from
Jan 10, 2023

Conversation

CommanderStorm
Copy link
Member

Fixes Database not writable (our current db is readonly, so anything from #289 is depending on this Bug getting fixed)

Proposed Changes (include Screenshots if possible)

  • This moves where we store our db in prodction to /tmp/server.db
  • Previously this was done by the docker builder in github actions
  • said database is no longer populated in chained builds

How to test this PR

  1. Deploy it
  2. It works/ does not

How has this been tested?

  • It will be testd tomorrow

Checklist:

  • I have updated the documentation / No need to update the documentation
  • I have run the linter
  • I have slept and am ready to possibly break production

@CommanderStorm CommanderStorm self-assigned this Jan 8, 2023
- an initContainer and
- an actual server
instead of chaining the build
@CommanderStorm CommanderStorm force-pushed the feature/DBinitContainer branch from ad7a34b to aa96440 Compare January 10, 2023 01:36
@CommanderStorm CommanderStorm merged commit e6364ea into main Jan 10, 2023
@CommanderStorm CommanderStorm deleted the feature/DBinitContainer branch January 10, 2023 01:37
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.

1 participant