You are viewing a single thread.
View all comments View context
42 points

manually FTPing the files up to the server seems ridiculously antiquated

But … but I do that, and I’m only 18 :(

permalink
report
parent
reply
28 points

Old soul :)

permalink
report
parent
reply
14 points
*

That’s probably okay! =) There’s some level of pragmatism, depending on the sort of project you’re working on.

If it’s a big app with lots of users, you should use automation because it helps reliability.

If there are lots of developers, you should use automation because it helps keep everyone organised and avoids human mistakes.

But if it’s a small thing with a few devs, or especially a personal project, it might be easier to do without :)

permalink
report
parent
reply
6 points

It’s perfectly fine for some private page etc. but when you make business software for customers that require 99,9% uptime with severe contractual penalties it’s probably too wonky.

permalink
report
parent
reply
4 points

Think of this like saying using a scythe to mow your lawn is antiquated. If your lawn is tiny then it doesn’t really matter. But we’re talking about massive “enterprise scale” lawns lol. You’re gonna want something you can drive.

permalink
report
parent
reply
3 points

Like anything else, it’s good to know how to do it in many different ways, it may help you down the line.

In production in an oddball environment, I have a python script to ftp transfer to a black box with only ftp exposed as an option.

Another system rebuilds nightly only if code changes, publishing to a QC location. QC gives it a quick review (we are talking website here, QC is “text looks good and nothing looks weird”), clicks a button to approve, and it gets published the following night.

I’ve had hardware (again, black box system) where I was able to leverage git because it was the only command exposed. Aka, the command they forgot to lock down and are using to update their device. Their intent was to sneakernet a thumb drive over to it for updates, I believe in sneaker longevity and wanted to work around that.

So you should know how to navigate your way around in FTP, it’s a good thing! But I’d also recommend learning about all the other ways as well, it can help in the future.

(This comment brought to you by “I now feel older for having written it”, and “I swear I’m only in my fourties,”)

permalink
report
parent
reply
3 points

Not to rub it in, but in my forties could be read as almost the entirety of the modern web was developed during my adulthood.

permalink
report
parent
reply
1 point

It could, but I’m in my early 40s.

I just started early with a TI-99/4A, then a 286, before building my own p133.

So the “World Wide Web!” posters were there for me in middle school.

Still old lol

permalink
report
parent
reply
3 points

Then switch to use sth more like scp ASAP? :-)

permalink
report
parent
reply
6 points

Nah, it’s probably more efficient to .tar.xz it and use netcat.

On a more serious note, I use sftp for everything, and git for actual big (but still personal) projects, but then move files and execute scripts manually.

And also, I cloned my old Laptops /dev/sda3 to my new Laptops /dev/main/root (on /dev/mapper/cryptlvm) via netcat over a Gigabit connection with netcat. It worked flawlessly. I love Linux and its Philosophy.

permalink
report
parent
reply
2 points

Ooh I’ve never heard of it. netcat I mean, cause I’ve heard of Linux 😆.

The File Transfer Protocol is just very antiquated, while scp is simple. Possibly netcat is too:-).

permalink
report
parent
reply

Programmer Humor

!programmer_humor@programming.dev

Create post

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

  • Keep content in english
  • No advertisements
  • Posts must be related to programming or programmer topics

Community stats

  • 3.4K

    Monthly active users

  • 1K

    Posts

  • 38K

    Comments