Replies: 2 comments 2 replies
-
Following up on this comment: farmOS/farmOS-community-blog#13 (comment) I did a little digging and found this: https://www.netlify.com/legal/open-source-policy/ + https://opensource-form.netlify.com/ We may be able to get a free "Pro" plan for the farmOS project with unlimited members! It looks like we already meet all the qualifications. The only additional thing we would need to do is add "This site is powered by Netlify" to farmOS.org. I'll go ahead and fill out the application form and see what happens... 😄 🤷 (Sorry don't mean to resurrect a closed issue, but this seems like the right place to document this for historical records.) |
Beta Was this translation helpful? Give feedback.
-
Update: the farmOS organization has an official Netlify account now! 🎉 |
Beta Was this translation helpful? Give feedback.
-
I'm opening (and will promptly close) this issue just to document some of the decision process in using the Netlify "starter" plan to host this, at least for the time being.
The current version of farmos.org uses GitHub pages, so the question has come up a few times, as with Field Kit (farmOS/field-kit#326 (comment)), whether we risk additional charges if we exceed Netlify's limits on traffic and build capacity for the starter tier, and how that compares to GitHub pages. So here's the breakdown, as of 2021-11-15:
They're pretty evenly matched, at least on those terms, although Netlify comes with a boatload of other free features that GHP doesn't even approach. And as I mentioned in a separate chat, perhaps the greatest advantage of Netlify is they at least give you the option of a higher price tier, if we're ever so fortunate to have that problem, while GitHub only has this advice:
Soooo, yea, to me this is a no brainer, but it's helpful to have the breakdown here for future reference in case it comes up again.
Beta Was this translation helpful? Give feedback.
All reactions