Administrator and architect path
11 videos and 1 docs page · 42 min
For the people who install and run Weik.io and decide where its parts go. You start with the overview and what runs where, install a hub, set up projects, access, sites and agents, follow one integration to production and finish with watching the installation and backing it up.
Start the pathSteps
1. Overview · 4:30 How Weik.io is put together An integration in Weik.io is a folder of Apache Camel files, and this overview follows one from your machine through versions, environments and the agents at your sites to the hub they all link to.Watched
2. Concept 2 · 3:41 What runs where Each part of Weik.io has its place, from the weikio CLI and the admin UI on your machine to the agents at each site.Watched- 3. Docs pageInstall a hub on one serverInstall the hub on one server with Docker Compose, from the release files and their checks to
weikio-backend init,docker compose up -dand the first sign-in with two-factor authentication. 
4. Admin 2 · 3:40 Projects, environments and access An admin sets up a second team's project on the hub, with a production environment after devtest.Watched
5. Admin 3 · 3:49 Sites and agents A new site joins your Weik.io installation by enrolling its agent, and the agent's capabilities decide which deployments placement puts on it.Watched
6. Camel 1 · 3:15 Your first integration A folder of Apache Camel files on your machine becomes an integration running in devtest and logging to the terminal and the admin UI.Watched
7. Camel 3 · 4:04 What a running integration is doing When a step of the hello integration starts failing, its logs, its failure counts and the trace of one message show what happened, in the terminal and in the admin UI.Watched
8. Camel 4 · 3:56 Where the values live Variables and secrets give an integration its values per environment, kept out of its files, and a new value takes effect at the next start.Watched
9. Delivery 1 · 3:56 From devtest to production The hello integration moves from devtest into production by promotion, and each environment keeps its own values for secrets and variables.Watched
10. GitOps 1 · 4:17 An integration in a Git repository The hello integration and its devtest documents move into a Git repository, and the hub is updated from there after a plan shows what the update will change.Watched
11. Admin 4 · 3:00 Watching the whole installation An admin sees what's wrong across the whole installation, including the hub's own health and logs, and looks up who changed what and why in the audit log.Watched
12. Admin 5 · 3:31 Backups, restore and upgrades A backup of the hub, checked against its manifest, restores one deleted document or the whole hub, and an upgrade starts with a backup.Watched
More in the University
Developer path For developers who write integrations. You start with how Weik.io is put together, run Weik.io on your machine and build one integration through the Camel track, then promote it to production and move it into a Git repository.All videos Every video of Weik.io University, with a filter for each track.