mariadb-podman-socket-activation VS obligator

https://github.com/eriksjolund/mariadb-podman-socket-activat...

In addition to that Podman supports socket activation that passes the socket to the container. Interestingly, this opens up the possibility to run a network server (e.g. a web server) with --network=none (i.e.podman run --network=none ...) in case the server process is happy with only communicating over the TCP socket it was passed. This increases security. Some references: https://github.com/containers/podman/discussions/13390 https://github.com/eriksjolund/mariadb-podman-socket-activation

Support for socket activation

Podman will pass on the socket-activated socket to the container.

I wrote a small example demo for setting up socket activation with systemd, Podman, and a MariaDB container:

https://github.com/eriksjolund/mariadb-podman-socket-activat...

I wrote a small example demo for MariaDB https://github.com/eriksjolund/mariadb-podman-socket-activation/

The deployment experience is awesome, but for me[0] the killer feature of Fly.io is their Anycast network and features such as FLY_REPLAY and LiteFS that make clusering a breeze[1].

[0]: using them for https://lastlogin.io

[1]: Here's all the fly-specific code necessary to run LastLogin in a globally distributed way: https://github.com/lastlogin-io/obligator/blob/37f75cc861f1b...

I use obligator with ephemeral storage, no db, 100% code driven setup.

In my opinion this is the simplist option.

https://github.com/lastlogin-io/obligator

See the table here: https://github.com/lastlogin-io/obligator#comparison-is-the-...

Sorry, this is indeed not very clear. Others already answered well, but if you look at the example[0] config you can see how you would use your own instance of obligator as a client to the instance running at lastlogin.io. This is a bit meta, but applies equally to any client application.

[0]: https://github.com/anderspitman/obligator#running-it