@leokhoa

Thanks. That worked just fine!

I guess another option is to update Cmder to use the system version of Git?

There's a discussion here...

https://github.com/cmderdev/cmder/issues/183

Hi,

How can we update Git that comes with Laragon: C:\laragon\bin\git?

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:\Program Files\git to 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-windows from 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.

Thanks!

@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:

https://www.apachelounge.com/viewtopic.php?t=6615

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.

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 php.ini

xdebug.remote_enable=On
xdebug.remote_host=localhost

This post prompted me to add xdebug.remote_host=localhost the 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!

@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

@leokhoa Thanks!

I updated Node by renaming the folder c:\laragon\bin\nodejs to c:\laragon\bin\nodejs_old and downloaded a new copy of nodejs from the node website and dropped it into c:\laragon\bin\nodejs.

Now when I run node -v I get v7.10.0 which is great!

However, my npm version hasn't updated? When I run npm -v I get 3.10.8 is this running the global npm?

If I run C:\laragon\bin\nodejs>npm -v I get 4.2.0

Any advice on getting Laragon/Cmder to run npm within Laragon, i.e. c:\laragon\bin\nodejs\npm?

Thanks!

@leokhoa

Thank you! Your efforts are greatly appreciated.

@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.