lcl.host VS Docker Secrets

Lcl.host is an easy way to enable HTTPS in local development environments, which improves the security of the development process, ensures feature parity between development and production environments, and enables features like CORS that behave differently on localhost. - Source: dev.to / 10 days ago

Getting HTTPS setup and working with an app in local development is tricky. There were two options: acquire a publicly-trusted certificate from a CA, or make your own self-signed certificate from the command line. Neither of these options are simple, that's why most developers skip HTTPS in their development environment. But lcl.host now makes this quick and easy. - Source: dev.to / about 2 months ago

Docker has revolutionized the way we build, ship, and run applications. However, when it comes to handling sensitive information like passwords, API keys, and certificates, proper security measures are crucial. Docker secrets provide a secure and convenient way to manage sensitive data within containers. - Source: dev.to / 11 months ago

Are you using swarm mode? If so, you might want to consider using secrets. Source: over 1 year ago

Have a look here https://docs.docker.com/engine/swarm/secrets/. Source: over 1 year ago

To use a secret you have to map it during the creation of a service (in this case redis like in the documentation:. - Source: dev.to / over 1 year ago

Using docker secrets: This seems a no brainer, however, I haven't yet fully understood the documentation entry. For example, after reading this entry I still don't know if I can use docker secrets along with my strategy of having a separate .env file containing the environment variables (and the sensitive ones being handled by docker secrets). I have to enable swarm mode and I don't fully understand the... Source: over 1 year ago