gatsby: Missing `--https` option for `gatsby serve`?

@kakadiadarpan I don’t believe gatsby serve is intended for actually publicly serving the site – it’s for locally serving it after it has been built (i.e., for previewing, or testing). Right @KyleAMathews?

If --https is a useful feature for develop (and I think it really is), then it is also a useful feature for serve.

This should be reopened.

Not stale. Still important in regards to testing.

What about running end-to-end tests? I have tests that check that secure cookies are written. It would be really useful to be able build and serve locally to run tests against.

Have a draft version of this here https://github.com/gatsbyjs/gatsby/pull/26110

Hiya!

This issue has gone quiet. Spooky quiet. 👻

We get a lot of issues, so we currently close issues after 30 days of inactivity. It’s been at least 20 days since the last update here.

If we missed this issue or if you want to keep it open, please reply here. You can also add the label “not stale” to keep this issue open!

As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing!

Thanks for being a part of the Gatsby community! 💪💜