Feature request

[w3suli]

An option would be to have a unique work directory for a project. After entering the directory and domain name, the laragon could generate the necessary entries. As it does for libraries created in the www directory.

[leokhoa]

@w3suli : I will consider the feature. I'm thinking about improving "Quick app" feature. Something like this:

WordPress=https://wordpress.org/latest.zip root=the-directory alias=domain1,domain2,domain3

Ref: https://forum.laragon.org/topic/1379/multiple-domains-per-app-via-ui

[w3suli]

I was thinking of custom external projects. Your idea is good, but I thought:

(Optionally, even the database could be a field.)

Once you have entered the data, the settings could be automatically generated: -host -site conf -SSL (crt and key)

Internal projects:

C:\laragon\www\

www: -project1 (http and https root folder) -project2 (http and https root folder)

External projects:

C:\developments\ -project1... -project2...

C:\custom_path\ -project3...

project1: -public_html (http root folder) -private_html (https root folder) project2: -web (http and https root folder) project3: -htdocs (http and https root folder)

[leokhoa]

@w3suli : I see your point. It's very clear indeed 👍 However, it will make Laragon UI more complex.

[w3suli]

Simpler option: A simple menu item: Add External Project

So external projects would not be included in the Laragon menu. However, the required files would be created automatically.

• Windows...\etc\hosts (add external projects to the list)
• etc\apache2\sites-enabled\externalprojectname.conf (http and https settings)
• etc\nginx\sites-enabled\externalprojectname.conf (http and https settings)
• etc\ssl\auto.openssl.conf (and add external projects to the list)

[leokhoa]

@w3suli : That makes sense. I will consider it.

[w3suli]

Thanks! I think it would be a useful feature. This would easily add external projects to Laragon.