1–10 of 12 posts
In 30 days, our Starter plan will require that GitHub repositories connected to your Netlify account are either linked to Personal GitHub accounts or set for public visibility. If you have repositories using an Organization-owned GitHub account set to private visibility, you will need to move to the Netlify Pro plan or above.
It's not unreasonable, however 30 days seems a bit on the short side. I have 15+ repos that I'll need to review. Another thing that would be nice is if the affected sites would be tagged in the Netlify dashboard or mentioned in the email. That would make the review process a bit easier
It's not unreasonable, however 30 days seems a bit on the short side. I have 15+ repos that I'll need to review. Another thing that would be nice is if the affected sites would be tagged in the Netlify dashboard or mentioned in the email. That would make the review process a bit easier
I don't think 30 days are reasonable and our costs would go up 150x! On top of having regular outages over the last six months. Not going to happen. I'm out.
I like their service but I paid for analytics for a while through them and didn’t find it worthwhile, so I will probably not want to pay for the one site that needs it when I can host elsewhere for cheaper now.
Pro plan is $19/month ( https://www.netlify.com/pricing/ ). As a business we have 5 static websites with them. It's reasonable and we will upgrade without looking around. The feature that brought us to Netlify was being able to set additional HTTP headers (via a configuration file). We don't use or need any of the other pro features (extra build minutes, more bandwidth). To us it was clear the free plan we used would…
I'm moving quite a few websites for the various non-profits I'm involved in to Cloudflare — mainly because it's free to add team members there.