Thanks. That worked just fine!
Posts made by haakym
Updating Git in Laragon
How can we update Git that comes with Laragon:
I have the latest git installer for Windows. When running the installer it will of course install to
C:\Program Files\git, so I am wondering how to run this for Laragon. Is it simply a matter of copy and pasting the install files over from
C:\laragon\bin\git? Do I need to worry about whether the install is 64-bit or 32-bit?
The current version of Git for Laragon 3.2 is Git 2.9.0. As of Git 2.16.1 I believe it's possible to run
git update-git-for-windowsfrom the command line so this should be much easier process, however, I can't do that while on 2.9.0.
Any help would be appreciated.
RE: Different PHP version per project
@poxxac Leokhoa answered a similar question here: https://forum.laragon.org/topic/805/a-specific-php-version-for-selected-virtual-hosts/2
I am also looking into the apachelounge forums as there is some info there on using Apache modules (fcgi) to allow different PHP version per virtual host:
However, the forum post is old and I am unsure if the suggestions work in a Windows context but it may be a starting point.
RE: [SOLVED] XDEBUG & PHP 7.0.8
Got stuck on this myself (specifically running my laravel tests with xdebug from cmd line in vscode).
I was following this tutorial: https://tighten.co/blog/configure-vscode-to-debug-phpunit-tests-with-xdebug which is for mac/linux and as I'm using Laragon/Windows I ended up here.
I did add PHP NTS, but not sure that it was needed. I think it's most likely that the solution was by adding the following options as a minimum in
This post prompted me to add
xdebug.remote_host=localhostthe https://xdebug.org/archives/xdebug-general/1865.html which made the difference.
I also set the env var by running
setx XDEBUG_CONFIG "idekey=VSCODE", again not sure if that made the difference or not but was one step I took.
Hope this helps someone!
RE: laragon as system service
@tatoosh You can do it manually with instructions from our friend @leokhoa here: https://forum.laragon.org/topic/455/laragon-auto-startup-on-windows-server-2008/2
Cmder running global copy of npm not laragon's npm?
I updated Node by renaming the folder
c:\laragon\bin\nodejs_oldand downloaded a new copy of nodejs from the node website and dropped it into
Now when I run
node -vI get
v7.10.0which is great!
However, my npm version hasn't updated? When I run
npm -vI get
3.10.8is this running the global npm?
If I run
C:\laragon\bin\nodejs>npm -vI get
Any advice on getting Laragon/Cmder to run npm within Laragon, i.e.
RE: Laragon auto startup on Windows Server 2008
@leokhoa Thanks so much for your reply!
I'll look more into what these commands are doing before I use them and then try experimenting.
By the way, do you have a way Laragon users can contribute a donation to the Laragon project? I have benefitted a lot from this tool and the support on the forum is fantastic. I would be happy to make a small donation if possible. Thank you.