From: Taylor Blau <me@ttaylorr.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: git-scm.com is now a static website
Date: Mon, 30 Sep 2024 12:11:06 -0400 [thread overview]
Message-ID: <ZvrNmsycmamx2dcR@nand.local> (raw)
In-Reply-To: <ZvM65LqtFW8f9uqC@nand.local>
On Tue, Sep 24, 2024 at 06:19:16PM -0400, Taylor Blau wrote:
> I haven't yet spun down the dynos on Heroku, on the off-chance that we
> need to quickly get back to the non-static version of the site. But the
> rollout has gone so smoothly that I doubt doing so will be necessary. In
> a couple of days I'll go ahead and spin them down, assuming nothing has
> changed.
I had a reminder in my personal calendar today to shut down our Heroku
account, which is now mostly done.
I de-provisioned all of our add-ons (which were the Heroku Scheduler,
Postgres, and Bonsai instances), and then deleted the app.
The only thing that is left is to actually delete the account itself,
which can't be done until our last invoice is cleared, which should
happen on sometime later today. Our final invoice is $61.86 USD. Once
that is cleared, I'll delete the account entirely.
(As an aside, this is a significant cost-savings for the project. Our
usual invoices are around $65 USD/mo, but that is taking into account
the OSS credits[1] that Heroku provides us, which are worth $40 USD/mo.
So the real cost-savings is somewhere around $1,200 USD/yr, which is
awesome.)
Thanks,
Taylor
[1]: https://lore.kernel.org/git/ZZ7zezSRZfdklS4u@nand.local/
next prev parent reply other threads:[~2024-09-30 16:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-24 22:07 git-scm.com is now a static website Johannes Schindelin
2024-09-24 22:19 ` Taylor Blau
2024-09-30 16:11 ` Taylor Blau [this message]
2024-10-09 16:09 ` Taylor Blau
2024-10-09 17:33 ` Junio C Hamano
2024-09-24 22:28 ` brian m. carlson
2024-09-24 22:29 ` Jeff King
2024-09-24 23:53 ` Junio C Hamano
2024-09-26 8:30 ` Toon Claes
2024-09-26 13:53 ` Patrick Steinhardt
2024-09-29 8:41 ` Scott Chacon
2024-09-30 7:46 ` Christian Couder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZvrNmsycmamx2dcR@nand.local \
--to=me@ttaylorr.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).