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.
I imagined that I can create separate environments with Laragon. Each project has a main configuration file (.lrgn or a conf.json) and that file contains like below (as if Docker).
This configuration file makes a Procfile or something different - I dont know. It could be hyper-super laragonization. And I can select which projects I want to run.
And they can run both - I think.
name: "Server 01"
host: "it-looks-good.oo" # prevent redundancy
nginx: # call nginx -p ./www -c ./nginx.conf
host # makes a configuration file and it will be including
proxy: # not necessary (ex.: a node app is runnig)
ssl: true|force # make a certification and then add it to Certification System
setup: # https://nginxconfig.io/?file_structure=modularized
server_tokens: on # rewrite defaults, custom settings are writable
node: # runs versioned node
mysql: # call mysql --defaults-file=./my.ini --host=it-looks-good.oo --port=3308
version: "5.7.21" # load mysql from versioned folder
port: 3308 # prior port scanning
pass: "rootpass" # makes a password to the root user
php: # call php -c ./php.ini
version: "7.2.4" # load php from versioned folder
setup: # not necessary
mail: # call mailhog, hmail
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