You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ A gitops tool to deploy systemd managed containers on linux. A.K.A quadlets.
6
6
7
7
`quadit` is focused on managing [quadlets](https://docs.podman.io/en/latest/markdown/podman-systemd.unit.5.html) and running containers in rootless mode using a gitops model.
8
8
9
-
The `quadit`' core usecase is a `remote edge` scenario enforcing a pure pull model that ensures no inbound access to the device.
9
+
The `quadit` core usecase is a `remote edge` scenario enforcing a pure pull model that ensures no inbound access to the device.
10
10
11
11
It is written in rust to minimise the overall footprint and improve the power consumption of running a gitops service on low resourced systems.
12
12
@@ -41,6 +41,10 @@ Please evaluate the following matrix to understand which one would better suit y
41
41
42
42
## install
43
43
44
+
This example runs [a simple container](https://github.com/ubiquitous-factory/quadit/blob/main/samples/helloworld/hello.container#L7) that tails `/dev/null` to demonstrate how you automate the provisioning of containers through a yaml config file.
45
+
46
+
Once you've seen the demo you will probably want to host the config file in your own repo rather than use this one so you can add additional services and test out how the GitOps aspects work when the `config.yaml` is updated.
47
+
44
48
From the edge device running a systemd based distro with the latest podman the following commands:
0 commit comments