Can you use those quadlets inside a development project? I use docker-compose (with podman) just so i can work on a project that is completely self-contained. No copying files to ~/.config/systemd just run docker-compose to start and stop.

Can i do that with quadlets?

▲

bogwog 4 days ago | parent | next [-]

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 4 days ago | parent [-]

> 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 4 days ago | parent [-]

> 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 3 days ago \| parent [-]
		The 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.uni...

▲

jabl 4 days ago | parent | prev [-]

What I've done is use the "podman kube play" similar to docker-compose when developing ("podman kube play file.yaml", "podman kube play --down file.yaml", "podman kube play --replace file.yaml", etc.) with the "file.yaml" in my working directory. Then when I'm satisfied and want to deploy to production I write a quadlet snippet referencing the kube file and put them under /etc.