Alin Voinea
Alin Voinea
@sneridagh Yes, it works! :tada:
@svx I'm OK with this
@gforcada I'd place the Dockerfile directly within the development buildout, as we did for plone.restapi. We can have a talk on gitter, if you want ;)
The idea was not to encourage people to use this image directly in production with the `ADDONS` environment variable and all the other `env` variables that trigger re-build within Docker...
Anyway, I agree that we can remove the warning from the front-end README as Sven took care and added it everywhere else where it is relevant :smile: - https://docs.plone.org/manage/docker/docs/index.html#introduction -...
@svx @datakurre @jensens @tkimnguyen @thet @Rotonen @david-batranu See https://github.com/plone/plone.docker/tree/no-buildout branch. I also added a auto-build on docker-hub to test it: ``` docker run -i -p 8080:8080 -e ADDONS=eea.facetednavigation plone/plone:no-buildout ```...
@Rotonen https://github.com/plone/plone.docker/blob/no-buildout/5.1/5.1.0/pip/Dockerfile It's Debian stretch, no pin to setuptools.
And for [Plone 4](https://github.com/plone/plone.docker/blob/no-buildout/4.3/4.3.15/pip/Dockerfile) ``` docker run -i -p 8080:8080 -e ADDONS=eea.facetednavigation plone/plone:4-no-buildout ``` Wait for build to finish before running the above command :) https://hub.docker.com/r/plone/plone/builds/
We should take a look at https://hub.docker.com/r/sixfeetup/dietplonedocker/dockerfile made by @calvinhp