3 ms·

> The paid plan is a little pricy It's literally the only problem with Ghost. Wonderful product but boy... how many people are going to pay $29/month or $228/y

> The paid plan is a little pricy It's literally the only problem with Ghost. Wonderful product but boy... how many people are going to pay $29/month or $228/year to host their personal blog? Yeah, there's some serious added value: managed upgrades, managed backups, DDoS protection, CDN setup, etc., and that's wonderful, but still... if you're basically just writing as a hobby, it's too much. I really hope they look into offering some kind of $5-10 hobbyist plan for low-traffic blogs.

scrollaway 9y ago
FWIW I don't think Ghost should be used on its paid plan for personal blogs. You can host it on a droplet or AWS free tier pretty easily, otherwise you can use Github pages. I hope Ghost will at some point have a "static site generation" mode though.
- solatic 9y ago
  You can use a droplet or AWS free tier, you'll just go offline in the "just in case" situation that your site gets hugged to death. Maybe it's just me, but I'd rather not plan for failure in the event of success. Part of the value added in SaaS like Ghost(Pro) is that the infrastructure needed to deal with traffic spikes is built-in. There really ought to be a pricing model along the lines of "I really don't expect this site to get much traffic at all, so sell me a cheap plan for day-to-day expected usage, but just in case something I write happens to go viral, I pre-approve a charge of $100 (or whatever) to deal with the traffic spike, and in case there's new sustained traffic then I'll of course upgrade to a more expensive plan which covers a higher expected rate of day-to-day traffic." Edit: let's put it another way: if you're publishing something to the Internet, it's because you want other people to read it. You therefore want other people to actually be able to read it in the rare but foreseeable circumstance that it becomes popular. If you didn't care about that, and you were really just writing for yourself, you'd just keep an offline journal.
  - scrollaway 9y ago
    > You can use a droplet or AWS free tier, you'll just go offline in the "just in case" situation that your site gets hugged to death Cloudflare in front with aggressive caching? What you're generating essentially is a static site, so it's safe to do that. If your S3 static site gets hugged to death, you won't go offline but you will pay an unexpectedly larger bill, so you should be setting up Cloudflare in front either way.
    - canttestthis 9y ago
      But that's no longer (non-technical) user friendly. Ghost is on the other end where they host it for you and if you get reddit or hn hugged it's still going to take your site offline, you just won't pay for it, but you get a pretty heavy charge for the convenience. None of these solutions would work for me.

scrollaway 9y ago

FWIW I don't think Ghost should be used on its paid plan for personal blogs. You can host it on a droplet or AWS free tier pretty easily, otherwise you can use Github pages. I hope Ghost will at some point have a "static site generation" mode though.

solatic 9y ago
You can use a droplet or AWS free tier, you'll just go offline in the "just in case" situation that your site gets hugged to death. Maybe it's just me, but I'd rather not plan for failure in the event of success. Part of the value added in SaaS like Ghost(Pro) is that the infrastructure needed to deal with traffic spikes is built-in. There really ought to be a pricing model along the lines of "I really don't expect this site to get much traffic at all, so sell me a cheap plan for day-to-day expected usage, but just in case something I write happens to go viral, I pre-approve a charge of $100 (or whatever) to deal with the traffic spike, and in case there's new sustained traffic then I'll of course upgrade to a more expensive plan which covers a higher expected rate of day-to-day traffic." Edit: let's put it another way: if you're publishing something to the Internet, it's because you want other people to read it. You therefore want other people to actually be able to read it in the rare but foreseeable circumstance that it becomes popular. If you didn't care about that, and you were really just writing for yourself, you'd just keep an offline journal.
- scrollaway 9y ago
  > You can use a droplet or AWS free tier, you'll just go offline in the "just in case" situation that your site gets hugged to death Cloudflare in front with aggressive caching? What you're generating essentially is a static site, so it's safe to do that. If your S3 static site gets hugged to death, you won't go offline but you will pay an unexpectedly larger bill, so you should be setting up Cloudflare in front either way.
  - canttestthis 9y ago
    But that's no longer (non-technical) user friendly. Ghost is on the other end where they host it for you and if you get reddit or hn hugged it's still going to take your site offline, you just won't pay for it, but you get a pretty heavy charge for the convenience. None of these solutions would work for me.