Closed jakst closed 6 years ago
The conf/html
and conf/php
configs that are supplied are opinionated as the readme details. Those configs are templates for people to build upon, tear down or toss away. Why not create your own conf/yourownconfig
that reflects a dev, stage or production setup? You can create a conf/dev
, conf/stage
and conf/prod
configs that reflect your desired setup. You can easily create a compose file dev.yml
, stage.yml
and prod.yml
that makes running everything super simple.
That really reduces the purpose of you docker image to a mere starter template though. Now I will have to manually implement almost all your upstream improvements to these configs.
The reason I asked so bluntly is actually because I believed there to be one implemented already that I had missed.
Anyway, I have already forked your project because of other customisations, but I do believe a dev mode without caching would be a worthy addition to your image.
The challenge with any pre-built set of configurations is that it depends on what you are developing. Is it html
, php
, python
, something else? Is it just cache or anything else? I don't know. You could always use basic
for a local development configuration but I'm guessing that is not what you want. The goal of releasing this was to allow others to build upon. You could always contribute by creating a development configuration and I would be happy to review a pull request. If you just want to fork, that is up to you.
How do you turn off the cache for development purposes? It is frustratingly difficult to develop now as this image caches so agressively (which is awesome for production though).