Working on this: https://www.prisonlegacy.com - Twenty-six years ago, a small Spanish studio shipped the most unusual PC MMO ever made: a maximum-security prison where every player is an inmate. La Prisión ran on community loyalty until its servers finally went dark in 2018. And we're bringing it back...
I like when projects like this mention other projects. "Phinx" (PHP) has been a breeze to work with for database migrations for years now, and handles more than my team needs. Meanwhile, some time ago a colleague in other job was raging they didn't have migrations but a chaos of DBs in their environments.
Indeed, made some preliminary tests under RHEL 9 (Rocky, etc) for example and if you're used to compile HAProxy from sources to use specific OpenSSL versions, testing "aws-lc" is fairly straightforward. Their BUILD instructions and INSTALL file from HAProxy also help.
Agree. But you need confidence on being able to debug / log / fix / revert, so having a strong knowledge of some of the parts is mandatory (i.e. server if it's web-dev, etc).
My experience: coming from programming in C, then doing web-scripting with Perl, then PHP 4 through 5, 7 and 8 versions, it's been delightful. Big improvements in speed, ecosystem, very nice backwards compatibility in general (which is hard to do), and keeps being a flexible, multi-paradigm language. About frameworks, you can do things now like-ruby-on-rails with Laravel, like-java with Symfony, or just use any custom solution you see to fit better for team/yourself. Mantra: you can do shit code with any language, and PHP is flexible enough to let you organize projects the right way.
Same here, PasswordAuthentication is globally No, but I always hold an special username for emergencies which is the only user allowed to login via password (easy at sshd_config file, Match User xxxx then "PasswordAuthentication yes"). Besides emergencies, also works wonders when some sysadmins insist to login via bare metal terminal and cannot use a key...
Same here, gource did help to visualize a complete revamp / refactor of a software, from the current mess by that time, to the final, pratically complete rewrite it was (through a process, since keep it working was mandatory). Really interesting to see the "mess" mutating into a more organized file struct, etc.
Well, in my particular experience with juniors, it's astonishing the so many ways they have to make any code run slower than it has to be (besides the network and database queries), just by thinking 'nah, this is a computer and it can do millions of ops by second'. And that's why I always take the "premature optimization" dogma with a grain of salt while my life's miserable enough having to accelerate some other's stuff.
Same here on using lsyncd and restic. Curious about the LVM+rsync method for nightly? My two cents: ReaR (Relax and Recover) for Linux for raw moving servers has saved me a couple of times.
>Skip low level and go as high as you can. Ditch C, assembly, hardware. Take python, ruby, js. Never touched C++ cause it’s awful? Good.
In my personal experience, I think that having to work on different high AND more low level programming languages over time is what sets me apart from people/coworkers with low basic knowledge of computer foundations (the order in my case being Basic, Pascal, C, Perl, C/C++, PHP, JS, etc). Also it depends on the projects, but just my two cents.
Those comments are nice to read. I tried, but my coworkers are too "young" or from other generation, I guess. The response [about simply buying a book] was "Oh, another person said it wasn't needed [to buy a book about that] since it will always be behind newer versions coming"...
Interesting. Just for sharing, for backup on Linux I've been using rsnapshot, restic (which accepts Rclone as interface) and ReaR (Relax and Recover) for full linux recovery; on Windows, commercial Acronis and recently UrBackup. Old good "pathsync" from Cockos also helps on LAN.
Everything boils down to your amount of files or GBs when some solution becomes "too slow" doing incrementals and/or file processing. My two cents.
Ummm no, but just to give credit, I'm using lighttpd for production for years now and happy with latest patches and stuff (supports HTTP/2 and several improvements over time), give it a try
As others have commented, my team at work use SVN because it's what somebody is confident to manage with svn+ssh protocol and want to keep it internal. Some projects use a "release" branch to which we merge when deploy is sensible, most projects haven't this branch and is just "trunk"/master. No more is needed. SVN works.
Not showing him as cast of terminator 2, his most successful movie, is bad, but not showing him as cast of CONAN THE BARBARIAN -the 1982 movie- is worst!!¡
My opinion is that too often we say "good enough" performance, let's optimize later if this degrades overtime... And there we are, sometimes creating time-bombs of performance degradation just for the sake of delivering features the faster the better... When you have to clean up and refactor other people mess because it's a clusterf*ck of "just works", you begin to appreciate some basics rules and "dont's" about doing things in software