Automatic HTTPS is one of the most exciting features of DockerStacks and is heavily useful one as well.
DockerStacks has dedicated the domain stacks.run to achieve this feature for local development. When you create a new stack, DS app automatically maps the Stack ID as the subdomain of stacks.run using a reverse proxy
You can then access your stack using https://your-stack-id.stacks.run
How useful does this feature gets in development?
Well, very useful. When developing on a local server you can troubleshoot issues like mixed content errors, force HTTPs redirections, etc which are very hard to catch until deployed on a production server
Does it really work by default?
Yes, it does as long as you’ve port 80 & 443 not being used by other applications in your system. DockerStacks enables reverse proxy on these ports to serve the domain stacks.run on your local server