Closed nohant closed 1 month ago
ok, i made the app working. it seems that in caddy you cant have:
:8080 {
but instead need to have:
{$CADDY_SERVER_SERVER_NAME} {
with this edit the app is working, i mean, i have a blocked-mixed-content error but i can fight that, not all the app now :D
What happened?
Hello, we tried to switch from a normal
laravel/fpm
configuration to afrankenphp/octane
one. the fist step was configuring our local environment to work and that was almost flawless:and our entrypoint configuration is pretty simple to be honest:
and all this config works correctly, locally i can test the software and everything works fine (i love this.). But oh boy, when we tried to configure our staging environment (same image as production, you will read that in the dockerfile) everything went crazy, from caddy to octane to php?
we use a rootless environment and use www-data as our main user, the caddyfile is pretty simple too:
and to complete everything, the entrypoint for production, this is also pretty standard/straightforward:
i dont like to have to force
--admin-port
but i cant make the command work without that, and the log-level debug was needed in order to try to understand something of what was happening to be honest.we cant make this work on kubernetes with a barebone deployment, but we don't understand what we are doing wrong, since the only error we get is a 139 (we can see that from the
kubectl describe pod
)by the look of this there is something wrong we are doing that im missing? Thank you for your time.
Build Type
Docker (Alpine)
Worker Mode
No
Operating System
GNU/Linux
CPU Architecture
aarch64
PHP configuration
PHPINFO from the local enviroment (same dockerfile.)
Relevant log output
No response