Change it and run it again

Camel 2 · 4:01

weikio run publishes an edited folder and moves the deployment to the new version, and every older version is kept. The same folder also runs on your own machine without publishing anything.

Download the mp4Recorded on 2026.2

What it covers

Changing the timer period and the message in two files
Checking the folder with weikio validate before anything is published
Publishing and deploying version 0.1.1 with weikio run
Listing every version, newest first, with weikio get versions
The version list and the Source section's version picker in the admin UI
Running the folder locally with weikio dev run, which publishes nothing

Commands in this video

Terminal

$ weikio validate -f ./hello
$ weikio run ./hello
$ weikio get versions sandbox/hello
$ weikio dev run ./hello

Transcript

0:02The first integration runs. The next change happens in its files.
0:06This video shows what that change takes.
0:12This is the folder from the earlier Camel video, hello/ on your machine.
0:17Your Weik.io installation keeps the one published version, 0.1.0.
0:23In devtest, agent dev is online at the site and runs the integration.
0:28Its deployment runs version 0.1.0.
0:32The route fires every five seconds, then logs its message.
0:36Each tick under the agent marks one log line.
0:42hello.camel.yaml holds the timer's period, application.properties holds the message.
0:49The first edit sets the period to three seconds.
0:53The second changes the message the route logs.
0:59Before anything is published, weikio validate on the hello folder checks the shape,
1:05names and fields of its documents.
1:08The folder passes, so the change is ready to publish.
1:15weikio run on the hello folder publishes the change, then deploys it in devtest.
1:22The build makes 0.1.1, a patch above 0.1.0, which stays.
1:29The command then follows the log lines of sandbox/hello.
1:33The folder arrives in Weik.io as a built version.
1:39The deployment follows latest, so it moves to 0.1.1 within seconds.
1:45The running copy stops, then a new process starts on 0.1.1.
1:51The log carries the new message every three seconds.
1:54Control C stops only the following.
1:57sandbox/hello keeps running at the installation.
2:04weikio get versions sandbox/hello lists every version the installation keeps.
2:12The newest row comes first, marked latest.
2:15Publishing put 0.1.1 on top of the stack.
2:19A built version never changes.
2:26The Versions section in the admin UI carries the same history the command listed.
2:31Each row notes when the version was made and whether devtest runs it.
2:36The page's Source section stores the integration's files as they were published.
2:40The picker above the file list moves the section from
2:43the current source to an older version's stored files.
2:51weikio dev run on the hello folder runs the folder without publishing anything.
2:57Camel starts on your machine, beside the folder.
3:00Before starting, dev run reads the environment's resolved values from the installation,
3:06so placeholders read the same values locally.
3:09It prints the camel command it runs.
3:11The installation keeps no trace of the local run.
3:15Control C stops the local Camel for good.
3:22This video showed four things: edit, run, versions, dev run.
3:28The change was two lines in the files.
3:30weikio run publishes the new version, then points the deployment at it.
3:36The stack keeps every version as built, newest marked latest.
3:40weikio dev run tries the same folder on your machine without publishing anything.
3:46The installation logs the new message every three
3:49seconds until the next run replaces it.

Next in this track

Camel 3 · 4:24 What a running integration is doing