Admin password generation vs. docs about docker-wintercms HOT 6 CLOSED

@pablorq just to note, the docs are out of date. Setting a default of admin / admin is not a good security practice, hence why we put the generated password on install.

from docker-wintercms.

I have tested the combination of environment options and I have added an example docker compose file for fixing timing.

See examples/init-winter/docker-compose.yml

this commit

I think this is as far as I would like to automate. I think any further automation might be better implemented by extending the base image in a cutom Dockerfile

from docker-wintercms.

Using this:

docker exec -it container_name winter passwd admin admin

... as suggested in wintercms issue could be a solution if you work with docker from command line.

But in my case, I use Portainer and create stacks for each app, and this solution is not easy to use.

I think that the best way is to have admin:admin by default, specially when used with the INIT_WINTER=true variable.

from docker-wintercms.

@bennothommo I know that is not a good practice.

The point I'm trying to focus on is to deploy docker-wintercms with tools like Portainer or Kubernetes. And for this is necessary to setup the admin password outside the container, without having to get into it to extract the admin password.

I was trying to do that by adding this to the docker-compose file (as detailed here):

    environment:
    ...
      - INIT_WINTER=true
      - CMS_ADMIN_PASSWORD=admin

But it doesn't work. The password is randomly generated inside the container.

Any other ideas?

from docker-wintercms.

I just added this and need to properly test it. I think there may be some timing issues with the DB coming up and the winter:up occurring (and crashing) too early. I'm adding more detail on the subject at the moment

from docker-wintercms.

I'd say that's all you need @mik-p - nice one!

from docker-wintercms.