I see you have no problem with the installation, but SSL. Comment the line about SSL in httpd.conf if you don't want to see Apache warn.
Posts made by leokhoa
RE: Every Laragon install ends in a disappointment
RE: Moving to a production server.
@cfree918 : If your production server is Windows. There are 2 easy ways to choose:
Method 1: Install Laragon on the the server. Then, copy www dir & data dir to it. With this method, the setup of Laragon will install any missing libraries needed to run PHP, Apache2,...
Method 2: Just copy Laragon folder to the server. That is.
For production, you should set Laragon auto run with Windows and auto run all the Services.
MySQL default password is empty, so you should set it to a difficult to guess one.
RE: laragon needed nodejs for 64-bit
Laragon use 32-bit nodejs & npm for portability (to work on both 64 & 32 bit Windows). This is helpful when you move/copy Laragon stack to another 32-bit Windows with no worry.
If you prefer nodejs 64-bit you can install it yourself easily, just download (https://nodejs.org/dist/v5.11.0/node-v5.11.0-x64.msi) and install to C:\laragon\bin\nodejs
RE: Sublime Text 3 as an inbuilt editor in Laragon as a replacement for notepad++
Many thanks for your post. I'm very happy when reading it
Sublime Text is great. However, I must ask them if it is OK to distribute. If yes, I will include it to Laragon soon
RE: A reference to Laragon in Styde.net. We are on the good way!
Wow!!! very nice article about Laragon in Spanish.
Thank you for your information
RE: Laragon and Let's Encrypt
@Kurre: You're right. However, when @askaoru asked about Let's Encrypt, I think he asking for using in production.
For localhost development, I see no reason to use Let's Encrypt and it is impossible because Let's Encrypt can not connect to localhost to valiadate.
If he need to use SSL on localhost, your self-signed certificate article is very helpful
Or he can use ngrok and tunnel https if this solves his problem.