3 ms·
I don't like that the first step in the tutorial, before they even explain what this thing is, is "execute our arbitrary code on your machine" > Start the Link
by evil-olive 6mo ago
I don't like that the first step in the tutorial, before they even explain what this thing is, is "execute our arbitrary code on your machine"
> Start the LinkedRecords backend locally with a single command (requires Docker)
> docker compose -p linkedrecords -f https://github.com/wolfoo2931/linkedrecords.git#main:docker-compose.yml https://github.com/wolfoo2931/linkedrecords.git#main:docker-... up
(I didn't know docker-compose could take arbitrary URLs like that. cool. `curl | sudo bash` is old-school I guess?)
for every 1 legit use of starting off a blog post with those instructions, I can think of N that would be malicious or scammy in some way.
- WolfOliver 6mo agoYou a free to inspect the yaml file which will be passed into the docker compose. Also it is not as dramatic as it looks like as docker compose will just start containers. All the potentially malicious code will be run in containers.
- WolfOliver 6mo agoWould you be less sceptical if the tutorial would use a publicly hosted instance?