
Managed file transfer
Weik.io
- 1
3:40Your first transfer (MFT 1)
Weik.io
A transfer copies a supplier's invoices from an FTP server to an archive bucket, with no Camel route. It is written as three documents, with its two ends as variables, and published before anything runs.
- 2
3:31Deploy it, and see a file move (MFT 2)
Weik.io
Once its two secrets are set, the transfer is deployed and run on request, and the first file moves into the archive bucket. The schedule field, a cron, repeats the run on its own.
- 3
3:41Shape what moves (MFT 3)
Weik.io
The supplier's folder also holds a price list, and a filter pattern keeps it out of the archive so only invoice PDFs move. The operation field decides whether the originals stay on the supplier's server.
- 4
3:44What happened: the files behind a run (MFT 4)
Weik.io
Two records answer what a transfer's runs moved. The journal keeps one row per file, and each run publishes a run record with its counts, both readable in the admin UI and in the terminal.
- 5
3:59To production (MFT 5)
Weik.io
The invoice transfer from the earlier MFT videos goes to production, where its remotes and secrets have values of their own. A run that fails on a changed supplier password is found and fixed.