You can set up multiple remotes for a repo and push to a local git server and github at the same time
You can set up multiple remotes for a repo and push to a local git server and github at the same time
I was too dumb too link it lol
Damn, I thought this was self hosted
Try running docker logs
for the tailscale container to see if it gives any more info
For anyone thinking about conducting a similar search for this image.
Turn on safe search before you search “flesh prison”
I’m done internetting for today
Tailscale keeps the private keys locally, . It just facillitates setting up wireguard. They could steal your private keys, as could any program you install with root access. But it would comepletely destroy their business, and it’s open source. I really dont think they have anything to gain by tricking everyone
I’m just gonna leave this here
Have you tried taking the metwork config out of the compose file and just letting podman handle it?
I’m in the wrong timeline
Was thinking “Oh shit now I have to become vegan”, but the article is paywalled so I didn’t have to go on the guilt trip.
Just to offer the other perspective. I started with podman years ago. I knew very little about containers and I would say it made the learbing curve a lot steeper. Most guides and README’s use docker and when things didnt work I had to figure out if it was networking, selinux, rootless, not having the docker daemon, etc… without understanding fully what those things were because I didn’t know docker. But when I started running stuff on kubernetes, it was really easy. Pods in podman are isomorphic to kubernetes pods. I think the pain was worth it, but it was definitely not easy at the time. Documentation, guides, and networking have improved since then, so it may not be as big of a deal now
Quadlets with podman have completely replaced compose files for me. I use the kuberentes configs. Then I run a tailscale container in the pod and BAM, all of my computers can access that service without have to expose any ports.
Then I have an ansible playbook to log in to the host and start a detached tmux session so my user systemd services keep running. Its all rootless, and just so dang easy.
For every sever install I’ve had, flatpak defaults to the system install which requires a password. You have to explicity pass the --user flag.
I’m not sure how to make it the default
Where’s the source code? Seriously, the only thing I can find for drive & calander are repos that were archived in 2021