Update on this: I've made the two GCS objects private for now, to reduce my bandwidth bill.
Also, we're turning down the Perkeep cloud launcher (to create an instance on GCP) & related infrastructure. Logs suggest there are fewer than 5 active users anyway, and it requires a disproportionate amount of work to maintain its DNS server & such. If you're one of those users and need help modifying your systemd unit files to pull the Docker image from elsewhere, let us know. On Fri, Jul 12, 2019 at 9:31 AM Brad Fitzpatrick <[email protected]> wrote: > Two users have Perkeep instances that seem to be crash looping, repeatedly > downloading the Perkeep docker image, costing me about $20/day. (mostly > due to me being lazy originally with how we distributed the bytes... we > don't conditionally fetch it, and we don't mirror around the world, so now > we pay for always-fetched redundant download bandwidth across the ocean) > > We'll put the downloads behind a CDN and make the downloading smarter, but > in the meantime, if you own one of: > > 104.154.108.235 > 35.246.163.66 > > ... could you fix or stop your instances? > > I don't want to delete the Google Cloud Storage objects and break other > people meanwhile. > > (Unfortunately, it doesn't seem like GCS supports per bucket or per object > ACLs that support filtering on IP addresses....) > > -- You received this message because you are subscribed to the Google Groups "Perkeep" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/perkeep/CAKPOmqPisn-jT3zaMpD0ojJEt4N2ZYXf%3DvwKSrQ3_14p1C6ZzQ%40mail.gmail.com.
