You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of yesterday, AW on Heroku has exceeded our 10k database line limit. After approx. Monday, 29-Aug the db will reject new additions unless we upgrade. What's the bottom line? AW will have to be off-line for some period of time during the next week (TBD) to do the upgrade. The db should migrate without problems, but who knows -- so... be prepared? More to come.
The text was updated successfully, but these errors were encountered:
Would deleting areas help in the short term? I didn't know there was size limit, and I uploaded a new version of a REALLY big zone. I can absolutely yank some stuff down.
Also, can I please help defray costs involved in the upgrade?
If you're having to pay for this it looks like Heroku gets expensive really fast. Have you looked into other hosting providers?
When I was an FLI my sites and forums were on a service from railsplayground.com, but it looks like they haven't really update much since then. Their software seems a bit out of date.
More recently I've used bluehost.com. They seem to be much cheaper than Heroku and support ruby on rails. I like them when I was using them.
Be aware, I haven't used either of these in at least 3 years so your experience may vary. That being said, it may be worth shopping around. Heroku seems too expensive.
Rows were reduced from ~11.2k to ~7.2k, so immediate action is no longer required. The db upgrade is only $9/mo and Heroku is easy, so I'm inclined to stick with it... but we can look at other options.
As of yesterday, AW on Heroku has exceeded our 10k database line limit. After approx. Monday, 29-Aug the db will reject new additions unless we upgrade. What's the bottom line? AW will have to be off-line for some period of time during the next week (TBD) to do the upgrade. The db should migrate without problems, but who knows -- so... be prepared? More to come.
The text was updated successfully, but these errors were encountered: