Have you used Git or file versioning or anything like that? Or you could do a new laravel project and just re insert the database files, if you are not using them it don't really matter as long as it makes the rest of your app work. Sorry if thats not a very specific solution.
Apr 30, 2018
3
Level 5
Deleted "forge" db, refusing to connect now
This Laravel app does not use a database - never ran php artisan migrate, and it was working just fine until deleting the "forge" db... now it's "refusing to connect" when you visit the page.
Update I created a new db and db user, configured in .env, cleared config, migrated, restarted nginx and it works now. Thanks Cronix!
Level 67
Another option is to go into the forge control panel, go to the affected server, and recreate the forge db using the same user/password in the MySQL section of the server details.
1 like
Please or to participate in this conversation.