I have the mini version (with nginx). So no phpmyadmin.
But when I change the port to 3307, it gives me an error that Laragon can't find the phpmyadmin config.
(or perhaps it's a warning.)
Anyway, It runs on port 3307 after the change.
(so the warning/error just try to scare me, but I didn't fall for it hahaha)
Hi, Anyone can help me with this problem? "Laragon Detected Exceptions" This Message keeps popping up every time I click start. is it the root file problem ? (D:\laragon\www) I accidentally created another folder below the "www" folder but I remove it .
I Tried reinstalling it but still work the same. I asked some developers about this problem and the said that they haven't encountered this problem.
Since Laragon is a wonderful tools for... ehr... lazy people like me ( ), is there a way to add PHP to PATH environment variables (for using PHP in other consoles) from within Laragon or should I do it by hand? Thank you
The problem is resolved with command:
mysql_upgrade -u root -p --force
from the MySQL distrib folder (\laragon\bin\mysql\mysql-5.7.17-winx64 in my case).
While laragon is great abt watching for new alternative MySQL or MariaDB distrib folders added to \laragon\bin\mysql\ and setting up ini settings for MySQL, just to eliminate this handiwork, please add the command (mysql_upgrade -u root -p --force) along with my.ini settings out of the box.
Is it just me or does this forum make posting lots of config files etc. somewhat difficult? Specifically using MS Edge and pasting a bunch of config from cmder (it was an nginx.config) had the text area input thingo just go off the page with no way to scroll down below it to actually write what I wanted - my other post was done in Chrome
I'm using the "mail" driver on Laravel 5.3 (MAIL_DRIVER=mail in .env), and I use Laragon to "catch" the email instead of sending them.
The generated HTML mail is encoded in quoted-printable, so when I open it in browser it is unusable: I have to change the .html extension with .eml so I can open it with Thunderbird (or any other mail client) to see it working. (or I have to use setEncoder(Swift_Encoding::get8BitEncoding()) to bypass the quoted-printable encoding, but this is a Laravel related stuff)
Is there a way to automatically save a copy of the mail in .eml?
2.1.2 works fine on my computer but it confused me at first; specifically I installed over my current Laragon installation.
The relevant files (e.g. Nginx as I'd used the Nginx version) were installed but the application installer didn't seem to replace the installed laragon.exe as it claimed I only had apache.
I'm not sure of the fix here but maybe the installer could do something like:
"It looks like you've already installed Laragon at SOME_PATH - this is not recommended!"
"Do you really want to blow away the current installation at SOME_PATH?'
In other words I'd downloaded the new 2.1.2 Nginx full version and installed It over version 2.0.X (I think) but the installer didn't have the expected results. I did then install it to an entirely different directory and it works fine so there's nothing wrong with the installer as such.
I wonder if the default forum when making a post could be changed from Announcements to something else (general discussion maybe)? It's caught me out twice and I would suppose that "Announcements" are usually the lowest amount of posts.
Hey Leo, for some odd reason, I'm getting a SQL error when attempting to run Yetishare. If you're not familiar with what Yetishare is, it just turns any website into a file host, but with many more features. I'm not sure what's going on here and it could be related to Yetishare itself, but possibly the errors in the screenshot will shed some light on exactly what the problem is, as I have no idea. I've already tried to disable strict mode for MySQL.
I've followed the tutorial on how to set up Yetishare and everything in MySQL checks out just fine. Thanks in advance!
I think that Caddy HTTP/2 web server would make a fine alternative to Apache. It's little easier on memory usage and feels slightly snappier than Apache (could be placebo). Also configuring it feels quite easy.
Also it seems that Apache might have some problems with memory usage (atleast on my old dev environment)..
Usually memory usage is around 40-50 megs..but occasionally memory usage skyrockets through the roof and I'll have no choice but restart it