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.

Hey @leokhoa ,

I've seen on a previous post ( https://forum.laragon.org/topic/1273/notice-undefined-index-request_scheme-in-thrown-in-wp-cli ) that by default Quick App was adding

define( 'WP_SITEURL', $_SERVER['REQUEST_SCHEME'] . '://' . $_SERVER['HTTP_HOST'] ); & define( 'WP_HOME', $_SERVER['REQUEST_SCHEME'] . '://' . $_SERVER['HTTP_HOST'] );

Then it was wrapped with the if ( !defined('WP_CLI') ) { as well.

I'm not sure why those lines are added, but they shouldn't.

Here's why:

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.

Thanks !

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.

Let's discuss on it.

Hello, i very like use this service,
but i was looking to understand if was possible add some switch for autorun mysql - postgresql, like img

i know that i can use it from option, enable and disable it from service & port, but was more "friendly" if was in first page like image, from the switch if we have more sql can ON/OFF more easy.

atm i use mysql and postgresql, and i use togheter ON(like img), if we can switch in this way that is more simple, i can very appreciate it

then idk if is a bug or is normal, but if we put ON ssl, then click on padlock (green), it will disable SLL, but for active i need enable, is possible add a padlock(gray) and with a click enable it?

thanks always for your work and sorry to my bad english

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.

thanks.

Hi. Maybe you can implement a selective start, where we can select desired servers we want start, and its respectives versions.

I was wondering that in addition to ngrok we can also add support for localtunnel.me. It's pretty similar except that you can assign custom subdomain for free, which makes it possible to have the testing host same as the development site.

The syntax is quite simple:

> lt -p <port> --subdomain <name> --local-host <name> > your url is: https://name.localtunnel.me

Right now I'm using a bat file for this, but it would be a great addition to the menu also.

Thanks,
San

P.S. The full details are here: https://localtunnel.github.io/www/

Can you update CMDER to it's latest version please?

Can you add a similar functionality to user.cmd for Laragon Stop, to set a script to execute before Laragon exit?

Can you add auto set and unset Path Environment Variables on Start All and Stop actions as options in General Preferences for more portability?

I want to open terminal and type in something like this:

laragon add sitename --wordpress

And Laragon add new site automatically. Is there any way to do this. If not, is this planned?

I'm in the process of moving a bunch of sites to Laragon, and it's amazing to be able to quickly create a new WP installation, but after creating it I usually want to migrate an existing site to it, and most migration plugins only support migrating a site to another site with the same database prefix. It's not as simple as just renaming the tables either, because the prefix exists in option values within the tables as well, so I have to go digging for the prefix and change it manually. It would be super helpful if I could simply set the database prefix when I do the WP install.

It already creates an entry in the host file with the standard domain, is there any way to add another entry with www.

When would be MySQL 8.x.x supported in Laragon ?

Hello

Can you consider adding configuration profiles to Laragon, and a simple way to change between them?

Imagine this cenario:

In my WWW laragon folder i have two diferent projects, which unfortunately are not on the same PHP/MYSQL/APACHE/Whatever versions.

To work on each, i have to remember to first, change ALL those versions to the correct ones prior to access the site.

Could you make some sort of PROFILE available, that when we change it, also uses the laragon configuration associated.

Im guessing that if I have diferent LARAGON configuration file laragon.ini, i can excange them via a batch file.

But why not implement this directly on the LARAGON binary?

Do any of you see this as a usefull feature or is it just me?

Waiting your feedback.

I would like to have to install version Laragon for MAC. Any help for this?

It would be very nice if you could expand the list of laragon's cli commands with:

stop a single service laragon stop apache or laragon stop mysql or laragon stop (stop all) start a single service laragon start apache or laragon start mysql or laragon start (start all) change package versions (php, apache, mysql) laragon switch php "php-version-directory"

I did a test by changing the value of [php] Version = php-xxx directly in laragon.ini and launching the command laragon reload or laragon reload apache, but php remains in the previous version until I click on reload button in the main window aside the apache version, even though the notification above the clock shown that the apache service has been restarted.

I hope my feedback can help you to improve this great app.

Sometimes we need to create an application with multiple domain (multi tenant). Laragon come with automatic virtualhost detection, also by default it will create a wildcard alias in Apache configuration. I suggest to disable automatic wildcard ServerAlias, here is my reason:

We need to create an app with multiple domain, for example the domain are: example.test and api.example.test.

So, we have to create a folder with example for the name, so Laragon will create virtualhost example.testand wildcard ServerAlias, so we can use anything.example.test for the domain.

The problem is, if we create a multi tenant inside a subdomain, for example app.example.test, and api.app.example.test, ServerAlias give *.example.test, not *.app.example.test.