Hi Gatsby Team!
Why do we need Gatsby develop mode in internet?
Our authors are non technical people who contribute content directly to CMS.
We are running Gatsby in develop mode on an Amazon EC2 instance to provide them better preview experience. When authors make some changes on the CMS side, we just trigger
The server is available in internet and restricted with Basic auth, that's it. As well we activated https for sure.
Questions
What do you think about making server running gatsby develop available in internet from security perspective?
Does Gatsby server in develop mode open some insecure sockets, does it give some potential for vulnerabilities?
Thanks!
Hey @teavirdis
There aren't any security vulnerabilities _per se_ but gatsby develop does expose the /___graphql route that gives access to all your data (which you might or might not be with)
Also, I really wouldn't recommend running gatsby develop as a production server as one would miss out of all the benefits of building to static assets. As an internal preview server of sorts, I suppose it's fine.
@teavirdis expanding on what @sidharthachatterjee said, and from a perspective of a contributor to the project, vulnerabilities per se there are none until someone finds one and reports it and then it's fixed either by a development team member or even for a contributor like myself.
I've applied the same approach you're using a while ago to demonstrate a proof of concept to a audience that was not in any way, shape or form technically savy, as part of the audience was in a different part of the country and one part in a different country and i got no issues whatsoever.
But it goes without saying, that while demoing it's fine in this form. But i would like to leave a couple of items regarding this issue:
Hope i can see the finished product being added to the list of sites in a near future. I would like to thank you for using Gatsby.
Thank you guys for answers! Such great support brings a lot of confidence in using your solution:)
Most helpful comment
@teavirdis expanding on what @sidharthachatterjee said, and from a perspective of a contributor to the project, vulnerabilities per se there are none until someone finds one and reports it and then it's fixed either by a development team member or even for a contributor like myself.
I've applied the same approach you're using a while ago to demonstrate a proof of concept to a audience that was not in any way, shape or form technically savy, as part of the audience was in a different part of the country and one part in a different country and i got no issues whatsoever.
But it goes without saying, that while demoing it's fine in this form. But i would like to leave a couple of items regarding this issue:
Hope i can see the finished product being added to the list of sites in a near future. I would like to thank you for using Gatsby.