-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
base: next
Are you sure you want to change the base?
Conversation
v4.0.0-beta.392
feat(service): add convex
v4.0.0-beta.393
v4.0.0-beta.394
v4.0.0-beta.395
infisical.yaml
UpdateI 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 |
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. 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. |
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
db-migration
part from theinfisical.yaml
template