Skip to content
Weik.ioDocs
2026.2
Try Weik.io

To production

Weik.io 2026.2

The same remote names have different values in devtest and production, so weikio promote moves the tested version to production without a rebuild. Product page · Video

Watch: To production, 4:27

The video promotes the transfer to production. In production, its two ends point at different systems.

On this page

The transfer refers to its source by the remote’s name, remote: supplier-ftp. That name has a different value in each environment, so the same version runs in devtest against a test system and in production against the supplier’s server.

Two values of the same remote#

The default value of supplier-ftp is the supplier’s server. Devtest has a file of its own that points at a folder on the devtest agent. A test run moves the files you put there:

finance/variables/supplier-ftp.yaml
apiVersion: weik.io/v1
kind: variable
metadata: { name: supplier-ftp, project: finance }
spec:
  value: |
    type = ftp
    host = ftp.supplier.example
    user = weikio
    pass = {{supplier-ftp-password}}
finance/devtest/variables/supplier-ftp.yaml
apiVersion: weik.io/v1
kind: variable
metadata: { name: supplier-ftp, project: finance, environment: devtest }
spec:
  value: |
    type = alias
    remote = /var/lib/weikio/test-files

With this value, the transfer’s path /outgoing is home/test-files/outgoing in the site’s folder on its host. Because the variable has the remote’s full definition, the two environments can use different kinds of system. For a supplier’s test FTP server, write that server’s definition in devtest’s file instead.

Promote#

Production needs its own values of the two secrets:

Terminal
$ weikio secret set finance/supplier-ftp-password --env production
$ weikio secret set finance/invoice-archive-key --env production

Once a run on devtest moved what it should, promote the version:

Terminal
$ weikio promote finance/supplier-invoices --from devtest --to production

Production’s deployment gets the version devtest ran, with no rebuild, because the host isn’t part of the version. Check the values it gets before its first run:

Terminal
$ weikio get variables --env production --resolved --integration supplier-invoices

The list has each value the transfer gets in production and where it comes from. Secrets show as ********.

Change the server later#

When the supplier moves its server, edit the variable file and apply it. The apply lists the deployments that get the new value at their next start and the command that restarts each one now:

Terminal
$ weikio apply -f ./finance/variables/supplier-ftp.yaml
$ weikio restart finance/supplier-invoices --env production

For a password in a placeholder, weikio secret set lists the deployments that use the secret. With --restart, it also restarts them.

Through Git#

In a repository, promotion is a pull request that changes the version in finance/production/deployments/supplier-invoices.yaml. The production workflow applies it after the reviewers approve what will run. Keep integrations in Git has the workflow files.

Sign in to the live demo

Sign in with the shared viewer account. It can open every screen of the example projects but can't change anything.

E-mail
viewer@demo.weik.io
Password
try-weikio-live-demo
Open the live demo