TAPPaaS/makerfloss
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
No description
6 commits 1 branch 0 tags 110 KiB
Find a file
Lars Rossen 1c48eb4634 portainer: gate the admin bootstrap on being able to log in 
The previous guard was 'does the password file exist'. The first lab1 install
wrote the password, then failed init on the missing setup token — leaving a file
that made every later run skip the bootstrap and then fail to authenticate, so
OIDC never got configured. Ask Portainer instead: try /api/auth, and bootstrap
only when that yields no token. The JWT is then reused for the settings PUT
rather than logging in twice.
2026-08-24 20:58:22 +02:00
src portainer: gate the admin bootstrap on being able to log in 2026-08-24 20:58:22 +02:00
.gitignore Seed the MakerFLOSS devops repo with the podman module 2026-08-22 18:46:24 +02:00
README.md Add portainer and komodo as parallel container-management modules 2026-08-23 09:45:01 +02:00

README.md

makerfloss

The MakerFLOSS DevOps repository for experimental TAPPaaS modules.

Modules are developed and tried out here, on the TAPPaaS system at makerfloss.eu, before they are proposed upstream to TAPPaaS or Community. Expect things to be half-built, renamed, or removed.

Layout

src/module-catalog.json      # the registry a TAPPaaS instance reads
src/containers/podman/       # one directory per module

Using it from a TAPPaaS instance

Register the repository on the tappaas-cicd mothership, then install a module from it:

site-manager repository add forgejo.makerfloss.eu/TAPPaaS/makerfloss --branch main

module-manager module add podman --environment <env>

--branch main is not optional: repository add defaults to stable, and this repo has no such branch. The repository name (makerfloss) is derived from the URL, and the clone is made over HTTPS.

Modules

Three parallel takes on the same job — run containers on a lab host, let registered people manage them, reach the other hosts in the zone. They exist side by side on purpose.

Module What it is Status
portainer Portainer CE on rootful Podman; OIDC login, agents on other hosts incomplete — the one the session uses
komodo GPL Core + Periphery alternative; scaffold, scripts specified but not written scaffold
podman Plain Podman host with the Cockpit console; single host, local login incomplete

Why three: Cockpit turned out to fit neither requirement — it is not an OIDC client and cannot be made one, and its multi-host switcher is deprecated and disabled by default because it "cannot be secure". The reasoning is written up in podman/DESIGN.md.