So, Laragon 3.0 was released, it has all the services in 64-bit by default and other shiny 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 successful installation, I start the program and click on start all to turn on Apache http server and MySql server.
As usual, I visit demo.dev 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 until the weekend when I was calm enough to look at the issue objectively.
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 HTTP Server 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
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 your database folders will have the same name as the 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 a 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, learnt anything at all, just share it with your friends on Facebook and Twitter. Let everyone know what quality content you read, especially in these days of junk everywhere.
Maven Central to the World, deploy your open-source Java library for other people to use in their projects as a dependency
Being able to read log files on a production server can boost the quality of your emergency readiness and response. Read on to learn how.
Why upload the file, when all you need is the data in it? Cleaner, faster avoid connection timeouts, corrupted data just by adding excel_uploader js
Export your MySQL database to a zip file, send the generated SQL dump to your email, Amazon S3, Google Drive etc. Plus automate the process #DevOps
Interacting with the Formstack API v2 just got better with this new fstackapi_php library. We'll use it to submit form dynamically and more
Here is a curation of the different technologies that power the web and the ones you should learn to make a living as a web developer
Ever wish there is a way you insert default data into the database during application startup in a SpringBoot environment? Read on!
We'll build a complete desktop application that'll translate English text to Morse Code and vice-versa plus an overview of Java GUI