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.
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 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.
As you know seting CRON jobs are pain on windows. Is there a way to make it easy with laragon?
And for example on laravel you can create queue's as you know,
When you want to use need to run artisan command(s) and in real world example (as far as i know) on linux systems you need to set up supervisor service's for this type of things.
If is it possible laragon has able to handle with these it would be awsome ?
Blueprints for WordPress like "Local" (created by flywheel, if you can view a example of this feature). This option can create other fast installation from a original WordPress install (for example for test anymore without break the actual development). This option will copy all actual WP structure and database.
Disk space is not problem, but opening all log files with code/text editors. Almost impossible when log files are several hundreds MB.
I understand need for live servers, online servers and keep so huge log files. In case of for instance hacking you could check logs from months ago. And some other cases.
But when Laragon is used on localhost so huge log files are absolutely not needed. Do you have a problem with some website ? Just refresh this website, front-end or back-end. Open log files and read what problem is. Theoretically it is enough with log files of 1-5 MB in size. When developing websites you are only interested in latest log lines.
How to delete log files when they grow to one size, and continue making new one, and on and on ?
I tried "rotatelogs". Works somehow, but activate several new windows processes. And cannot delete old log files. So if you forget (and you will) you have this installed and set, subfolder with logs will have a chaos of new log files.