You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be great to keep our base images (apache + fpm) simple and don't overcomplicate things by adding a million different tags. (e.g. If you would like to add a 'heavy' tag, you would have to do apache, fpm, apache-heavy, fpm-heavy multiplied by the number of versions we're offering.)
Instead we could document the possibility to build on the base images and add what the user needs via derived dockerfiles.
For example something like:
FROM nextcloud:apache
RUN apt-get update && apt-get install -y smbclient && rm -rf /var/lib/apt/lists/*
This would be a great way to let the user choose what he needs. (Personally I use exactly this method now, I was just to lazy to update my github repo 😁 )
For the official compose part:
After working with diffrent installations (at work and at home), I think it's not feasible. There are so many possibilities to configure even the simplest nextcloud installtion and it's depending heavily on the server architechture used (proxies, databases, ect.). We surely should add more examples (and I strongly agree that our documentation of how to use the fpm image must get better), but marking a docker-compose solution as "official" might be misleading and a bad idea. We should focus on giving the right examples so anyone can build the setup that suits him.
PS: any comment on the /var/www/html volume part? #23
Activity
SnowMB commentedon Mar 3, 2017
I looked through the discussion and your comments and I like the ideas in docker-library/owncloud#79.
It would be great to keep our base images (apache + fpm) simple and don't overcomplicate things by adding a million different tags. (e.g. If you would like to add a 'heavy' tag, you would have to do apache, fpm, apache-heavy, fpm-heavy multiplied by the number of versions we're offering.)
Instead we could document the possibility to build on the base images and add what the user needs via derived dockerfiles.
For example something like:
Or for cron:
This would be a great way to let the user choose what he needs. (Personally I use exactly this method now, I was just to lazy to update my github repo 😁 )
For the official compose part:
After working with diffrent installations (at work and at home), I think it's not feasible. There are so many possibilities to configure even the simplest nextcloud installtion and it's depending heavily on the server architechture used (proxies, databases, ect.). We surely should add more examples (and I strongly agree that our documentation of how to use the fpm image must get better), but marking a docker-compose solution as "official" might be misleading and a bad idea. We should focus on giving the right examples so anyone can build the setup that suits him.
PS: any comment on the /var/www/html volume part? #23
ambis commentedon Mar 3, 2017
@SnowMB Spot on. Happy to see Nextcloud docker images are in good hands.
pierreozoux commentedon Mar 13, 2017
@SnowMB you are right, closing in favor of #47