The heredoc in the script is never terminated. Probably it's not the production version but one for publishing ;-)
My deployment platform is a shell script
21–30 of 141 posts
Re: My deployment platform is a shell script
#22Not to deride this (too much), but the 'robustness' of deployments with shell scripts is tempting bait. Things are until they aren't, 'nobody rides for free' - decide what you're willing to pay. Example: this interprets the output of 'ls' . Reliability is dependent on good quoting/never introducing a project with spaces Ansible is a nice middle ground, personally. I write the state that differs, use a library of scri…
Putting SAVEIFS=$IFS IFS=$(echo -en "\n\b") or something similar at the top of the script might not come across as comparable to adopting Ansible to some people.
I knew giving specific examples would lead this way, that's not my point.
This case has been handled. Others?
There isn't anything really insightful here. Someone pleased with a script has not yet grown beyond the needs of it. Yay.
The more portable/maintainable version of this is a playbook or whatever. Someone wrote and tested a better version of whatever Work Unit as a module.
Wheel enthusiast is pleased with their finely polished, but not particularly traveled, wheel. It's great, but they're commodities and not seeing much.
I would have done the same thing with 'ansible-pull' and zero code, in even less time/effort... but I also already know Ansible and bash.
Configuration management tools are excellent at managing applications and configs. Who knew.
Something else to suggest: systemd timers. At a glance info for scheduling of the job, instead of inferred from logs that may or may not have been recorded. You can also then actually declare your deployment needs networking.
Eyeroll.jpg. This is great because the bar is so low. They'll generate a ton of useless logs if they lose networking, as-is. Long enough and the disk will fill: this is trying every minute.
Re: My deployment platform is a shell script
#23Earlier quoted context omitted.
[flagged]
> The phrase “sweet summer's child" became a popular way of describing an innocent, naive person (especially among American writers) during the early Victorian era. It was used by a number of authors during the 1840s, notably:- Fredrika Bremer (1840), James Staunton Babcock (1849) in The West Wind and Mary Whitaker (1850) in The Creole. It has been used in a number of other novels, poems and speeches (especially by U…
My sweet summer child, you couldn't tell I was being sarcastic and rhetorical?
Re: My deployment platform is a shell script
#24Earlier quoted context omitted.
It's an expression that implies that someone is naive and/or inexperienced.
I find it condescending and cliched in the same way those in this thread do: https://news.ycombinator.com/item?id=39417916 It adds absolutely nothing to the discussion. A better response is for the GP to tell us why they think the OP is naive. It's a low effort unsubstantiated jab that pollutes the comments.
You getting so tilted[0] at a turn of phrase[1] is polluting the comments far more than GP is. Touch grass[2].
[0] "tilted" is a common idiom used to denote anger or frustration which originates from the gaming community, when frustrated pinball machine players would literally tilt the machine. I am not suggesting that you are literally sitting or standing at an incline.
[1] "Turn of phrase" denotes a particularly notable form of non-literal expression. It was likely coined by Benjamin Franklin. Ironically, "turn of phrase" is itself a turn of phrase, as it is meant to evoke the image of turning words on a lathe, despite it not being physically possible to turn words on a lathe due to words being abstract concepts.
[2] "touch grass" is a lighthearted or humorous way of advising someone to take a break from their online activities, perhaps by going outside and interacting with the real world, particularly if they are excessively immersed in virtual or digital environments. It is also a useful metaphor for partaking in the smoking of marijuana, which is often referred to as "grass."
Re: My deployment platform is a shell script
#25If the author is reading this: did you code the fish animation CSS manually or used some wrapper for all these moz- and webkit- variants?
Re: My deployment platform is a shell script
#26Earlier quoted context omitted.
I find it condescending and cliched in the same way those in this thread do: https://news.ycombinator.com/item?id=39417916 It adds absolutely nothing to the discussion. A better response is for the GP to tell us why they think the OP is naive. It's a low effort unsubstantiated jab that pollutes the comments.
You getting so tilted[0] at a turn of phrase[1] is polluting the comments far more than GP is. Touch grass[2]. [0] "tilted" is a common idiom used to denote anger or frustration which originates from the gaming community, when frustrated pinball machine players would literally tilt the machine. I am not suggesting that you are literally sitting or standing at an incline. [1] "Turn of phrase" denotes a particularly no…
I hung some washing out and it was grounding to literally touch grass (before it started raining). Thanks & apologies
Re: My deployment platform is a shell script
#27I use similar things for bigger (multi-server) deploys too. It's light and it just works and works for decades without changes/updates. People say it's brittle; I have a proof of n>0 that this is not the case compared to many other solutions, this post making that point too. Sh/bash/perl(8) have been around forever, they don't break after update etc.
I sadly don't recommend it for my day job, simply because of liability. When something messes up with ansible, terraform, docker, cloudformation etc, no-one gets any blame because 'complex systems', 'it happens' etc etc; with a simple script going wrong, they would hang me high even though it probably saves a crap load in maintenance, compute etc over the 10s of years. Same reason we use clusters and IaC while of course nothing we do needs it; if an aws cluster goes down, no-one but aws gets blamed, while if the $2 postgres vps@cheapafhosting (with an higher uptime than that aws cluster by the way; human error downed it a few times, short, but still) is down even for a ping, everyone is upset and pointing fingers.
Re: My deployment platform is a shell script
#28Off topic: I love the writing style of the author and this blog. Gonna follow it.
Re: My deployment platform is a shell script
#29Earlier quoted context omitted.
It's an expression that implies that someone is naive and/or inexperienced.
I find it condescending and cliched in the same way those in this thread do: https://news.ycombinator.com/item?id=39417916 It adds absolutely nothing to the discussion. A better response is for the GP to tell us why they think the OP is naive. It's a low effort unsubstantiated jab that pollutes the comments.
I don't agree it adds nothing - it conveys that the author underestimates the power of Murphy's law.
Re: My deployment platform is a shell script
#30Not exactly the same configuration as the op, but if you are developing software using Go, the combination of Caddy, a single go binary, and systemd or some other supervisor is extremely flexible and i think is the way for running multiple services on a single VM.
A shell script that deploys a couple config files and off you go. Use different accounts for each service for isolation and put all of your static files in your binary using embed.FS. No need for fancy configuration management or K8s.