From 829f26441adb299d38fa5f96efef738d0e4f0446 Mon Sep 17 00:00:00 2001 From: mat ess Date: Sun, 21 Aug 2022 17:58:29 -0400 Subject: [PATCH] Minorer edit --- content/posts/gitea-on-fly-io/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/posts/gitea-on-fly-io/index.md b/content/posts/gitea-on-fly-io/index.md index 0e17445..28ca4bb 100644 --- a/content/posts/gitea-on-fly-io/index.md +++ b/content/posts/gitea-on-fly-io/index.md @@ -176,7 +176,7 @@ That doesn't look so great. It seems like Gitea idles just under the amount of m I have been running my Gitea install on a 512MB instance since the first day I started using it, which seems to be plenty of headroom for personal use. If you open up your Gitea installation to the public and it starts to get popular, you might end up needing to scale up further. -It's worth noting that scaling up to 512 MB means you will start accruing a Fly.io balance, but thus far this has never been more than a $2 monthly bill for me. If that's too steep for you, consider that Fly.io doesn't (at the time of this writing) charge for monthly bills below $5, or else check out some of the competing PaaS options out there. +It's worth noting that scaling up to 512 MB means you will start accruing a Fly.io balance, but so far this has never been more than a $2 monthly bill for me. If that's too steep for you, consider that Fly.io doesn't (at the time of this writing) charge for monthly bills below $5, or else check out some of the competing PaaS options out there. ### Acknowledgements - [Thank you to Xe Iaso for xer blog post on Fly.io that inspired me to try it in the first place!](https://xeiaso.net/blog/fly.io-heroku-replacement)