3 ms·
Disagree! I'm normally all for easier entry points, but ssh login to running instance using curl to download the gcloud sdk tar to unpack sudo to insta
by grx 9y ago
Disagree! I'm normally all for easier entry points, but
ssh login to running instance
using curl to download the gcloud sdk
tar to unpack
sudo to install
systemctl to start local processes
useradd dedicated www
chmod and chroot to allow access
rsync to tranfer files
are absolute basics of system administration.
People who cannot even handle those tasks should not use a root server for their project.
There are alternatives to a full system, if running a single app with a database is your use case. Be it Heroku or Lambda, there are solutions that do not need administrator knowledge to run an application.
To add to this, servers that are lousily configured because some developer did not know what platform to use damages the infrastructure as a whole. They are broken in, used for spam or data theft if the application has some user base. If you know someone who does not know how to handle a system, please advice them to either coop with an admin or to not use a full system for their project.
- Bartweiss 9y agoSomeone who doesn't know how to do those things probably shouldn't be administering an important server themselves, agreed. But there's still a lot to be said for putting up a Hello World webpage locally, or making minor tweaks on a system formally run by a sysadmin. My concern would mostly be that the list above is unacceptable for learning, not for usability. That's ~8 different tools to learn from scratch, totally independent of the underlying project. And sure, most devs will eventually know all of those tools (or equivalents) without much conscious effort. But there's a lot to be said for scripted introductions to complex systems.