Once I do that - can’t get in. The hosting provider put back my original package limits, so I assume it’s reverted to the bad behavior. Could I just clone certain parts of the database to the new one? I mean - it’s just like 2MB of data - it shouldn’t be giving this much trouble right?
Could there be some issue with the database having moved from v4 previously? Is there any way to rebuild this?
Based on what’s going on, I’ve tried to run an Ubuntu instance to attempt deploying - but no luck thus far. Using these resources - but no luck.
May have to do some further digging - but I’ve tried this on a fresh Ubuntu install and I have varying problems.
I’m not as Linux savvy as I’d like to be, and that’s why I try to simplify and write out details/guides for myself and others.
I did find some info elsewhere that may work with v5.5. Maybe I should attempt that and then udpate? The issue seems to be with the php version. In the end, none of the options I tried actually worked to get thigns running self-hosted. I’m open to added assistance though.
Let’s see if I can get the shared hosting working first. I’d rather keep things the way they were with that.
So…what are the CPU/RAM requirements like for running this? I assume it’s heavier than v4?