3 ms·
I'm not the best person to ask about this as I don't do much web dev these days, and my experience with podman is mostly limited to deploying existing software.
by bogwog 1y ago
I'm not the best person to ask about this as I don't do much web dev these days, and my experience with podman is mostly limited to deploying existing software. If compose works for that use case, then you should probably stick with it. For actually deploying it somewhere though, you should be using quadlets instead (or kubernetes I guess)
> No copying files to ~/.config/systemd just run docker-compose to start and stop.
Naively, I'd say to create symlinks instead of copying, and run `systemctl daemon-reload`/`systemctl restart ...`. Although there are probably more streamlined web development options out there.
Maybe look into Podman Pods. They're probably closer to what you're looking for, but idk what kind of dev tools exist out there for it. Maybe a few custom shell scripts to run the pod management commands is all you really need?
- johnny22 1y ago> Naively, I'd say to create symlinks instead of copying, I did mean symlinks too. The rest of my system shouldn't have to know or care about my project at all. I just wanna be able to systemctl --user start ./my-service.service or something to that effect.
- all2 1y ago> I just wanna be able to systemctl --user start ./my-service.service or something to that effect. Can you not? I know that systemctl has a userspace dot folder for user's services. [0] `~/.config/systemd/user/`
- bogwog 1y agoThe quadlet user folder is typically at `~/.config/containers/systemd`. So if you put your .container files in there, you can start them with `systemctl start --user MyContainer` https://docs.podman.io/en/latest/markdown/podman-systemd.unit.5.html#podman-rootless-unit-search-path https://docs.podman.io/en/latest/markdown/podman-systemd.uni...
- johnny22 1y agoand that's why it's a non-starter for dev stuff (to me). I'll stick with docker-compose (although with podman)