Developer path
10 videos · 40 min
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.
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 your own agents to the Weik.io installation they all link to.Watched
2. Concept 1 · 3:07 Projects and environments A project keeps one team's integrations and people apart from another team's, and all projects share the same environments.Watched
3. Getting started 1 · 3:02 Try Weik.io on your machine The whole Weik.io platform runs in a dev container on your own machine, opened from a GitHub repository and ready for a first sign-in to the admin UI.Watched
4. 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
5. Camel 2 · 4:01 Change it and run it again weikio runpublishes an edited folder and moves the deployment to the new version, and every older version is kept.Watched
6. Camel 3 · 4:24 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
7. Camel 4 · 4:37 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
8. Camel 5 · 3:59 Connecting to another system An integration that calls an outside HTTP service needs extra libraries, declared in integration.yamland resolved by Weik.io from Maven Central when you publish.Watched
9. Delivery 1 · 4:21 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:20 An integration in a Git repository The hello integration and its devtest documents move into a Git repository, and Weik.io is updated from there after a plan shows what the update will change.Watched
More in the University
Administrator and architect path 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 Weik.io, set up projects, access and agents, follow one integration to production and finish with watching the installation and backing it up.All videos Every video of Weik.io University, with a filter for each track.