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

[fix]: remove db-migration step from infisical.yaml #5209

Open
wants to merge 12 commits into
base: next
Choose a base branch
from

Conversation

zaaakher
Copy link
Contributor

The db-migration step in the docker compose caused issues that I shared in this discord post
Basically last week Infisical made a release that does the db-migration automatically. Read more and including it in the docker compose caused issues that prevented infisicial from working altogether. So this PR fixes it.

Changes

  • Remove the db-migration part from the infisical.yaml template

@zaaakher zaaakher changed the title Fix/infisical 1 [fix]: remove db-migration step from infisical.yaml Feb 23, 2025
@zaaakher
Copy link
Contributor Author

Update

I added SMTP environment variables to the docker compose since Infisical expects them as per their email configuration docs https://infisical.com/docs/self-hosting/configuration/envars#resend

@zaaakher
Copy link
Contributor Author

On a side note, I found out (the hard way) that I have to map the port 8080 to the custom domain I added to the infisical backend service.
https://example.com didn't work and I had to do https://example.com:8080

Is there a way the port mapping could be configured automatically when using Infisical template? So that future users can just set their custom domain without having to worry about the port.

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