Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Heroku has been running a second copy of my scheduler instance

openfolder.sh

Post reply on HN
Print view View original

61–70 of 132 posts

Re: Heroku has been running a second copy of my scheduler instance

#61

Post by netsharc »

joering2 wrote: post #39
ranting-moth wrote: post #38

Earlier quoted context omitted.

File a chargeback each time they charge your card. The merchant has to pay the transaction fees both ways and a fee for the chargeback.

But don't do it if its Google. I had been charged for g-suite for domain that expired and someone else picked it up (and parked), long story short after 3 months of back-and-forth with "support" I gave up and started with chargebacks. It was 7 of them, each month one for $6, until one sunny day I woke up and my own gmail account, my youtube TV and Google Play on 2 Android devices all got blocked with messages popping…

Geez, interesting heuristics with the WiFi, I guess the fucktards weren't checking SSIDs but noticed his account and yours shared the same IP, although that was in the past as well?

Re: Heroku has been running a second copy of my scheduler instance

#62

Post by lloydatkinson »

tannhaeuser wrote: post #57
lloydatkinson wrote: post #49

Earlier quoted context omitted.

I have been mulling over switching from Netlify to Vercel for a while for my personal site too. Netlify has weird defaults for everything. It caches almost nothing by default. I had to create a Netlify headers file to tell them that actually yes I would like my CSS, JS, and fonts cached. Absolutely absurd I had to do that. Even for font files. Because as we all know, the font files change so often that we should neve…

> fear of changing DNS settings Is that really a thing, with HNers of all people? You just use your registrar's/nameserver operator's web tool to point your DNS name to a new IP. Transferring your DNS to a new registrar might be a bit more involved but is guaranteed to be also possible by domain market regulation. Or maybe it is a problem of cache invalidation and/or lack of control over exact timing of DNS switchove…

Given that Netlify has very specific and unusual steps to setup in the first place, yes, it is a concern.

Re: Heroku has been running a second copy of my scheduler instance

#63

Post by lloydatkinson »

echelon wrote: post #58
tannhaeuser wrote: post #57

Earlier quoted context omitted.

> fear of changing DNS settings Is that really a thing, with HNers of all people? You just use your registrar's/nameserver operator's web tool to point your DNS name to a new IP. Transferring your DNS to a new registrar might be a bit more involved but is guaranteed to be also possible by domain market regulation. Or maybe it is a problem of cache invalidation and/or lack of control over exact timing of DNS switchove…

> Is that really a thing, with HNers of all people? You want it to be hitless. Unfortunately DNS can take days to fully propagate and you may not see mistakes until it's too late to fix them. This can cause horrifying outages. HNers should be respectful of DNS changes and plan accordingly.

Indeed, not sure what the anger in their comment was for.

Re: Heroku has been running a second copy of my scheduler instance

#64

Post by lloydatkinson »

echelon wrote: post #56
lloydatkinson wrote: post #49

Earlier quoted context omitted.

I have been mulling over switching from Netlify to Vercel for a while for my personal site too. Netlify has weird defaults for everything. It caches almost nothing by default. I had to create a Netlify headers file to tell them that actually yes I would like my CSS, JS, and fonts cached. Absolutely absurd I had to do that. Even for font files. Because as we all know, the font files change so often that we should neve…

> It caches almost nothing by default. Now I have to go check and see if it's not caching our fonts. Geez, I just assumed... > fear of changing DNS settings I recently had to migrate DNS to Cloudflare to stop a 40,000 QPS DDoS attack. DNS migration was slow, but painless. As long as you plan accordingly and set up the new destination in advance, it should be fine. Hosting DNS at a DNS provider will give you extra fle…

Yeah, it's absurd. Every page load the fonts were sent again.

I use google domains for dns too, just with netlify as the host.

Re: Heroku has been running a second copy of my scheduler instance

#65

Post by Gordonjcp »

sufehmi wrote: post #8

Clearly the author still hasn't learned his lesson: his "no more vendor lock" solution is another vendor(s) - which is always able to vendor-lock him, again. It is truly mind blowing on how many people keep falling for one of the oldest trick in IT : vendor lock-in. === No more vendor lock In 2018 Heroku was pretty much the only option for a newbie like me to get started with web-development. The landscape is very di…

> Heroku was pretty much the only option for a newbie like me to get started with web-development

How, exactly? What happened in 2018 that somehow made it impossible to just host a website?

Re: Heroku has been running a second copy of my scheduler instance

#66

Post by zakki »

echelon wrote: post #58
tannhaeuser wrote: post #57

Earlier quoted context omitted.

> fear of changing DNS settings Is that really a thing, with HNers of all people? You just use your registrar's/nameserver operator's web tool to point your DNS name to a new IP. Transferring your DNS to a new registrar might be a bit more involved but is guaranteed to be also possible by domain market regulation. Or maybe it is a problem of cache invalidation and/or lack of control over exact timing of DNS switchove…

> Is that really a thing, with HNers of all people? You want it to be hitless. Unfortunately DNS can take days to fully propagate and you may not see mistakes until it's too late to fix them. This can cause horrifying outages. HNers should be respectful of DNS changes and plan accordingly.

You can change your DNS TTL to let say 5 minutes before you move to new IP. You can change it 3 days before the movement(?).

Re: Heroku has been running a second copy of my scheduler instance

#68

Post by winrid »

vultour wrote: post #36

> In 2018 Heroku was pretty much the only option for a newbie like me to get started with web-development Free PHP webhosts have been around for 15+ years

you could even just throw up the job as an endpoint and have Zapier call it once a day or something! provided you can configure timeouts.

Re: Heroku has been running a second copy of my scheduler instance

#69

Post by progval »

emodendroket wrote: post #16
TylerE wrote: post #11

Earlier quoted context omitted.

Rent a $5/month VPS, install a few packages? Or just run a linux vm locally.

So, rely on yet another vendor, or do as I suggested except without any semblance of reliabiliy.

But there is no vendor lock-in here, VPS providers are interchangeable.

Re: Heroku has been running a second copy of my scheduler instance

#70

Post by oefrha »

lloydatkinson wrote: post #49
echelon wrote: post #41

Earlier quoted context omitted.

Netlify did this to me too! I have my startup with them and pay them a hefty bill. I had my personal websites on a second account (that should have been a free plan - one deploy every three years, next to zero traffic), and they deleted them and continue to bill me. I've had multiple customer service interactions asking them to stop billing me and they're nothing short of rude and unhelpful. "We've told you the dozen…

I have been mulling over switching from Netlify to Vercel for a while for my personal site too. Netlify has weird defaults for everything. It caches almost nothing by default. I had to create a Netlify headers file to tell them that actually yes I would like my CSS, JS, and fonts cached. Absolutely absurd I had to do that. Even for font files. Because as we all know, the font files change so often that we should neve…

Careful now, if you use Netlify’s _headers to do caching the obvious way, every time you push a new build, some of your users may get a broken site that can only be unfucked by clearing cache. I happened to have written about this problem a few days ago: https://news.ycombinator.com/item?id=35508640
Post reply on HN