Hi, when using CMSes, probably the best server to use to date is OpenLiteSpeed, because it is famous for its support for large amount of requests per second, memory caching and updating static and dynamic content. I hope this is possible.
I'm working as WordPress trainer and would like to recommend Laragon.
But for beginners (and most of my trainees are real beginners!), there are 3 open points for me:
1.) Please make removing/deleting a project available as menu item!
(Manually deleting www folder + database + don't know about hosts etc. is too complicated for beginners. And after installing a WordPress site in Laragon is so easy, removing it should be easy too.)
... a really needed feature!!!
2.) Please make phpMyAdmin "1 click" available!
(The manual install works, but is also too complicated for beginners. HeidiSQL works, but for training I need phpMyAdmin which is pre-installed in most shared hosting environments.)
3.) "portable" seems a bit strange when using an installer which (Laragon 3.5) also demands a restart of the computer ... (How can this be portable?)
Maybe more information during the installation about which changes causes the demand of a restart?
And/or less installation dependencies and more self-contained, really portable run-time components?
Love the great work & effort you've been putting into Laragon!
Behind huge company proxies it can be difficult to use mail trap / send services as they generate traffic which is frowned upon by company IT.
But there's a locally available alternative to these online services, which can happily introduce chaos in to the connection as well. It's called MailHog https://github.com/mailhog/MailHog
It's got ready made windows binaries as well which can be configured by the command line or environment variables.
I don't presume to know how much work goes into on-boarding a tool like mySQL or any version of php for that matter, but It doesn't seem as the hardest challenge in the basket
Hello Mr. Leokhoa,
First of all, please accept my thanks - a great product. Excellent balance of functionality and portability.
Could you please answer - is there in your plans an extension of the functionality by adding a PERL language?
I will be grateful to you for your response.
Thank you for creating Laragon with Go . I really appreciate it because I am training myself of this language both for web development and general-purpose programming using Laragon. In addition to Go, Rust is one language that I am learning too for similar purpose. They compete each other as being developed by two biggest internet browser developers (Google and Mozilla). I believe that both languages deserve same chance in coming to this Laragon family. I hope that there will be Laragon Rust in the next version
How about a clone function in Laragon? What's missing from my workflow is the ability to clone a website. Something like this:
First thing - In Laragon I'd like to be able to select an existing website > Clone > Enter new Project Name (URL) and voila! New website.
Second thing - In Laragon, select an existing website > Save as Template / Blueprint. Then when creating a new project I can create a new project and select a Template / Blueprint and voila! New website based on a pre-existing website.
For me this is specific to WordPress, my business has three major services of which one is building turnkey websites for businesses and a lot of the initial setup etc. e.g. Installing WordPress setting up starter theme, mu plugins, etc. etc. and this will save a lot of time.
Anyone have any suggestions to make this even better? Please join in the conversation.
URL works fine with mobile. Windows 10 tablet, a bit frustrating. Choosing one app from store that works among a few...found one that will work if the URL includes the http:// prefix in the QR code like:
Is there a way to have a global php.ini file that is included in all versions?
I have a multi-version PHP setup with Laragon 3.1.8, and for each new version, I edit the new php.ini directory to set certain INI settings back (max_execution_time for example). It would be great if we could have a /etc/php/php.ini file that is always included in addition to the default php.ini file.
Appreciate your time reading this and if you could shed a light.
I think Laragon would be great for simplifying the process of setting up a dev environment for WordPress core contributing.
WordPress' recommended way of setting up a local development environment for contributing to WordPress core is pretty involved (see https://make.wordpress.org/core/handbook/tutorials/getting-started/#setting-up-your-development-environment) and I think Laragon could make it a lot simpler.
I was thinking of creating a fork of Laragon that:
-already has a WordPress site setup from the development repo (ie, git://develop.git.wordpress.org/)
-has phpunit setup
-runs npm install && grunt build && grunt watch on startup
This way, folks could just download this version of Laragon, and then start contributing code or testing Wordpress core patches, without so much hassle.
Any thoughts on how to implement this? I was thinking of:
-forking the github repo
-in the fork, create the site and database and commit them
-also add support for phpunit, and probably wp-cli while I'm at it
I think that post this before, but i dont remember...
With this new update, Laragon is the best option for local server compare with xampp or wamp.
I discovered the new update thanks to my email, but not because of the use of laragon.
Laragon should have an update notice and its update notice should only warn of news. For bugs or other fixes, you should link to the website forum
Thank you for your great work. After testing several local servers, Laragon is the best. It's portable
I'm going to create a platform for web development courses, and Laragon is going to be everyone's choice. It works on very low-end computers like BBEN MN9 (I have connected it to my 40-inch TV and work on it)
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.