Skip to content
Weik.ioUniversity
Try Weik.io

Your first integration

Camel 1 · 3:15

A folder of Apache Camel files on your machine becomes an integration running in devtest and logging to the terminal and the admin UI. You need a Weik.io installation with an online agent, such as the Try Weik.io dev container.

Download the mp4Recorded on 2026.2

What it covers

  • Signing in with weikio login, which saves the server and the API key as a context
  • The three files that weikio init hello writes, and the message in application.properties
  • Publishing the folder as version 0.1.0 with weikio apply
  • A deployment to devtest with weikio deploy, created without starting it
  • Starting it from the devtest cell's menu in the admin UI, or with weikio start
  • The log lines on the admin UI's Overview page and from weikio logs

Commands in this video

Terminal
$ weikio login https://hub.example --project sandbox --env devtest
$ weikio init hello
$ weikio apply -f ./hello
$ weikio deploy sandbox/hello --stopped
$ weikio start sandbox/hello
$ weikio logs sandbox/hello
Transcript
  1. 0:02This video shows your first integration on Weik.io.
  2. 0:05It ends with the integration running and logging to your terminal.
  3. 0:12You need your Weik.io installation.
  4. 0:15Agent dev at the site runs integrations and is online.
  5. 0:22With the Weik.io CLI, run weikio login against the installation.
  6. 0:27Login saves the server and the API key as a context,
  7. 0:31so later commands read the project and the environment from it.
  8. 0:39weikio init hello writes the folder hello/ with three Apache Camel files.
  9. 0:45A timer fires every five seconds, then the route writes the message to the log.
  10. 0:54The log step prints {{message}},
  11. 0:56which application.properties sets to hello from weikio.
  12. 1:01The folder is an integration, and its full name is sandbox/hello.
  13. 1:11weikio apply publishes the folder,
  14. 1:14then the installation builds the files into a version.
  15. 1:17The first line confirms the server,
  16. 1:20the project and the environment came from the context.
  17. 1:23The first publish becomes version 0.1.0, and a version never changes.
  18. 1:30Nothing runs yet. The last line gives the deploy command for this folder.
  19. 1:39Next, a deployment puts a version of the integration into an environment.
  20. 1:44That environment is devtest.
  21. 1:46weikio deploy sandbox/hello takes the integration by its full name.
  22. 1:52The flag at the end creates the deployment without starting it.
  23. 2:00Open hello from the Integrations page of the admin UI.
  24. 2:04The cell for devtest marks version 0.1.0 as stopped.
  25. 2:10Pick Start in the cell's menu to see the command for the CLI:
  26. 2:14weikio start sandbox/hello.
  27. 2:20After Confirm, hello runs on one agent.
  28. 2:25Agent dev runs hello as one Java process.
  29. 2:33The same log lines reach the Overview page in the admin UI.
  30. 2:40weikio logs sandbox/hello prints the log in the terminal.
  31. 2:50The hello folder on your machine has become version 0.1.0 in your Weik.io installation.
  32. 2:57That version then runs as a deployment in the devtest environment.
  33. 3:01Starting the deployment gives the agent a Java process.

Next in this track

Camel 2 · 3:36 Change it and run it again Watched