Moving from Laragon 2 to Laragon 3.0 : My Telltale

This is how I migrated my data and the undocumented changes I discovered

So, Laragon 3.0 was released, it has all the services in 64-bit by default and other shinny new changes. The news was on and oh yea! I want one. In a jiffy, I downloaded the distributions for wamp, nodejs and java.

Then began my travails:

I did not read the release notes or any migration guide. I installed the new program blindly. After a successfully installation, I start the program and click on start all to turn on Apache http server and MySql server. As usual, I visit in my web browser, and I got database user error. So, I thought, the user doesn’t exist yet; let’s create it.

I visit http://localhost/phpmyadmin to create a new database user alas! I was met with a 403 Forbidden Error! How can I be forbidden in my own local dev environment? My projects, my databases! I scrambled round folders and config files, trying to fix this seemingly small issue and yes I was able to fix it the second day? No! Not at all. It lasted till the weekend when I was calm enough to look at the issue objectively.

What I learnt . . .

  1. phpmyadmin has been replaced with HeidiSQL. So http://localhost/phpmyadmin has been replaced with http://localhost/adminer. Although, the phpmyadmin folder yet exists, apache has been configured to deny access to it by default.
  2. The data dir now has a mysql folder where your mysql data, preferences and database folders are stored.
  3. Read other changes in the release note
The new HeidiSQL Management Console. Database name’s striked out

Moving your database. . .

Just in case you find yourself in my shoes, do the following:

  1. Move your database folders from c:\laragon\data to c:\laragon\data\mysql
  2. Note that the your database folders will have the same name as your database names that you see in phpmyadmin
  3. Do not move the default mysql database folders like test and performance_schema. They will already be in the destination folder c:\laragon\data\mysql
  4. There will be another mysql folder (c:\laragon\data\mysql\mysql) in the destination folder. It is for the mysql database that has the mysql user table and others. Just leave it as it is.
  5. Copy this singular file ibdata1 from old c:\laragon\data to new c:\laragon\data\mysql. This will ensure you don’t get errors like ‘database doesn’t exist in engine’
  6. If you start HeidiSQL now and logged in as root user, you will see all your database tables with their data. If you try to create a new database user, you may be met with an error indicating the user table need repairing.
  7. To repair the table, run this SQL REPAIR TABLE mysql.user then create a new root and other user accounts as you want. Create a new user account before closing the application to avoid being locked out

If you are new to Laragon altogether, start by reading this intro article here.

That’s about as much as it gets. If you find this post helpful, remember to heart it for others to see. Oh yea! Facebook and twitter share as well.
Thank you.