dandarie

7 ms·

1.
by dandarie 3y ago
For what?
2.
Vintage Apple rig says ‘Hello, 1994’ from Romania [Setups](cultofmac.com)
3 points by dandarie 5y ago|0 comments
3.
by dandarie 5y ago
Is that a fact or an opinion?
4.
by dandarie 5y ago
How about tags/sets?
5.
by dandarie 5y ago
I can attest winters were definitely colder in the Moldavian part. I remember two meters of snow, digging tunnels through it and such. And I remember four distinct seasons. Now it's more like a long summer, a long autumn, and short spr
6.
by dandarie 5y ago
> The criticism only applies to users who reused their passwords on other sites, because Edward can still attack those other sites. Of course, but that's a weakness that concerns the user, not the platform. It is not a flaw of Faceb
7.
by dandarie 5y ago
Yes, he can steal the cookies and new passwords, but still won't have access to user accounts and/or passwords for more than an hour. So, after Edward is discovered, all sessions are remotely logged off and all accounts created du
8.
by dandarie 5y ago
You still have to trust your passwords being stored elsewhere, with weak encryption, if at all.
9.
by dandarie 5y ago
The solution is for docker-compose (or plain docker). I don't think the reproducibility is out. It's the same app, the same image, the same intended user, you just inject, once, the local user and group ids.
10.
by dandarie 5y ago
From my experience, UID is not always available as to docker-compose.yml because it isn't exported (at least in bash). See more here: https://stackoverflow.com/a/50900530/15428104 $ declare -p UID declare -ir
11.
by dandarie 5y ago
Of course, but really only build once on every machine. The subsequent starts use the cached build, even after reboot. In fact, docker-compose up -d takes care of the build thing by itself. It's a five second tradeoff for the lifetime
12.
by dandarie 5y ago
You start from a base image of your choice. You only build the user replacement part. You run docker-compose build ONCE and you're set. On my machine, it takes five seconds. Heck, you can even run docker-compose build everytime you sta
13.
by dandarie 5y ago
> Do I need to set USERID for project foo, or UID? Does it default to 1000 or the author's UID? Oh, someone has a problem with our project, did they remember to set COMPANY_USERID in their bashrc? Oh, wait, they're using zsh, h
14.
by dandarie 5y ago
That runs the container as a given usee, but doesn't prevent the container running some processes as a different internal user.
15.
by dandarie 5y ago
1. Nope, they are not pre-baked. They are built at runtime from env vars on each machine. 2. One step, setting up two vars. They can be set by a build script. Lots of things have build scripts way more complicated than this. The only tediou
16.
by dandarie 5y ago
> The problem with this approach is that is not portable. What if I am developing using more than one computers where in each computer my user has different ID? Make the build script use local $USERID and $GROUPID as args during the buil