I've done what the other thread says (thanks btw), but I cannot actually use it.
Putting in dep in Cmder outputs the same as the screenshot, and I can go to my project folder and create a deploy file with init.

However, as soon as that is there, whenever I use dep, it says either self-update (doing so gives the same message) or use php vendor/bin/dep, which outputs some stupid error code.

I understand that this isn't a laragon thing, but the official Github doesn't seem to be very helpful.

Update:
Okay, I've sorted it out.
For anyone who wants to do the same thing, follow the instruction in the link above, and make sure deployer isn't installed via composer globally or in the local directory (that was my issue).

Both would be best so I can simulate the real environments our code would run on.

PS. I love 💕 Laragon, great work. As a plugin developer who has nearly 600k sites using our products, its always been hard setting up local testing environments with mutliple versions of apache/mysql/php, have never had that issue with Laragon in the past 2+ years.

It would be really cool if you could import other manifest.tpl files inside a manifest.tpl file.

Importing should just copy over the content of the imported file and inject it into that position then.

This would be really useful for several uses, such as:

in the nginx.sites-enabled.00-default.manifest.tpl file (and the SSL one), being able to add/import your own server{}'s easily that are defined in manifest.tpl as well (so they can use <<LARAGON_ROOT>> etc)

being able to place all repeatedly-used lines (like for example the ssl lines in nginx sites enabled) into one file, to prevent it from being copy pasted everywhere

First time Laragon user here and I hit this annoyance. When trying to start all services, Apache wouldn't start. I changed the port but to no avail. Then I noticed the address Laragon was trying to bind to and it was one of my Vmware interfaces. The moment I disabled every other interface, Laragon started normally
I would like to request an option that allows to choose which interface Laragon binds to. I'd guess that a lot of us out there are using multiple interfaces and automatic selection is problematic.

Hi. I think as interesting feature if I can define in Laragon profiles for my applications where I can set servers versions. Example: To my application 'OsTicket' I set Apache, PHP 7.3 and MySQL 5.5, from my servers. They will be listed in menu and when I choose one, a server will be started with the profile servers.

1] WordPress has the 5-minute install for the specific reason that it should be accessible even for people without much knowledge. That install takes care of URLs & PATHs as well during that time, configuring the .htaccess and the database entries. So there's no need for any definitions in wp-config.php from the get-go.

2] By adding the ! defined( 'WP_CLI' ) you are forcing WordPress to always redirect to a siteurl & home that are not yet defined especially when an installation doesn't exist. There's no need to do that.

3] If you DO NOT use the Auto Virtual Hosts option and you want to use the http://localhost/subfolder scheme those defines will always redirect you to http://localhost/ ( there's no REQUEST_URI ) defined there so the full path is getting stripped off. This makes it impossible for people who are not fully tech-savvy to understand what is going on as their installation always ends up on a "Not found" page due to the wrong redirect.

I'm not really sure why those lines were added but there's no need to have them at all in my opinion .

You can of course continue to generate the wp-config.php and adjust the database credentials to make it even easier but that's about it, nothing else needs to be touched by default from Laragon itself.

I hope the above reasons make it clear of why those 2 constant definitions might end up doing more damage than good and you could re-consider on removing them on the next release.

Integrate Screenshot tool like Lightshot into Laragon for Better development. Most of the times, we debug the error, if we are tired, we will share the error through screenshot to your friends. So i think, screenshot tool like lightshot will be good choose to bundle into laragon.

I would guess many of us here are Wordpress developers. How many of us run a project and then have to add wp-admin in the browser to then edit the project? Surely there is a demand to add a parameter to the project url? (ensuring that it can be immediately after the url without a space ie ...projectname/wp-admin

Currently the default setting for the "www" link in Laragon's menu is to go straight to the installed WordPress project front (home) page. As far as I can find, there is no place to set the "www" link to go to the WordPress login page for any specific project.

Hence this feature request,

"Provide the option to set the www link to go to the WordPress login page".

Reason: installing WordPress onto a localhost environment is not for public access, it is primarily for development and editing. This requires our access to have the default location as the login page for the WordPress install, not the front/home page.

The featured "www option" allows us to set it to where we want to go each time.

Hi leokhoa thanks for this beautiful local development environment software.
I am using it from early release of this software.

I am wondering if you can make same for production vps server.
I is tedious to make production vps working with lots of commands and configurations, if you can make it automatic it will be easy to manage and monitor production servers.

For this feature i am ready to pay for software even others will also pay if you make it.

There is another software for production server management is claver https://getcleaver.com it is good software but has very less amount of features and not actively developed. As i know you are very active in community you can make it much better. I hope you can take it to higher level.