docs
docs copied to clipboard
Update log shipper docs to ensure that no public access is granted
A customer pointed out that our log shipper could expose its GraphQL API. We want standard shipper deployments to have no services nor IPs.
Note: --no-public-ips fails when an HTTP service is setup by default by fly launch.
Should we mention that if they want only 1 machines, then use the --ha=false flag on fly deploy?
Related: this user PR for apps that do have 2 machines https://github.com/superfly/docs/pull/820
Yes, actually this may be a related issue. The shipper can operate in HA mode by setting a QUEUE env var, but that doesn't happen by default. I've been working on automating the shipper, but parked that for now.
#820 mentioned above was merged. this added info about QUEUE env var to the docs
@jsierles Should we still ship this docs change or did it get fixed in flyctl?