Getting new SQL errors out of the blue from the site I set up using this project

[crates]

Describe the bug
Hey there! I love the work you've done on this. I've been running a blog using a free Heroku dyno for the last 6 months or so, and adding content to it regularly. However, starting on May 1st, I am no longer able to spin up my instance. It crashes when trying to boot up, with this error message:

Error: ER_TABLEACCESS_DENIED_ERROR: INSERT command denied to user

I haven't changed anything. This just started happening out of the blue. I tried redeploying the Dyno, but it's not working anymore. The site is down and I have no idea how to recover it.

How are you deploying this?
Originally I did the one-click deployment, until things broke earlier this week. Since then (and AFTER the problem started happening) I tried cloning the repo and upgrading Ghost from 3.2.0 to 3.14.0, and deployed it that way... but that didn't fix anything! :-(

[crates]

Just wanted to weigh in on this one more time, as I've done a bunch of troubleshooting and I think I've narrowed it down to the underlying issue. I'm guessing someone else might need this information in the future, if they actually write any content for their Ghost site!

Here's what the issue seems to be (as near as I can tell thus far):
The JawsDB MySQL instance that comes with the Heroku plan that you've included in this project is limited to a maximum of 5 MB of storage, which I ran out of pretty quickly.

What really sucks here is that the only plan that provides more than 5 MB of storage is the "Leopard" plan, which costs $10 a month. I chose this method of setup because I was hoping to avoid paying hosting costs like that -- for that amount of money, I can easily set up a whole VPS on any one of a number of hosts.

Any thoughts on this? Have you encountered any similar issues? Suggestions for a workaround?

[JaneJeon]

Yikes, that's rough. Honestly, you're not gonna get any paid DB hosting under 10/mo, especially so if you want it to be "proper" (e.g. JawsDB hosts its DB on HDDs - which is absolutely mind boggling to me - instead of on SSDs). The proper ones - like those hosted on DigitalOcean & AWS - often cost $15/mo.

The workaround would be to host your own MySQL by (ab)using some of "big boy" cloud providers' perma-free tiers, which are much more beefy than what JawsDB offers. I know for a fact that GCP offers a permanently free VM instance, which has 30GB of HDD disk, for example. Oh, and I think Oracle (scary, I know) has a generous free tier as well (much beefier "perma-free" VM, iirc).

[flynncowell]

Having same issue here.

Love the Button aside from this.

[JaneJeon]

@crates @flynncowell again, please report back AFTER you've upgraded your instance. If you have nothing else to add, this will be closed in a week.

[crates]

@JaneJeon : I upgraded the instance and redeployed, and this issue self-resolved immediately.

I'll close the issue, but it's worth noting that it's still (sort of) an issue with the project.

I'd be satisfied if the documentation clearly stated that you're only going to get about 2 dozen pages or posts published before you need to upgrade to a paid plan. That would've probably guided me to make different choices when setting this up, since it's more viable for hobbyist test purposes than any kind of production use.

[crates]

@JaneJeon / @SNathJr :

I also just noticed that the documentation does, in fact, state:
If you create a lot of content or decide to scale-up the dynos to support more traffic, a more substantial, paid database plan will be required.

All I'm looking for is a little more clarity there. Ideally I would revise that to:
If you create a lot of content (more than 2 dozen pages or so), a more paid database plan will be required. The cheapest option on JawsDB (the default) is $10 per month. If you use more than 5 MB of database space, you'll get an error stating "ER_TABLEACCESS_DENIED_ERROR: INSERT command denied to user", which means you've run out of space and need to upgrade your plan.

I'm happy to open a pull request if you'd like! I already have an upgraded fork of this project where I've migrated to Ghost 3.14.0 which contains a lot of performance and stability fixes anyhow.

[JaneJeon]

@crates hey, I didn't get to read your final comment. We'd definitely appreciate the PR - would you like to create it?

[crates]

@JaneJeon

Sure thing, my pleasure! I'll take a look at creating one later today.

[Indosaram]

I was dragged by this issue as well. I figured out this happened because of MySQL, but didn't know this coming from the store limit. I had chosen this setup due to the same reason as @crates, but 5MB limit is so hash.

How can I replace thouse DBs to other DBS?

[crates]

@Indosaram - For me, I just ended up paying for Jaws DB... However, their hosting costs are a little steep, so I'm also looking at migrating to a different host. I've been meaning to update this repo with a pull request and just running a little behind with it. I'll see if I can include something like that with the PR, or maybe a second one later. In the meantime, consider paying the $10 a month for a paid Jaws DB membership for a month or two until we can get you clear instructions to migrate elsewhere.

[Indosaram]

@crates Thank you for a quick reply! I just abandoned ghost CMS and moved on to pure Gatsby 😥

Ghost is a beautiful and easy-to-use blogging platform(Especially their Unsplash integration, automatic meta info generation), but their CMS integration might need to be improved.