#techSupport in this code for step 4 where it says ${name}, is it implied that i replace "${}" with something? it makes sense to me for passwords, but something like ID i am unsure about because i don't have an ID command on windows, and in step 3 they write "change_me" explicitly and a note in the warnings to change the password. but the config section makes it seem like changing things is optional.
Post
i am having a hard time figuring out if this is like, assumed knowledge for people who are used to using command line programs or not
some of the people in the github issues are replacing it, some are not
when i try to search for this kind of question i get junk. so i think i'm in a weird noob spot where i don't know how to explain my question well enough.
@pixouls Nah, I think this is a poorly written guide.
In the same breath it gives you the code for 2 different files, and then tells you how to replace the placeholder text inside them -- without saying that you're only supposed to do the replacement on one of the files.
---
In general, I also find the ${SOME_VARIABLE} syntax in tutorials confusing.
Depending on the context, it could be telling you to either replace the entire string, or just the SOME_VARIABLE bit, or nothing at all.
(1/2)
@pixouls In this case, it's bash-like substitution which replaces the entire string:
APP_ID=${SOME_VARIABLE} -> APP_ID=1234
But, like, that's not the assumption I'd make in every context.
And, as @inherentlee showed, it's indeed the wrong assumption to be making for the yaml file!
Blah!
(2/2)
This is something that always annoyed me when learning this stuff... 😁
Still arguing with some of the design decisions made in the 1960's... :))
@BillySmith @ragman @pixouls it's kludge all the way down lmao
And duct tape and string... :))
I was standing on the platform of Hackney Central station starring at the power lines in an un-caffeinated state, when I realised that some of the ralway power lines were held together with string!
I spoke with one railway engineer I know about this, and he grumpily said, "Yes! It's a very expensive brand of Railway-Grade String!" then he ordered another pint... 🤦 🤣
1+ more replies (not shown)
@inherentlee @BillySmith @pixouls
Nothing more permanent than a temporary job-security hack, amirite? XD
1 more replies (not shown)
Just realized that what I said in the second comment might be confusing.
It's their code (or, probably Docker), whatever processes the yaml file, that's doing the substitution, not (you) the installer!
(3/3)
Thinking about things, and you would have an interesting time gossiping with the people from @coopcloud on their comms channels.
There's been a lot of "discussion" about Docker issues... :))
@BillySmith @pixouls @inherentlee @coopcloud
They seem cool! And yeah, I think Docker is great to get reproducible environments (nice for helping ppl self-host), but it also comes with a big learning curve and another layer of abstraction
It's more of a historical programming/scripting thing.
Way back in the 1950's/1960's, when mainframes were leased/sold to banks/governmat-departments/financial-institutions, the programmer were directly employed by the org's to write software for them. Software was not sold, it was purpose-made.
This lead to a lot of scripting being a thing for sys-admins, where they would create their own small programmes specific to the system they were using.
When those scripts/programmes were shared, it couldn't be guaranteed what format of variables were acceptable to the system, as each system manufacturer went off on their own tangent.
It became standard practice for anyone discussing their scripts to use a $ sign to signify a variable, with the brackets around the variable containing the description of what the variable was used to contain.
So far, so "functional programming". :D
@BillySmith yes. that makes sense to me. it's hard for me to know without enough context whether ${var} is calling an existing var (which turns out to be the case), and is not instead ${var-placeholder}
Exactly! 😁
We don't know whether ${name) is a short-hand description meaning "Insert your own variable of the correct format here" or whether it is "the correct syntax for a specific programming language", or as you say, ${name) referring to an instance of an existing variable.
This is the sort of "job securoty dark pattern" that was used by mediocre programmers, and is one of the reasons that programmers became less trusted by managers.
This is why they want to use AI... 🤦
The ${var-placeholder} is also a programming standard, used for portability between incompatible systems with very different variable formats. :D
This became used in some of the programming language designs that were evolving at that time, and in the scripting languages.
So the "$" sign became a standard way of denoting a variable, but it also became used as an official syntax denoting variables in some scripting languages, and some programming languages.
Add in the job security that came from hiding what you were doing so you could not be replaced, and you have the mess that our current situation evolved from. :D
@BillySmith my main ick is that it's being distributed advertised to windows users without full support for windows users which just happens a lot in open source. like i'm not at the point where i can have linux as a daily driver to learn it and i also can't easily get another machine dedicated for it either. i just learn everything in bits in pieces from people who actually do workshops that are truly for the 101
