-
-
Notifications
You must be signed in to change notification settings - Fork 91
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
Docker #313
Docker #313
Conversation
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. We should probably fire this up where it's actually on the internet to see how it goes before we fully release it.
We can add more compose files later. Some with all the things needed for redis/valkey and mariadb support.
I've been digging into this a bit, both testing the Compose as well as the container builds, and tinkering with Helm. I run entirely in k8s any more, and having everything so tightly coupled in the current Dockerfile causes issues there. That being said, I was able to split out Caddy and the Panel with Docker Compose (and Helm as well), by simply overriding commands, and editing and mounting the config file. But I do believe the base Dockerfile for the Panel should not bundle Caddy, each component (Caddy, Panel, Redis, etc.) should be it's own service. From what I've been looking into this evening, what's needed to make this more micro-service friendly is:
Just a note that I'm willing to work on the above if you'd accept a PR. Let me know what you think of the above or if you're looking to go a different direction, happy to help. |
On the "composer install --no-dev --optimize-autoloader" part from the docker-compose, after reaching it, it returns the error code 2 This is the logs:
|
@LumiKattlin did you have this issue while building the container? I just tried out a build and it worked. Have you tried this recently? |
Yeah, dw, it ended up being a mistake on my part ended up working 👍 |
@parkervcp sorry for ping, do you have any ETA on when this will be merged ? |
This reverts commit 649e82d.
dockerfile cmd updated to just start php-fpm entrypoint now starts caddy unless SKIP_CADDY has been set. compose file updated ports to work properly. updated networks to use the correct network. added commented port and variable to disable caddy added further notes.
Well that was ugly |
f6609b1
to
6f15537
Compare
Update the dockerfile to use supervisord Update supervisord config to use start caddy unless configured not to. Updated entrypoint to handle caddy skip for supervisord.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
No description provided.