-
Notifications
You must be signed in to change notification settings - Fork 271
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
Update dockerfile #665
Update dockerfile #665
Conversation
I think we have have only the option to have a single nginx-php-fpm conatiner and only mount the storage volume
could be replaced with If we go with a single container, we could go with frankenphp. Update: Line 112 in 113c700
At the momment I think the "workaround" solution is to |
@benbrummer I wanted to avoid comingling nginx + php images as we've had criticism on that front before as it then is not optimal for a user who want to use caddy etc etc. The submodule idea is good, but we have the added complexity here of merging the react project also. This would not be a deal breaker, but it does add some additional overhead I think. I've never tinkered with this kind of idea. However I think ultimately we are still in trouble as we will always need to expose the public/ directory even if :ro which then circles us back to the original problem where the volume mount excludes the images public/ dir.... |
With the submodule, we only need to update the commit hash to get the new version. A merge is not needed. Update: Got it react project is not part of the invoiceninja repo |
|
This has certainly gone beyond my experience levels with docker, so I am in your hands for this 😆 |
I will try to come up with a proposal. Can you tell me the purpuose of Line 127 in 113c700
as it is not inside |
I believe public/uploads it is redundant. I will merge this PR as a temporary solution so that as we tag new images, the files can at least update until a new master image has been created. |
No description provided.