Every coworker can check out the (private) repo and has working HTTPS without any fuss or configuration. There are projects like https://lcl.host, but they require installing stuff on the machine and/or modifying the browser trust configuration. Why has nobody just registered a similar domain like lcl.host, pointed it to 127.0.0.1, and published the private key for everyone to use? Would the CA revoke this cert?... - Source: Hacker News / 7 months ago

Hi HN! I'm part of the Anchor (https://anchor.dev/) team building lcl.host: We launched lcl.host in March as the easiest way to get HTTPS in your development environment, and today we're launching new features to make lcl.host the best local HTTPS experience for development teams. Before lcl.host, setting up HTTPS in your local development environment was an annoyance, but getting your team to... - Source: Hacker News / 8 months ago

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 / about 1 year 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 1 year ago

For more information, refer to the official Docker documentation on secrets. - Source: dev.to / about 2 months ago

Storing sensitive information like passwords, API keys, and other secrets directly in your Dockerfile or Docker Compose file is a security risk. Instead, use Docker secrets for managing this sensitive data. - Source: dev.to / 7 months ago

Yes, swarm is not deprecated. I haven't used it myself yet, but I read elsewhere that swarm offers an easy way to manage secrets with containers. Some people run their 1 container in a swarm cluster with 1 node just for this feature. I see it's even officially suggested as a Note in the doc: > Docker secrets are only available to swarm services, not to standalone containers. To use this feature, *consider adapting... - Source: Hacker News / 8 months ago

The solution is to keep your images clean of any sensitive data. Instead, use environment variables, Docker secrets, or dedicated secrets management tools to handle sensitive information. - Source: dev.to / 9 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 / almost 2 years ago