steep hawk
I currently have a client who asks me to work on many different things. One of those things is a Laravel web app that the previous developer walked out from. I don't have a lot of experience with the Laravel framework so I'm trying to do the best I can.
The other day I had to move MySQL database from an Amazon RDS server to a local one. I'm used to working with MySQL databases so I moved over the database table for table and changed the .env file to reflect the new database location.
When I reloaded the app, it simply crashed with a 500 error. When I changed it from production to local so I could get diagnostics on the app in the .env file, I reloaded the site and found that a crucial array was not identified.
I don't have any idea where this variable ($school_info) is located because that was declared by the previous developer before I came onto the job. What I can say is that when I place the .env back to the original RDS database location, this problem goes away and the site loads right up.
I imagine that this is some kind of a cache issue like parts of the code are still looking for dependencies in the old location and not finding them. I can't be sure. What I know is that all my googling has come to nothing and this is primarily because I'm not working with Laravel in the local environment but in the production environment and therefore, can't use PHP artisan commands. I also have just opted to delete cache files altogether and found that that does not correct the issue.
I've looked into database migrations in Laravel and don't fully understand them. To the best of my understanding, all they do is provide seeds for starting new databases in other locations. But in this case, I'm not throwing any data away. I just want to keep all my data exactly the same and put it in a new location.
Can anyone tell me what I might be missing?
rough latch