Not really an issue per se, but I don't know why we lost and then gained rows. Either way we are above the limit for the free heroku tier. My AWS account should be within the free year for using AWS RDS for Postgres. We could move it up to there or find another db solution. Either way we are going to lose the insert privileges very soon. Maybe we can have a cycle of blowing the database up, then uploading a backup? Might be a sufficient work around of the limit (assuming that it doesn't get all freaky again and starts removing rows bc we broke boys).
Might want to look at migrating to AWS entirely, on resume might look better to say 'hosted on aws", also might be easier to manage our database issues.
Not really an issue per se, but I don't know why we lost and then gained rows. Either way we are above the limit for the free heroku tier. My AWS account should be within the free year for using AWS RDS for Postgres. We could move it up to there or find another db solution. Either way we are going to lose the insert privileges very soon. Maybe we can have a cycle of blowing the database up, then uploading a backup? Might be a sufficient work around of the limit (assuming that it doesn't get all freaky again and starts removing rows bc we broke boys).