Skip to content
Weik.ioUniversity
Try Weik.io

Change it and run it again

Camel 2 · 3:36

One command 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 in one step 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
  1. 0:02Video one left sandbox/hello running.
  2. 0:05This video changes it and runs it again, with one command for the whole loop.
  3. 0:14Video one ended with sandbox/hello running in devtest.
  4. 0:18The folder on your disk is the integration's source,
  5. 0:21and the hub holds the version it built from the folder.
  6. 0:24Its log line arrives every five seconds.
  7. 0:30This video changes the folder and runs it again.
  8. 0:33The edit touches two of the three files.
  9. 0:36In hello.camel.yaml, the timer's period goes from five seconds to three.
  10. 0:42In application.properties, the message text changes.
  11. 0:46The integration still runs 0.1.0, because nothing here is published yet.
  12. 0:56validate checks the folder before anything is published.
  13. 1:00It reads the files the way the build reads them.
  14. 1:03Checked 1 integration and found nothing to fix.
  15. 1:07A broken route fails here, with the file and the line,
  16. 1:11before the hub builds anything.
  17. 1:17weikio run publishes and runs in one command.
  18. 1:21Video one used apply to publish and deploy to run.
  19. 1:25run does both, so one command replaces the two.
  20. 1:29The folder becomes version 0.1.1, built at the hub.
  21. 1:37The deployment in devtest moves to it at once.
  22. 1:40The following prints each new log line as the hub receives it.
  23. 1:45The new message arrives every three seconds.
  24. 1:48Ctrl-C stops the following, and the integration keeps running.
  25. 1:55The versions command lists every version, newest first.
  26. 1:59A publish adds a version, and the ones already there never change.
  27. 2:03devtest runs the new one, and 0.1.0 is kept.
  28. 2:08The star marks the newest one.
  29. 2:14The admin UI shows the same versions.
  30. 2:17Each row shows when it was published.
  31. 2:20The Source section shows the files of the current version.
  32. 2:23The admin UI reads the files and does not edit them.
  33. 2:27The folder on your disk stays the source of truth.
  34. 2:30The picker above the files opens an older version.
  35. 2:37For fast edits, the folder can also run on your own machine.
  36. 2:41weikio dev run hands the folder to camel run,
  37. 2:45Camel's own runner, with the environment's values.
  38. 2:48Camel JBang is installed separately, from Camel's own site.
  39. 2:52The same log lines appear, and nothing is published.
  40. 2:56Ctrl-C stops it, and the hub is exactly as it was.
  41. 3:04Here is the whole loop.
  42. 3:06An edit is only files until run publishes them.
  43. 3:09run built version 0.1.1 and moved the deployment to it.
  44. 3:14Every version is kept, and video nine rolls back on that.
  45. 3:18When only the run matters, dev run skips the publish and the deploy.
  46. 3:23Video three reads what the running integration is doing.

Next in this track

Camel 3 · 4:04 What a running integration is doing Watched