4 ms·
> Personally, I'd still want to take over if needed There's obviously no way you're getting access to the servers, but Ghost has a fully import / export option
by sudhirj 6y ago
> Personally, I'd still want to take over if needed
There's obviously no way you're getting access to the servers, but Ghost has a fully import / export option already built in. I can also zip up your images / themes etc. for you, so there's no lock-in. Even the domain will continue to be your own nameservers, you'll just point your custom domain to abcd1234.ghosting.dev.
And no, I don't think I'll need to limit the number of domains that point to your installation, but of course you'll want to do that yourself for SEO reasons.
The official Ghost.org do seem high, but I empathize because it does pay the salaries of an international team. But they're so high as to be inaccessible to normal people and companies. An individual writing a blog (especially outside a developed country) or a small company wanting to start a team blog isn't going to pay that much.
Would want to give a portion of revenue to the Ghost non-profit and support development as soon as I get ramen profitable, though, which will probably be happen at 100 to 150 customers.
- dna_polymerase 6y ago> But they're so high as to be inaccessible to normal people and companies. An individual writing a blog (especially outside a developed country) or a small company wanting to start a team blog isn't going to pay that much. They'd much rather use your reasonably well priced service. \s
- sudhirj 6y agoThe individual plans are going to be $5 / month, so yeah, I actually hope so.
- Brajeshwar 6y agoOK. Will you also have an option to auto-push the generated HTML and other static files to our S3? That can solve all the bandwidth issues while using your EC2/Server to just do the CMS part.
- sudhirj 6y agoGhost is a NodeJS app, and doesn't automatically do static site generating, but there's first class support for using other static site generators via the CMS API. That would be entirely up to the users, once you take over the installation you can either use it as an API for site builds or send people directly to it. Makes no difference to me either way.