I agree. Currently, in order to setup a reverse proxy in either Apache or nginx I have to modify the auto-created vhost entry. I tried setting up a bash script to handle it automatically, but couldn't figure out how laragon is auto creating the vhost entries. So, for now i have to stick with the manual way.
Posts made by eddielee394
RE: Reversed proxy
Yarn - NPM - global package directory
This was already referenced in this post: https://forum.laragon.org/topic/553/don-t-want-to-use-appdata-to-store-npm-and-composer-packages
I'd like to accomplish the same thing - save global npm & yarn packages in my
laragon/data/directory instead of
@leokhoa mentioned that a setting to modify the global package path via the laragon menu would be considered for a future version. Has that been released yet?