Yeah, I'm full stack. But for other reasons. Mainly because I do most of my full stack work out of home, not from work. At work, I'm like most, working on the narrow field I'm tasked to, and that is relatively shallow, we have staff dealing with the stack around my little corner.
But at home, well, I have kept in service junk IT from work as servers that provide services to clubs and societies I work with and they are full stack by definition, including gateway and LAN which is broader even than full stack, maybe we should call that the full schemozzle? ;-).
And one of the drivers of course is a fashion and interest in getting away from the big players. That is Amazon, Google and their ilk out of data ownership and privacy concerns. In fact looking into using Google indirectly, mainly for cloud backups, but hoping for encrypted.
And so there's a Nextcloud here, and a few Django sites among other things running on a handful of servers.
The most common stack then that I work with closely isn't LAMP or MERV or any other funky fashion but LLUPP - an if you never heard of that it's because I made it up, but it's a thing and if it ever takes off, I was there first ;-)
And so it's a direct derivation of the LAMP acronym (Linux, Apache, MySQL, PHP), but uses better tech (Linux, Lighttpd, Uwsgi, Python, Postgresql) ...
Apache is a mystery to me. Every single benchmarking of Apache vs. nginx and lighttpd sees the latter two on par kicking Apaches ass on every single measure, no surprise for a web server that takes its name literally from an intentional pun: "A patchy web server" and that shot to popularity on the measure mainly of being FOSS. The nginx boom is a mild puzzle, given it's not FOSS but freemium, and lighttpd is FOSS and performs just as well on every measure (both are ground up rewrites). I'm guessing marketing and time to market maybe.
Truth be told though I use lighttpd primarily because I use OpenWRT on my routers as best I can, and it runs lighttpd, and fulls stack and all I still don't need to spend time on different web servers unnecessarily ... much rather I tend to add lighttpd support to exiting services (run Nextcloud and Django under it neither support it, they both support Apache and nginx so I'm on my own).
For the rest, well I just landed with Django over PHP and hence Python/Uwsgi as the framework and again while I have some PHP (Nexctloud is PHP for example) I bias toward Django services (host a club site under tendenci).
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Yeah, I'm full stack. But for other reasons. Mainly because I do most of my full stack work out of home, not from work. At work, I'm like most, working on the narrow field I'm tasked to, and that is relatively shallow, we have staff dealing with the stack around my little corner.
But at home, well, I have kept in service junk IT from work as servers that provide services to clubs and societies I work with and they are full stack by definition, including gateway and LAN which is broader even than full stack, maybe we should call that the full schemozzle? ;-).
And one of the drivers of course is a fashion and interest in getting away from the big players. That is Amazon, Google and their ilk out of data ownership and privacy concerns. In fact looking into using Google indirectly, mainly for cloud backups, but hoping for encrypted.
And so there's a Nextcloud here, and a few Django sites among other things running on a handful of servers.
The most common stack then that I work with closely isn't LAMP or MERV or any other funky fashion but LLUPP - an if you never heard of that it's because I made it up, but it's a thing and if it ever takes off, I was there first ;-)
And so it's a direct derivation of the LAMP acronym (Linux, Apache, MySQL, PHP), but uses better tech (Linux, Lighttpd, Uwsgi, Python, Postgresql) ...
Apache is a mystery to me. Every single benchmarking of Apache vs. nginx and lighttpd sees the latter two on par kicking Apaches ass on every single measure, no surprise for a web server that takes its name literally from an intentional pun: "A patchy web server" and that shot to popularity on the measure mainly of being FOSS. The nginx boom is a mild puzzle, given it's not FOSS but freemium, and lighttpd is FOSS and performs just as well on every measure (both are ground up rewrites). I'm guessing marketing and time to market maybe.
Truth be told though I use lighttpd primarily because I use OpenWRT on my routers as best I can, and it runs lighttpd, and fulls stack and all I still don't need to spend time on different web servers unnecessarily ... much rather I tend to add lighttpd support to exiting services (run Nextcloud and Django under it neither support it, they both support Apache and nginx so I'm on my own).
For the rest, well I just landed with Django over PHP and hence Python/Uwsgi as the framework and again while I have some PHP (Nexctloud is PHP for example) I bias toward Django services (host a club site under tendenci).