You can read about Procfile here at Heroku: https://devcenter.heroku.com/articles/procfile

However, Laragon makes Procfile more convenient to use with GUI. On Laragon all processes on Procfile will be displayed on Menu > Laragon
Some other differences on Laragon are:

A process name can have spaces. For example: My Cool App You can add autorun to make the process auto triggered when Laragon starts You can hide (don't show Console) a process if you quote its command. For example: "php artisan serve" You can set PWD=xxx - xxx is Path of current processs You can have env_file=yyy - yyy is Path to your Environment File.

Here is format of a Procfile:

# Format: ; Program Name: autorun COMMANDS env_file=PATH_OF_FILE pwd=PATH_OF_WORKING_DIR ENV_VAR1=VALUE ENV_VAR2="VALUE WITH SPACE" # Help: ; Program Name: Will be displayed on Procfile or Tools' Menu (can contains space) ; autorun: Your COMMANDS will be run automatically when Laragon starts ; COMMANDS: A command or a series of commands (separated by & ) ; env_file: You can set environment variables directly or put them to the file ; PWD: Current working directory - where the COMMANDS run # Examples: ; My Cool App: autorun node start $PORT PORT=9000 env_file=usr\my_file.env PWD=usr/proj/myapp DB_HOST=1.2.3.4 DB_PORT=9999 DB_USER=user DB_PASS="!$Ab.cs3cre1" DB_NAME=cooldb ; Awesome Tool: "PATH HAS SPACES SHOULD BE QUOTED LIKE THIS" ------------------------------------------------------------------------------

Note:

pwd is case-insensitive. autorun is case-insensitive. Your env_file may look like this: VAR1="VALUE WITH SPACE" DB_HOST=1.2.3.4 DB_PORT=9999 DB_USER=user DB_PASS=!$Ab.cs3cre1

You can also add/update phpMyAdmin easily yourself. Just download from its official site (https://www.phpmyadmin.net/downloads) and extract to {LARAGON_DIR}\etc\apps\phpMyAdmin.
That's all.

Now, you can acess phpMyAdmin at:
http://localhost/phpmyadmin

Create this file trigger-php.bat in usr\bin:

\usr\bin\trigger-php.bat:

php trigger.php %PHP_VERSION% %APACHE_VERSION%

You can access PHP_VERSION and APACHE_VERSION through $argv in trigger.php in usr\bin:

\usr\bin\trigger.ph:

<?php print_r($argv); # YOUR CODE HERE

In you code, you can download correspond Apache version from http://www.apachelounge.com/download/ and extract it to bin\apache

With Laragon 2.1.0, you can use your favourite editor with Laragon and add it to the Right-Click Menu for quick access. In this article, we will add VS Code.

Download VS Code:
https://code.visualstudio.com/Docs/?dv=win Extract the downloaded to: {LARAGON_ROOT}\bin\code Open laragon.ini in Menu > Laragon > Settings file: laragon.ini Put Editor=PATH-TO-EXE under [preferences] [preferences] Editor=bin\Code\code.exe

Note: If you extract outside Laragon's installation dir, you must put full path. For example:

[preferences] Editor=C:\editor\Code\code.exe (Optional) Add to Right-Click Menu: Click Tools > Right-Click Menu > Add/Update Code & Terminal
Note: You must run Laragon as Administrator to do that.

Very easy huh. That's all forks!

Note: You may need to install VC Redist 2013 (64-bit): https://sf.net/projects/laragon/files/addon/vc_redist.x64.2013.exe

With Laragon 3, adding PostgreSQL is very easy.

Download PostgreSQL (64-bit zip):
https://get.enterprisedb.com/postgresql/postgresql-9.6.3-1-windows-x64-binaries.zip Extract the downloaded to: {LARAGON_ROOT}\bin\postgresql\postgresql-9.6.3-1-windows-x64 C:\laragon -- bin -- postgresql -- postgresql-9.6.3-1-windows-x64 -- bin -- include -- lib -- ............. Select the new version at: Laragon Menu > PostgreSQL > Version > postgresql-9.6.3-1-windows-x64

Very easy huh. That's all forks!

Note: When PostgreSQL is added to Laragon this way, it is also portable.

You can add Xdebug to Laragon easily.
Method 1: Using phpinfo() & Xdebug Wizard

Copy phpinfo() content:
http://localhost/?q=info

Paste the copied data to the form in the Xdebug Wizard page
https://xdebug.org/wizard.php

Click "Analyse my phpinfo() output", and follow the instructions.

Note: Their instructions will ask for "4. Restart the webserver" but with Laragon, you just need to click Reload button.

With Laragon, adding another PHP version is very easy. Here's how to add PHP 7.3

Download PHP:
http://windows.php.net/downloads/releases/

In this case we download:
https://windows.php.net/downloads/releases/php-7.3.0-Win32-VC15-x64.zip

Extract the downloaded to: {LARAGON_ROOT}\bin\php\php-7.3.0-Win32-VC15-x64 C:\laragon -- bin ---- php -------- php-7.3.0-Win32-VC15-x64 -------- ............. Select the new version at: Laragon Menu > PHP > Version > php-7.3.0-Win32-VC15-x64

Very easy huh. That's all!

Please be noticed about PHP Version (so you can add new extensions properly)

x64 means 64-bit x86 means 32-bit nts means Non Thread Safe

If something's wrong, please check and install correspond VC Redist (VC11, VC14, VC15...)

Re: [Tutorial] How to add phpMyAdmin

It's easy. Here how:

Open "Quick app > Configuration..." Add this line: WordPress BedRock=composer create-project roots/bedrock %s Now, you can create your project "Quick app > WordPress Bedrock"

That's all.

After installing, remember to update .env file
Note: if you project name is bedrock, Laragon will create a database bedrock so your .env will look like below:

DB_NAME=bedrock DB_USER=root DB_PASSWORD= WP_ENV=development WP_HOME=http://bedrock.test WP_SITEURL=${WP_HOME}/wp

Re: How to upgrade from Laragon 2 to Laragon 3

HI I have Laragon 2.2.2 NGINX and I tried to first install Laragon 3 BUT at this momento I do not find the Laragon 3 link to download.

Since I want to have Laragon 4, do I still need to install v3 (dollowing the steps in this topic) and later replace the laragon.exe ?

If so, kindly can someone provide a link to download Laragon v3? Thanks

The easiest way is:

Backup laragon.exe (rename to laragon.exe.bak) Replace it with the file download from github.com:
https://github.com/leokhoa/laragon/blob/master/laragon.exe

That's all folks.

Re: [Tutorial] How to add another Apache version

Adding another MySQL version is very easy and safe with Laragon.
Hint: This tutorial also applies for MariaDB.
https://downloads.mariadb.org/mariadb/10.2.6/#os_group=windows
[Download the MariaDB 64-bit version]

Download MySQL 5.7 (64-bit) or 32-bit:
https://dev.mysql.com/get/Downloads/MySQL-5.7/mysql-5.7.18-winx64.zip Extract the downloaded to: {LARAGON_ROOT}\bin\mysql\mysql-5.7.18-winx64 (see below Note for MariaDB) C:\laragon -- bin -- mysql -- mysql-5.7.18-winx64 -- ............. Select the new version at: Laragon Menu > MySQL > Version > mysql-5.7.18-winx64

Very easy huh. That's all forks!

Note: If you use MariaDB, extract it to: {LARAGON_ROOT}\bin\mysql\mariadb-10.2.6-winx64, Laragon will automatically create correspond DataDir for MariaDB on data/mariadb

Re: Your connection is not private

I'm experiencing the same problem as the related topic above. Only that I'm using a {project}.test instead of {project}.dev and I'm still getting the connection not secure error.

I have researched and tried every possible thing I could find but it doesn't seem to work.

Laragon screen.

When I click on "how to manage "quick Apps I get a page(https://forum.laragon.org/topic/1019) that reports:

Access Denied
You seem to have stumbled upon a page that you do not have access to.

Installing ImageMagick is really pain on other systems. However, it is trivial with Laragon if you follow these below steps (works with both Apache & Nginx):

Download links:
PHP Extension (PECL):
https://pecl.php.net/package/imagick/3.4.3/windows
Imagick Binaries & Dlls:
http://windows.php.net/downloads/pecl/deps

*IMPORTANT: Choose the right packages (version, x86 or x64, VC, Thread Safe (ts) or Non Thread Safe (nts)).
Even your OS is 64-bit, you should depend on the suffix -x86 or -x64 of the PHP version to select the correct ones.

To be more specific: if you are using php-7.1.7-Win32-VC14-x64 you should download:*
PECL:
http://windows.php.net/downloads/pecl/releases/imagick/3.4.3/php_imagick-3.4.3-7.1-ts-vc14-x64.zip
ImageMagick Binaries & Dlls:
http://windows.php.net/downloads/pecl/deps/ImageMagick-6.9.3-7-vc14-x64.zip

After downloading the right packages, the next steps are easy.

Extract: PECL: Extract php_imagick-3.4.3-7.1-ts-vc14-x64.zip to a tmp dir, then put just php_imagick.dll to PHP Extension dir (Menu > PHP > dir:ext) Imagick Binaries & Dlls: Extract ImageMagick-6.9.3-7-vc14-x64.zip to a tmp dir, then put all dlls in bin (CORE_RL_*.dll, FILTER_analyze_.dll, IM_MOD_RL_*.dll, ImageMagickObject.dll) to PHP dir where the php7ts.dll is located (Menu > PHP > Version > dir:php-7.1.7-Win32-VC14-x64)

Enable:
Just click Menu > PHP > Extensions > imagick

Restart Apache/Nginx

That's all forks.

This tutorial is for setting up WordPress in Laragon so you can test patches from WordPress Trac.

Prerequisite: you'll need Laragon WAMP, not just Laragon Portable. You'll need to run node and npm.

Create Development Site

Video: https://drive.google.com/file/d/12Y-7QRUpA6V1207fCDvxxG6kmgyRipY0/view

Open Laragon. Click Menu -> Quick App -> Blank. Name it "wpdev" Click "Terminal", and in the terminal type git clone git@github.com:WordPress/wordpress-develop.git wpdev and then enter (or git clone https://github.com/WordPress/wordpress-develop.git wpdev and enter your GitHub username and password) Copy {laragon}/www/wpdev/wp-config-sample.php to wp-config.php, and enter change the database name to be wpdev, and user to be root, with blank password Still in terminal, type cd wpdev, enter, then npm install && grunt build If using nginx, find{laragon}/etc/nginx/sites-enabled/auto.wpdev.conf (if using apache, use that instead) and remove auto. from its name. In that file, find the line that starts with root (or sometimes define ROOT), and add build/ onto it. In laragon, click "Stop All" and "Start All'. Now your copy of the development version of WordPress should be running at wpdev.test. Apply Patches Find the ticket from trac.wordpress.org that you want to apply, and take note of its ticket number From {laragon}/www/wpdev/, run grunt patch:{ticket-number}. Eg if you wanted to apply the first patch from [Trac ticket 43443](https://core.trac.wordpress.org/ticket/43443), you would typegrunt patch:43443`, and then it would ask you which one of the uploaded patches you'd like to apply. After applying the patch, you should run grunt build again (to re-sync the changes made to the src directory to the build directory) When you're all done testing and want to undo the patch, run git checkout .
See https://make.wordpress.org/core/handbook/tutorials/working-with-patches/#applying-a-patch for more information.

Example to run Sublime Text in CMD / PowerShell / Bash Terminal
No need to add Path anymore, hell ye!

%laragon_root%user\bin\subl.cmd

#!/usr/bin/env bash SUBLIME_PATH="$(dirname \"$(realpath\ "$0\")\")" SUBLIME_PATH="$(dirname \"$SUBLIME_PATH\")" SUBLIME_PATH="$(dirname \"$SUBLIME_PATH\")" SUBLIME_PATH=""$SUBLIME_PATH"/bin/sublime" "$SUBLIME_PATH/subl.exe" "$@"

%laragon_root%user\bin\subl.cmd

@echo off setlocal set SUBLIME_PATH=%~dp0\..\..\bin\sublime call "%SUBLIME_PATH%\subl.exe" %* endlocal exit 1

Re: How to Easily Change a WordPress theme using Laragon

Hi, Please help. I have followed this video in order to change the theme on my website. All has worked great until I needed to Save my Permalink Settings on my local duplicate site. I then discover that my login details are not recognised. I repeated the process and had the same luck. Both duplicate sites are saved to Laragon, but neither recognise my login information. Thank you soo much in advance for your help.

If your machine is behind a company proxy, you may not be able to download files using "Quick app" and "Quick add" features of Laragon.
With laragon 4.0.1+, you can overcome the limitation by using Proxy. Here's how:

Open laragon.ini in Menu > Laragon > laragon.ini Add Proxy=<host>:<port> below [preferences]. For example: [preferences] Proxy=206.81.6.31:8080

That's all.

Note: if you don't have a proxy, you can paste this link to your browser to get a free one (repeat the process until you find one that works):
http://pubproxy.com/api/proxy?limit=1&format=txt&https=true&country=US&type=http

Change country=XX to the country you prefer.
For more information, you can check this github:
https://github.com/clarketm/proxy-list