How about a clone function in Laragon? What's missing from my workflow is the ability to clone a website. Something like this:
First thing - In Laragon I'd like to be able to select an existing website > Clone > Enter new Project Name (URL) and voila! New website.
Second thing - In Laragon, select an existing website > Save as Template / Blueprint. Then when creating a new project I can create a new project and select a Template / Blueprint and voila! New website based on a pre-existing website.
For me this is specific to WordPress, my business has three major services of which one is building turnkey websites for businesses and a lot of the initial setup etc. e.g. Installing WordPress setting up starter theme, mu plugins, etc. etc. and this will save a lot of time.
Anyone have any suggestions to make this even better? Please join in the conversation.
I've built the pcntl exension to work with PHP 7.1 64-bit on Windows. The extension is compatible with Unix pcntl api, but is not functional yet as it will take much time to convert Unix's signals to Windows procees model.
However, you can add it to your PHP's extension to overcome the extension-missing stopper.
for your information, they took .app from us too, Chrome add https:// in front of the hostname.
So, here are the candidates:
For you guys who still fall in love with this domain, you know what? .dev is like your ex-girlfriend, no matter what, how much she changes or hurt you, you always want to come back to her.
if that's what you feel, i suggest you to follow @leokhoa suggestion, use Vivaldi browser, it's a chrome-based browser. Watch the video and you will fall in love with it.
I guess, you can use this domain when you want to give some example.
I have no idea with this one, but here it is.
.invalid" is intended for use in online construction of names that are sure to be invalid and which it is obvious at glance are invalid.
I don't have idea
IMO, this one is unique, thanks to @Athlone for the idea, you guys can use this in honour of Laragon.
.localhost / .loc
Since our development running in local, i guess i can agree with this, but the .localhost is too long, i guess, i will stick with .loc.
TLD has traditionally been statically defined host DNS implementations as having an A record pointing to loop back IP address and is reserved for such use. Any other would conflict with widely deployed cod.
This one is good too, and emphasized our application is in test/development environment. Almost the same like .dev right?
".test" is recommended for use in testing of current or new related code.
Do you have unique gTLD? Then tell us! Mention your idea, and i will update the list.
As per the latest chrome update which made any local site end with .dev extension force it to redirect to https so they give error and can't view them in chrome, How I can change the .dev extension with .test to be able to continue developing usin chrome? I changed the .dev to .test from the preference - general but it didn't work for me. @leokhoa
2017/12/07 06:50:36 [error] 6704#7024: *107 directory index of "C:/laragon/www/oto/public/panel/" is forbidden, client: 127.0.0.1, server: oto.dev, request: "GET /panel/ HTTP/1.1", host: "oto.dev"
I took it from error.log from nginx. Its laravel project. I can connect home or login but not that one. I don't understand and dont know what to do. I tried lots of things and checked all 403 errors. Nothing happened. Please let me know. If you have any idea.
Hi! Not all the predefined quick create projects work for me. What happens is that the database gets created, but then there is no progress on the download bar, even if the file has finished downloading and can always be found in laragon/tmp/downloads. The quick create process does not continue to extraction.
This problems occurs for projects based on these archives:
The archives behave the same way (same problems / success per archive) if I upload them to my own server, which makes me believe it is related to the archive file size. The files that do not work are all more than 10mb, while the ones that do work are 8,5mb and 4,10mb.
I have been working with this for two week now and the only item I can't get to seem to work is Logging. Pages load just fine so it isn't a permissions issue. It simply isn't logging. I have my log level set to debug and my log set to single. It SHOULD be writing out a file to storage/log/laravel.log yet it doesn't.
When I set up the mail driver to "log" it simply never sent the mail and still no log file.
I have tried manually writing to the log through tinker and through a controller and it doesn't fail but the file is still not there. I have changed the permissions to be as lenient as possible and still nothing. I created an empty laravel.log file and still nothing.
There is ssh support so the only thing that's missing is to have the option to include host file entries with www. prefix. Some projects have htaccess redirect from non-www to www address and having host file entry would save the manual trip to add it.
With Laragon changing technologies is super easy. Just few click and we are ready to go. Also we can have multiple in-memory cache systems, and multiple database systems! In additional we do not need to install others progams - laragon brings everything you need (for example HeidiSQL).
Developing with Laragon is just awesome You don't need Docker anymore.