I’m following the #NodeJS instructions, but really that means working with #Docker
brew install docker
docker login gives me
WARNING! Your password will be stored unencrypted in ~/.docker/config.json.Configure a credential helper to remove this warning. Seehttps://docs.docker.com/engine/reference/commandline/login/#credentials-store
OK, I’ll look at that later
Running the one liner docker build -t username/nodejs-app:1.0.0 .
DEPRECATED: The legacy builder is deprecated and will be removed in a future release. Install the buildx component to build images with BuildKit: https://docs.docker.com/go/buildx/
Let’s see if brew has this, yep brew install docker-buildx
With some advice about linking it into ~/.docker/cli-plugins
New error: ERROR: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
I could see running an entire organization off this … but I’m also having like a visceral reaction to the entire interface; would I want to be part of an org that gets work done using this?
I want to turn off some other services like the long running Venture Scouts Discourse
It’s on a really old version and I could upgrade it and then migrate it to Commons Computer
Community is a resource. Maybe we should stop mining it. One reason I’m here is because I believe that well-architected, user-centric social media can be regenerative of community instead of extractive.
When a message arrives, it feels like (and this requires real precision and control) you have just received a long rambly email from a (very smart, hugely successful) friend.
Lorde’s messages do not belong to the internet of Twitter or Instagram; they don’t belong to the internet of Substack, either. You can’t link to them! So they aren’t even part of the World Wide Web — not really. They constitute their own special thing.
I won’t quote Sloan quoting Lorde, but it’s excellent