@Some-T For that, you'll need to add some rules to Apache's .htaccess (In project).

Something like this (most simple way to do this):

<IfModule mod_rewrite.c>
    RewriteEngine on
    
    RewriteCond %{HTTPS} off
    RewriteRule (.*) https://%{SERVER_NAME}/$1 [R,L]
</IfModule>

Depending what you'll need/want, you might need to tweak this a bit. You could add these to .conf file created by Laragon, but it would get overwritten in case you choose to regenerate those confs.

If you're using Nginx, you'll need something like this: https://bjornjohansen.no/redirect-to-https-with-nginx (I don't use Nginx currently, so I can't give specific instructions).

And of course, you'll need to enable SSL and auto-generate options in Laragon.

I kinda like this idea (it reminds me of cPanel's MultiPHP feature, or Plesk's way to handle these kind of things per site/domain) and have few times actually hoped that there would be this kind of feature.

Even if this wouldn't be a part of Laragon, I'd like to chime in with few observations.

After thinking this a bit, I think there might be some problems which could cause some difficulties with implementation.

Let's say I have 2 different projects:

• Project 1
  • PHP 7.2
  • MariaDB 10.2
  • Nginx 1.13
• Project 2
  • PHP 5.6
  • MySQL 5.6
  • Apache 2.4

How would Laragon handle this kind of thing if I'm working on these projects in the same time?

Option 1
Laragon would load PHP 5.6 & 7.2, MySQL 5.6, MariaDB 10.2, Nginx 1.13, Apache 2.4 etc. daemons to memory? This would probably cause some conflicts and use lots of resources. This is the way cPanel and Plesk are handling these kind of situations (designed to work in this way), IIRC (with a smaller set of options to choose from).

Option 2
Laragon would hotswap daemons depending which site we are loading, but this would probably be very slow and inefficient way to handle this.

Option 3
Laragon would give you an option to choose which project is active (only 1 active project) and load daemons which are needed.

Option 4
Something else?

What if I have 20 projects which all have slightly different setup? Let's say total of 6 different PHP versions, 4 different HTTP daemons, 3 different DB daemons, etc. You get the picture

Option 3 would probably be the easiest way to do this, even though it would decrease Laragon's flexibility a bit.

Changing browser will (probably) work only for a limited time..

As mentioned, .dev is a gTLD and it's been added to HSTS Preload list.
All major browsers are using that same list (afaik)
https://hstspreload.org

So it's only a matter of time, until (all) other browser have updated to this latest list.

When I first heard about this .dev gTLD, I started to anticipate this kind of situation and changed to .test domain (which is valid TLD meant for development). It took some time get used to it, but nowadays I have no problems using it.

Only problem is that I need to add leading slash to make browser understand what I want (load page instead of searching..)

One could argue that this is a bad move, and I mostly agree..but I have better things to do, than worry about this kind of small(ish) changes

It's probably due this Chrome change: https://ma.ttias.be/chrome-force-dev-domains-https-via-preloaded-hsts

So changing hostname to use .localhost or .test gTLD should solve this issue.

edit: Maybe I was too quick to reply..dunno if this is the root cause of this, but it doesn't hurt to try

@P-Mo said in Laragon and Let's Encrypt:

Hello guys,

was there any radical change in how certificates are automatically generated for virtual hosts? For me everything seems to work (Apache 2.4.29, PHP 7.1.11) but even after adding generated certificate to Chrome, I get error NET::ERR_CERT_COMMON_NAME_INVALID

This server could not prove that it is newblog.dev; its security certificate is from [missing_subjectAltName]. This may be caused by a misconfiguration or an attacker intercepting your connection.

@P-Mo check this out https://forum.laragon.org/topic/493/self-signed-cert-not-working-due-to-chrome-latest-update

Maybe future Laragon version will handle this stuff automatically 🙂

@skeith22 Maybe https://forum.laragon.org/topic/493/self-signed-cert-not-working-due-to-chrome-latest-update/3 this would help?

Re: How to install Laragon in Linux operating system? as a reference.

Just started to wonder if there is any plans for a Linux version of Laragon?

I've been using Valet for Linux, LAMPP, Docker, Vagrant, etc..but IMHO those haven't been able to give as pleasant experience as hoped for, like Laragon has given, while developing web apps.

Truly isolated environment with easily swappable PHP/MySQL/etc version is what i'm missing atm

If you happen to plan Linux version of Laragon, I would be glad to help in any way I can.

@nate Hmm, can't really say for sure, as I haven't used BS for a long time.

But, reading http://getbootstrap.com/components/#glyphicons-how-to-use tells me that those fonts should be included in the Bootstrap CSS and loaded via @font-face. And that it tries to find & load those fonts from the ../fonts/ directory, relative to the compiled css file.

So, if you compile your CSS to /css/dist/site.css, it'll try to find those fonts from the /css/fonts directory. Thus that path.
And that extra slash shouldn't make any difference.

@leokhoa said in Composer by performing the following error shows:

@sajjadkazemi10 : Did you edit your PATH manually?

1. First, use Laragon to clean your PATH: Menu > Tools > Path > Remove Laragon from PATH
2. Add to your PATH C:\Windows\System32
   Right Click on My Computer, then click Properties, followed by Advanced System Settings > Environment Variables, look for the Path System Variable

As a side note, RapidEE is an excellent app for managing Windows environment variables
https://www.rapidee.com

Personally I've been using Ansible lately, and it makes many things very easy. But you first need to familiarize yourself with it and find/build needed Roles/Playbooks/etc to make everything nice and smooth. Initial step might take some time (well that's probably true with any new tool..)

There's lots of Ansible Roles available in Ansible Galaxy. Personally I've been using Roles made by geerlingguy + own custom ones (for PPA's, personal settings, etc..)

Alternatives to Ansible could be Chef, Puppet or Salt, but I haven't used any of those.

There's also some online services available, which could do the provisioning for you, like Laravel Forge, Serverpilot or some other service which offers similar features (if you don't mind paying few bucks a month for it).