Fixed Issue with the service status in the context menu. Thanks @vienmq for helping addressing it.
From version 2.0.2, Laragon works with both PHP Thread Safe (TS) & Non Thread Safe (NTS):
PHP TS will be bundled by default for compitability.
However, just 1-click you can easily switch to PHP NTS to experience php-fpm with great speed & low memory usage.
I firstly want to thank @leokhoa for Laragon. Have been using it since laragon 0.4.
Saw so many features added to it since last year and so much rapid development. So many features that a Developer using windows machines has come to love and now can't live without.
Before Laragon I used winscp, putty,cmder, git,composer,npm and redis which I had to install seperately. Now I can just install laragon on a new machine and thats it, nothing to worry about
But there a request that i want to make , I am a sublime text 3 user and sometime use Visual Studio code ,but my main text editor is sublime text.
Can you please try to include the free version of sublime text 3 in Laragon. I think all will appreciate this addition to Laragon as sublime has a smaller footprint and will not affect the installer size of laragon by a greater degree.
I love laragon and want it to be the only thing i need to install on my system for my work.
Thank you making development so much easier on windows and with Laravel.
I have project locally that works only with https.
How I can configure localhost with laragon for this project. I change 4443 port of SSL to 443 -> redirect on index.php with phpinfo. Another if I don't change defalut ssl port of laragon - 443. f.e in chrome - Unable to access the site.
So I set up Laragon to use Auto create virtual hosts and created a new site. The new site shows up as a vhost in drivers/etc/vhosts and in httpd-vhosts.conf, however when I hit the URL for the vhost in my browser, i.e. mysite.dev, it redirects to an IP which doesn't mean much to me and the webpage that is shown to me for this IP is the root of Laragon which shows index.php at the root folder which spits out phpinfo(). I can however access the site using the standard URL: localhost/mysite/public/.
I am using Laragon at work and we have a proxy here, is that an issue?
Any ideas on what is happening here and how to remedy the issue?
I had done a scan on my site using SSL Checker and the following were found.
SSL 3.0 is an outdated protocol version with known vulnerabilities. How can I fix this?
The server supports some insecure SSL ciphers
I had try to disable in httpd.conf and httpd-ssl.conf by entering the following ;
SSLRandomSeed startup builtin
SSLRandomSeed connect builtin
SSLProtocol All -SSLv2 -SSLv3
Restart service and use the SSL Checker to check but still get the same result , anybody can help
Good news is that Valet is only for mac (for now).
Well I know this requires quite a bit of work
Does Laragon have plan on this? It will certainly push Laragon to a greater height in Windows developer group.
So I've been developing an app in Laravel on Ubuntu, and now I installed Laragon on my Windows, downloaded and extracted my github repo and started the host. And so, when I enter app.dev, I get two notifications 'Whoops, looks like something went wrong' and the 500 error. Where should I start looking for the solution of this problem? How do I deploy Laragon virtual host correctly?
I have a website I use the Laragon and my backend works correctly at http://localhost:8000 (when accessing displays "Laravel" on the screen), but for testing now I need to access another computer from my local network, I tried the IP computer that is the Laragon installed http://22.214.171.124:8000 and received a 404 error after it went on Laragon Apache folder and set the "Listen 8000" in http.conf file and access the address http://126.96.36.199:8000 receive the return of a phpinfo(), or does not work.
How do I outsource Laragon?
Trying to install newer apache but Laragon still points at some files from the older apache installation.
I found out, after renaming my directory to apache-2.4.18_64vc14_old, that when trying to run
apache-2.4.20_64vc14, this happens:
When I click on the Vhost file, is says that the file is not found.
(if I rename the old dir back to it's original, it is found. So it point at the wrong directory. But I don't know, how I can make Laragon look at the latest one. Where is that configured?