Pff, you guys DO make it hard if you create multiple docker images. How do we decide which one to advertise or do we do multiple etc?
I actually have thoughts about that: as security is a serious issue with these images, I am not comfortable putting anything up on the website that isn’t maintained by at least 2 people, ideally more.
What do you think about that? Do you think either of you will be able to get others to help out, at least have a look and promise to help out, get access to the repo etc?
I understand the concerns when it comes to advertising community projects. Moreover we’re talking about Docker images, which have to be maintained, so we must consider this issue even more seriously. I’m ready to grant some people I trust access to my repository project (Github & Docker Hub). My images are being used by many people I know personally and I’m constantly getting feedbacks, so I think there’s no problem with that.
Most of all I’m glad to see the Nextcloud project has interests in Docker, since the latter is a very cool way to make things work without racking brain. It should be officially considered as an alternative way to install Nextcloud.
Ok, that is cool. Let’s see if we can find people who want to help you out - once you have at least one other contributor who knows his/her way around the code, I’d be happy to make it 'official.
We could also consider moving the repo to the Nextcloud project, to give it more visibility. You’d be the maintainer, of course. What do you think about that? And otbe, nice - up for helping with this, too?
Actually I know two people who want to help, they have skills in Docker and Nextcloud, and they’re using my container. They’re ready to contribute.
And I agree, it would be nice to move the repo to the Nextcloud project, it gives more visibility and we can also make an organisation on Docker Hub. It’s up to you I think!
What differs mostly from Wonderfall is that I wouldn’t use “testing” software for production deployments. Therefor my container uses PHP5 and Alpine Linux 3.4 instead of PHP 7 and Alpine Linux “edge”. But I would be happy to help. It doesn’t make really sense to have much different containers.
Indeed it’s a good idea I think. We can move everything to the Nextcloud project, create two branches, one for php5 (stability) and one for php7 (performance). On Docker Hub, we can easily use tags. That would make sense, yes. We want to use Alpine Linux as a base, so there’s no reason to not gather our efforts.
Perfect. So for me it would be perfect valid to gather our efforts and merge the stuff together. I’m also very open to help maintaining that container.
I’m a strong advocate of one process per container, and docker also, so it would be nice to make the alpine image without cron/nginx and so on, just fpm.
To make it faster, we can start just with the fpm image, and then add the alpine one later.
We can create an other repo with a compose file, something like compose-nextcloud would make sense.
Once the repo is done, we can PR the official repo.
I can help on all the process, let me know!
@stp yes looks cool Will you use ceph for a distributed filesystem? This is actually a setup I plan to work on, but I think I’ll s/kubernetes/docker swarm/ with ceph as the data backend! If you have questions on docker, I might have some answers! Do not hesitate!
