298
Old timers know (sh.itjust.works)
submitted 6 days ago by alphacyberranger@sh.itjust.works to c/programmerhumor@lemmy.ml
36 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[-] RegalPotoo@lemmy.world 29 points 6 days ago

I personally am familiar with 2 organisations with millions of dollars in annual revenue that deploy critical line of business applications like this in 2024

[-] hemko@lemmy.dbzer0.com 9 points 6 days ago

Ftp deployments are supported in azure web apps too, and widely used.

I just came by an org recently that serves intermediate ca certs that way ¯\_(ツ)_/¯

[-] skilltheamps@feddit.de 1 points 6 days ago

With something like this, how do you handle the period of time while copying? I mean you can't really leave it running as it wouldn't be in a consistent state. A "under maintenance" page instead? Copy to a fresh folder and when done tell the webserver to serve the new location?

[-] folekaule@lemmy.world 8 points 6 days ago* (last edited 5 days ago)

It depends. I've done it a few different ways:

  • YOLO: especially with thugs like PHP you only affect one page at a time and with low traffic the odds of a problem is small
  • Maintenance page: temporarily show a page. Some servers like IIS have this built in. Otherwise it's a simple update to httpd conf
  • In a cluster environment, just take the node you're updating out of rotation, and only update one node at a time.
  • Copy and switch like you suggested. Can be combined with any of the above and is a smart move if upload is slow or can be interrupted, or it's cumbersome to restore the old files

Edit: spelling

this post was submitted on 22 Jun 2024
298 points (97.8% liked)

Programmer Humor

31184 readers
59 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 4 years ago
MODERATORS
AgreeableLandscape@lemmy.ml
cat_programmer@lemmy.ml