This is some old draft article that I didn’t want to trash, so I’ll try to at least partially salvage it.
I played a bit with Deno deploy a while back, and I must say quite impressive that using Deno deploy is very easy to fast spawn a serverless worker, similar to a Cloudflare worker.
If I were to deploy something on a large scale where serverless workers could be a suitable environment as a replacement for a different backend set-up, and I had to choose a paid service, I would probably go with Cloudflare only because it allows the worker to be written in several languages, and thus gives you better flexibility. View full article
Somewhat of a month back I applied for GitHub copilot access, out of curiosity and I am using it since I got access around 11 June 2021. To apply for access you basically submit an application form, and after it’s reviewed you get an invite to a private GitHub repo, once you have access to that repo you can use copilot by using the VS extension and authenticate with the Github account that has access to that repo, be sure to change fast the issues watching level because it’s set to all and that will basically flood your email address with thousands of emails since it’s a very popular repo. View full article
When WSL1 first appeared I was pretty excited, a lot of people claim today that because WSL, Windows is the best platform for developers, personally these days I think any OS from the big three can act as a perfect developing platform since many of us use docker anyway.
But back to WSL1, what I really liked was the WSL1 was Cygwin on steroids a kind of “Linux Wine”, and that meant a lot from the perspective of OS development, because it really was a step in the direction of merging OSes rather than have yet another virtual machine.
I mostly switched to WSL2 because I grew tired of my applications crashing because WSL1 was missing some implementations, and I thought I wasted enough time on workarounds like setting Nginx buffering to off, replacing libc libraries, replace system binaries with custom scripts, replacing apt repos with custom ones, adding custom apt repos, changing network IP version preference, avoid using Unix sockets and so on and on(but even TCP wasn’t fully implemented, constantly you could bumble into TCP_INFO error), so basically WSL1 is not extremely stable. View full article
If you want to install Laravel on a RedHat 7.3 OS, you will have to use PHP 7.0.* as this is a Laravel minimum requirement, so this is the set of commands that I used in order to configure the needed software for Laravel. ( you can also download the set of commands as a text file below).
Also, I would like to mention that I generally prefer Nginx over Apache, and HTTPS obviously, but this is just a quick setup.
View full article
#--- AutoStart network interface
#--- Open FireWall 80
firewall-cmd --zone=public --add-port=80/tcp --permanent
#--- Check the updated rules with:(optional)
#--- Delete PHP 5.4
yum list php
yum remove php.x86_64