Make sure you have Git 2.18.0 or newer and Docker installed.

To run werf as a regular user, you should have access to the Docker daemon. First, make sure the docker group exists:

sudo groupadd docker

Add your current user to the docker group:

sudo usermod -aG docker $USER
newgrp docker

Setup trdl which will manage werf installation and updates:

# Add ~/bin to the PATH.
echo 'export PATH=$HOME/bin:$PATH' >> ~/.bash_profile
export PATH="$HOME/bin:$PATH"

# Install trdl.
curl -L "https://tuf.trdl.dev/targets/releases/0.1.3/linux-amd64/bin/trdl" -o /tmp/trdl
mkdir -p ~/bin
install /tmp/trdl ~/bin/trdl

Add werf repo:

trdl add werf https://tuf.werf.io 1 b7ff6bcbe598e072a86d595a3621924c8612c7e6dc6a82e919abe89707d7e3f468e616b5635630680dd1e98fc362ae5051728406700e6274c5ed1ad92bea52a2

To use werf locally in your terminal, we recommend to enable its automatic activation. To make werf available in all new shell sessions, you need to execute this command (just once):

echo 'command -v trdl &>/dev/null && source $(trdl use werf 1.2 alpha)' >> ~/.bashrc

Now, if you log out and log in to the system again, werf will be always available. You can make sure of that by executing:

werf version

To get werf running in your current terminal only (before any logout/login is done), you can simply execute the source $(trdl use werf 1.2 alpha command.

In CI, you need a different approaching with activating werf explicitly in the beginning of each job/pipeline by executing:

source $(trdl use werf 1.2 alpha)

Make sure you have Git 2.18.0 or newer and Docker installed.

To run werf as a regular user, you should have access to the Docker daemon. First, make sure the docker group exists:

sudo groupadd docker

Add your current user to the docker group:

sudo usermod -aG docker $USER
newgrp docker

Setup trdl which will manage werf installation and updates:

# Add ~/bin to the PATH.
echo 'export PATH=$HOME/bin:$PATH' >> ~/.bash_profile
export PATH="$HOME/bin:$PATH"

# Install trdl.
curl -L "https://tuf.trdl.dev/targets/releases/0.1.3/linux-arm64/bin/trdl" -o /tmp/trdl
mkdir -p ~/bin
install /tmp/trdl ~/bin/trdl

Add werf repo:

trdl add werf https://tuf.werf.io 1 b7ff6bcbe598e072a86d595a3621924c8612c7e6dc6a82e919abe89707d7e3f468e616b5635630680dd1e98fc362ae5051728406700e6274c5ed1ad92bea52a2

To use werf locally in your terminal, we recommend to enable its automatic activation. To make werf available in all new shell sessions, you need to execute this command (just once):

echo 'command -v trdl &>/dev/null && source $(trdl use werf 1.2 alpha)' >> ~/.bashrc

Now, if you log out and log in to the system again, werf will be always available. You can make sure of that by executing:

werf version

To get werf running in your current terminal only (before any logout/login is done), you can simply execute the source $(trdl use werf 1.2 alpha command.

In CI, you need a different approaching with activating werf explicitly in the beginning of each job/pipeline by executing:

source $(trdl use werf 1.2 alpha)

Make sure you have Git 2.18.0 or newer and Docker installed.

To run werf as a regular user, you should have access to the Docker daemon. First, make sure the docker group exists:

sudo groupadd docker

Add your current user to the docker group:

sudo usermod -aG docker $USER
newgrp docker

Setup trdl which will manage werf installation and updates:

# Add ~/bin to the PATH.
echo 'export PATH=$HOME/bin:$PATH' >> ~/.bash_profile
export PATH="$HOME/bin:$PATH"

# Install trdl.
curl -L "https://tuf.trdl.dev/targets/releases/0.1.3/linux-amd64/bin/trdl" -o /tmp/trdl
mkdir -p ~/bin
install /tmp/trdl ~/bin/trdl

Add werf repo:

trdl add werf https://tuf.werf.io 1 b7ff6bcbe598e072a86d595a3621924c8612c7e6dc6a82e919abe89707d7e3f468e616b5635630680dd1e98fc362ae5051728406700e6274c5ed1ad92bea52a2

To use werf locally in your terminal, we recommend to enable its automatic activation. To make werf available in all new shell sessions, you need to execute this command (just once):

echo 'command -v trdl &>/dev/null && source $(trdl use werf 1.2 beta)' >> ~/.bashrc

Now, if you log out and log in to the system again, werf will be always available. You can make sure of that by executing:

werf version

To get werf running in your current terminal only (before any logout/login is done), you can simply execute the source $(trdl use werf 1.2 beta command.

In CI, you need a different approaching with activating werf explicitly in the beginning of each job/pipeline by executing:

source $(trdl use werf 1.2 beta)

Make sure you have Git 2.18.0 or newer and Docker installed.

To run werf as a regular user, you should have access to the Docker daemon. First, make sure the docker group exists:

sudo groupadd docker

Add your current user to the docker group:

sudo usermod -aG docker $USER
newgrp docker

Setup trdl which will manage werf installation and updates:

# Add ~/bin to the PATH.
echo 'export PATH=$HOME/bin:$PATH' >> ~/.bash_profile
export PATH="$HOME/bin:$PATH"

# Install trdl.
curl -L "https://tuf.trdl.dev/targets/releases/0.1.3/linux-arm64/bin/trdl" -o /tmp/trdl
mkdir -p ~/bin
install /tmp/trdl ~/bin/trdl

Add werf repo:

trdl add werf https://tuf.werf.io 1 b7ff6bcbe598e072a86d595a3621924c8612c7e6dc6a82e919abe89707d7e3f468e616b5635630680dd1e98fc362ae5051728406700e6274c5ed1ad92bea52a2

To use werf locally in your terminal, we recommend to enable its automatic activation. To make werf available in all new shell sessions, you need to execute this command (just once):

echo 'command -v trdl &>/dev/null && source $(trdl use werf 1.2 beta)' >> ~/.bashrc

Now, if you log out and log in to the system again, werf will be always available. You can make sure of that by executing:

werf version

To get werf running in your current terminal only (before any logout/login is done), you can simply execute the source $(trdl use werf 1.2 beta command.

In CI, you need a different approaching with activating werf explicitly in the beginning of each job/pipeline by executing:

source $(trdl use werf 1.2 beta)

Make sure you have Git 2.18.0 or newer and Docker installed.

To run werf as a regular user, you should have access to the Docker daemon. First, make sure the docker group exists:

sudo groupadd docker

Add your current user to the docker group:

sudo usermod -aG docker $USER
newgrp docker

Setup trdl which will manage werf installation and updates:

# Add ~/bin to the PATH.
echo 'export PATH=$HOME/bin:$PATH' >> ~/.bash_profile
export PATH="$HOME/bin:$PATH"

# Install trdl.
curl -L "https://tuf.trdl.dev/targets/releases/0.1.3/linux-amd64/bin/trdl" -o /tmp/trdl
mkdir -p ~/bin
install /tmp/trdl ~/bin/trdl

Add werf repo:

trdl add werf https://tuf.werf.io 1 b7ff6bcbe598e072a86d595a3621924c8612c7e6dc6a82e919abe89707d7e3f468e616b5635630680dd1e98fc362ae5051728406700e6274c5ed1ad92bea52a2

To use werf locally in your terminal, we recommend to enable its automatic activation. To make werf available in all new shell sessions, you need to execute this command (just once):

echo 'command -v trdl &>/dev/null && source $(trdl use werf 1.2 ea)' >> ~/.bashrc

Now, if you log out and log in to the system again, werf will be always available. You can make sure of that by executing:

werf version

To get werf running in your current terminal only (before any logout/login is done), you can simply execute the source $(trdl use werf 1.2 ea command.

In CI, you need a different approaching with activating werf explicitly in the beginning of each job/pipeline by executing:

source $(trdl use werf 1.2 ea)

Make sure you have Git 2.18.0 or newer and Docker installed.

To run werf as a regular user, you should have access to the Docker daemon. First, make sure the docker group exists:

sudo groupadd docker

Add your current user to the docker group:

sudo usermod -aG docker $USER
newgrp docker

Setup trdl which will manage werf installation and updates:

# Add ~/bin to the PATH.
echo 'export PATH=$HOME/bin:$PATH' >> ~/.bash_profile
export PATH="$HOME/bin:$PATH"

# Install trdl.
curl -L "https://tuf.trdl.dev/targets/releases/0.1.3/linux-arm64/bin/trdl" -o /tmp/trdl
mkdir -p ~/bin
install /tmp/trdl ~/bin/trdl

Add werf repo:

trdl add werf https://tuf.werf.io 1 b7ff6bcbe598e072a86d595a3621924c8612c7e6dc6a82e919abe89707d7e3f468e616b5635630680dd1e98fc362ae5051728406700e6274c5ed1ad92bea52a2

To use werf locally in your terminal, we recommend to enable its automatic activation. To make werf available in all new shell sessions, you need to execute this command (just once):

echo 'command -v trdl &>/dev/null && source $(trdl use werf 1.2 ea)' >> ~/.bashrc

Now, if you log out and log in to the system again, werf will be always available. You can make sure of that by executing:

werf version

To get werf running in your current terminal only (before any logout/login is done), you can simply execute the source $(trdl use werf 1.2 ea command.

In CI, you need a different approaching with activating werf explicitly in the beginning of each job/pipeline by executing:

source $(trdl use werf 1.2 ea)

Make sure you have Git 2.18.0 or newer and Docker installed.

To run werf as a regular user, you should have access to the Docker daemon. First, make sure the docker group exists:

sudo groupadd docker

Add your current user to the docker group:

sudo usermod -aG docker $USER
newgrp docker

Setup trdl which will manage werf installation and updates:

# Add ~/bin to the PATH.
echo 'export PATH=$HOME/bin:$PATH' >> ~/.bash_profile
export PATH="$HOME/bin:$PATH"

# Install trdl.
curl -L "https://tuf.trdl.dev/targets/releases/0.1.3/linux-amd64/bin/trdl" -o /tmp/trdl
mkdir -p ~/bin
install /tmp/trdl ~/bin/trdl

Add werf repo:

trdl add werf https://tuf.werf.io 1 b7ff6bcbe598e072a86d595a3621924c8612c7e6dc6a82e919abe89707d7e3f468e616b5635630680dd1e98fc362ae5051728406700e6274c5ed1ad92bea52a2

To use werf locally in your terminal, we recommend to enable its automatic activation. To make werf available in all new shell sessions, you need to execute this command (just once):

echo 'command -v trdl &>/dev/null && source $(trdl use werf 1.2 stable)' >> ~/.bashrc

Now, if you log out and log in to the system again, werf will be always available. You can make sure of that by executing:

werf version

To get werf running in your current terminal only (before any logout/login is done), you can simply execute the source $(trdl use werf 1.2 stable command.

In CI, you need a different approaching with activating werf explicitly in the beginning of each job/pipeline by executing:

source $(trdl use werf 1.2 stable)

Make sure you have Git 2.18.0 or newer and Docker installed.

To run werf as a regular user, you should have access to the Docker daemon. First, make sure the docker group exists:

sudo groupadd docker

Add your current user to the docker group:

sudo usermod -aG docker $USER
newgrp docker

Setup trdl which will manage werf installation and updates:

# Add ~/bin to the PATH.
echo 'export PATH=$HOME/bin:$PATH' >> ~/.bash_profile
export PATH="$HOME/bin:$PATH"

# Install trdl.
curl -L "https://tuf.trdl.dev/targets/releases/0.1.3/linux-arm64/bin/trdl" -o /tmp/trdl
mkdir -p ~/bin
install /tmp/trdl ~/bin/trdl

Add werf repo:

trdl add werf https://tuf.werf.io 1 b7ff6bcbe598e072a86d595a3621924c8612c7e6dc6a82e919abe89707d7e3f468e616b5635630680dd1e98fc362ae5051728406700e6274c5ed1ad92bea52a2

To use werf locally in your terminal, we recommend to enable its automatic activation. To make werf available in all new shell sessions, you need to execute this command (just once):

echo 'command -v trdl &>/dev/null && source $(trdl use werf 1.2 stable)' >> ~/.bashrc

Now, if you log out and log in to the system again, werf will be always available. You can make sure of that by executing:

werf version

To get werf running in your current terminal only (before any logout/login is done), you can simply execute the source $(trdl use werf 1.2 stable command.

In CI, you need a different approaching with activating werf explicitly in the beginning of each job/pipeline by executing:

source $(trdl use werf 1.2 stable)

Make sure you have Git 2.18.0 or newer and Docker installed.

To run werf as a regular user, you should have access to the Docker daemon. First, make sure the docker group exists:

sudo groupadd docker

Add your current user to the docker group:

sudo usermod -aG docker $USER
newgrp docker

Setup trdl which will manage werf installation and updates:

# Add ~/bin to the PATH.
echo 'export PATH=$HOME/bin:$PATH' >> ~/.bash_profile
export PATH="$HOME/bin:$PATH"

# Install trdl.
curl -L "https://tuf.trdl.dev/targets/releases/0.1.3/linux-amd64/bin/trdl" -o /tmp/trdl
mkdir -p ~/bin
install /tmp/trdl ~/bin/trdl

Add werf repo:

trdl add werf https://tuf.werf.io 1 b7ff6bcbe598e072a86d595a3621924c8612c7e6dc6a82e919abe89707d7e3f468e616b5635630680dd1e98fc362ae5051728406700e6274c5ed1ad92bea52a2

To use werf locally in your terminal, we recommend to enable its automatic activation. To make werf available in all new shell sessions, you need to execute this command (just once):

echo 'command -v trdl &>/dev/null && source $(trdl use werf 1.2 rock-solid)' >> ~/.bashrc

Now, if you log out and log in to the system again, werf will be always available. You can make sure of that by executing:

werf version

To get werf running in your current terminal only (before any logout/login is done), you can simply execute the source $(trdl use werf 1.2 rock-solid command.

In CI, you need a different approaching with activating werf explicitly in the beginning of each job/pipeline by executing:

source $(trdl use werf 1.2 rock-solid)

Make sure you have Git 2.18.0 or newer and Docker installed.

To run werf as a regular user, you should have access to the Docker daemon. First, make sure the docker group exists:

sudo groupadd docker

Add your current user to the docker group:

sudo usermod -aG docker $USER
newgrp docker

Setup trdl which will manage werf installation and updates:

# Add ~/bin to the PATH.
echo 'export PATH=$HOME/bin:$PATH' >> ~/.bash_profile
export PATH="$HOME/bin:$PATH"

# Install trdl.
curl -L "https://tuf.trdl.dev/targets/releases/0.1.3/linux-arm64/bin/trdl" -o /tmp/trdl
mkdir -p ~/bin
install /tmp/trdl ~/bin/trdl

Add werf repo:

trdl add werf https://tuf.werf.io 1 b7ff6bcbe598e072a86d595a3621924c8612c7e6dc6a82e919abe89707d7e3f468e616b5635630680dd1e98fc362ae5051728406700e6274c5ed1ad92bea52a2

To use werf locally in your terminal, we recommend to enable its automatic activation. To make werf available in all new shell sessions, you need to execute this command (just once):

echo 'command -v trdl &>/dev/null && source $(trdl use werf 1.2 rock-solid)' >> ~/.bashrc

Now, if you log out and log in to the system again, werf will be always available. You can make sure of that by executing:

werf version

To get werf running in your current terminal only (before any logout/login is done), you can simply execute the source $(trdl use werf 1.2 rock-solid command.

In CI, you need a different approaching with activating werf explicitly in the beginning of each job/pipeline by executing:

source $(trdl use werf 1.2 rock-solid)

Make sure you have Git 2.18.0 or newer and Docker installed.

To run werf as a regular user, you should have access to the Docker daemon. First, make sure the docker group exists:

sudo groupadd docker

Add your current user to the docker group:

sudo usermod -aG docker $USER
newgrp docker

Setup trdl which will manage werf installation and updates:

# Add ~/bin to the PATH.
echo 'export PATH=$HOME/bin:$PATH' >> ~/.bash_profile
export PATH="$HOME/bin:$PATH"

# Install trdl.
curl -L "https://tuf.trdl.dev/targets/releases/0.1.3/linux-amd64/bin/trdl" -o /tmp/trdl
mkdir -p ~/bin
install /tmp/trdl ~/bin/trdl

Add werf repo:

trdl add werf https://tuf.werf.io 1 b7ff6bcbe598e072a86d595a3621924c8612c7e6dc6a82e919abe89707d7e3f468e616b5635630680dd1e98fc362ae5051728406700e6274c5ed1ad92bea52a2

To use werf locally in your terminal, we recommend to enable its automatic activation. To make werf available in all new shell sessions, you need to execute this command (just once):

echo 'command -v trdl &>/dev/null && source $(trdl use werf 1.1 alpha)' >> ~/.bashrc

Now, if you log out and log in to the system again, werf will be always available. You can make sure of that by executing:

werf version

To get werf running in your current terminal only (before any logout/login is done), you can simply execute the source $(trdl use werf 1.1 alpha command.

In CI, you need a different approaching with activating werf explicitly in the beginning of each job/pipeline by executing:

source $(trdl use werf 1.1 alpha)

Make sure you have Git 2.18.0 or newer and Docker installed.

To run werf as a regular user, you should have access to the Docker daemon. First, make sure the docker group exists:

sudo groupadd docker

Add your current user to the docker group:

sudo usermod -aG docker $USER
newgrp docker

Setup trdl which will manage werf installation and updates:

# Add ~/bin to the PATH.
echo 'export PATH=$HOME/bin:$PATH' >> ~/.bash_profile
export PATH="$HOME/bin:$PATH"

# Install trdl.
curl -L "https://tuf.trdl.dev/targets/releases/0.1.3/linux-arm64/bin/trdl" -o /tmp/trdl
mkdir -p ~/bin
install /tmp/trdl ~/bin/trdl

Add werf repo:

trdl add werf https://tuf.werf.io 1 b7ff6bcbe598e072a86d595a3621924c8612c7e6dc6a82e919abe89707d7e3f468e616b5635630680dd1e98fc362ae5051728406700e6274c5ed1ad92bea52a2

To use werf locally in your terminal, we recommend to enable its automatic activation. To make werf available in all new shell sessions, you need to execute this command (just once):

echo 'command -v trdl &>/dev/null && source $(trdl use werf 1.1 alpha)' >> ~/.bashrc

Now, if you log out and log in to the system again, werf will be always available. You can make sure of that by executing:

werf version

To get werf running in your current terminal only (before any logout/login is done), you can simply execute the source $(trdl use werf 1.1 alpha command.

In CI, you need a different approaching with activating werf explicitly in the beginning of each job/pipeline by executing:

source $(trdl use werf 1.1 alpha)

Make sure you have Git 2.18.0 or newer and Docker installed.

To run werf as a regular user, you should have access to the Docker daemon. First, make sure the docker group exists:

sudo groupadd docker

Add your current user to the docker group:

sudo usermod -aG docker $USER
newgrp docker

Setup trdl which will manage werf installation and updates:

# Add ~/bin to the PATH.
echo 'export PATH=$HOME/bin:$PATH' >> ~/.bash_profile
export PATH="$HOME/bin:$PATH"

# Install trdl.
curl -L "https://tuf.trdl.dev/targets/releases/0.1.3/linux-amd64/bin/trdl" -o /tmp/trdl
mkdir -p ~/bin
install /tmp/trdl ~/bin/trdl

Add werf repo:

trdl add werf https://tuf.werf.io 1 b7ff6bcbe598e072a86d595a3621924c8612c7e6dc6a82e919abe89707d7e3f468e616b5635630680dd1e98fc362ae5051728406700e6274c5ed1ad92bea52a2

To use werf locally in your terminal, we recommend to enable its automatic activation. To make werf available in all new shell sessions, you need to execute this command (just once):

echo 'command -v trdl &>/dev/null && source $(trdl use werf 1.1 beta)' >> ~/.bashrc

Now, if you log out and log in to the system again, werf will be always available. You can make sure of that by executing:

werf version

To get werf running in your current terminal only (before any logout/login is done), you can simply execute the source $(trdl use werf 1.1 beta command.

In CI, you need a different approaching with activating werf explicitly in the beginning of each job/pipeline by executing:

source $(trdl use werf 1.1 beta)

Make sure you have Git 2.18.0 or newer and Docker installed.

To run werf as a regular user, you should have access to the Docker daemon. First, make sure the docker group exists:

sudo groupadd docker

Add your current user to the docker group:

sudo usermod -aG docker $USER
newgrp docker

Setup trdl which will manage werf installation and updates:

# Add ~/bin to the PATH.
echo 'export PATH=$HOME/bin:$PATH' >> ~/.bash_profile
export PATH="$HOME/bin:$PATH"

# Install trdl.
curl -L "https://tuf.trdl.dev/targets/releases/0.1.3/linux-arm64/bin/trdl" -o /tmp/trdl
mkdir -p ~/bin
install /tmp/trdl ~/bin/trdl

Add werf repo:

trdl add werf https://tuf.werf.io 1 b7ff6bcbe598e072a86d595a3621924c8612c7e6dc6a82e919abe89707d7e3f468e616b5635630680dd1e98fc362ae5051728406700e6274c5ed1ad92bea52a2

To use werf locally in your terminal, we recommend to enable its automatic activation. To make werf available in all new shell sessions, you need to execute this command (just once):

echo 'command -v trdl &>/dev/null && source $(trdl use werf 1.1 beta)' >> ~/.bashrc

Now, if you log out and log in to the system again, werf will be always available. You can make sure of that by executing:

werf version

To get werf running in your current terminal only (before any logout/login is done), you can simply execute the source $(trdl use werf 1.1 beta command.

In CI, you need a different approaching with activating werf explicitly in the beginning of each job/pipeline by executing:

source $(trdl use werf 1.1 beta)

Make sure you have Git 2.18.0 or newer and Docker installed.

To run werf as a regular user, you should have access to the Docker daemon. First, make sure the docker group exists:

sudo groupadd docker

Add your current user to the docker group:

sudo usermod -aG docker $USER
newgrp docker

Setup trdl which will manage werf installation and updates:

# Add ~/bin to the PATH.
echo 'export PATH=$HOME/bin:$PATH' >> ~/.bash_profile
export PATH="$HOME/bin:$PATH"

# Install trdl.
curl -L "https://tuf.trdl.dev/targets/releases/0.1.3/linux-amd64/bin/trdl" -o /tmp/trdl
mkdir -p ~/bin
install /tmp/trdl ~/bin/trdl

Add werf repo:

trdl add werf https://tuf.werf.io 1 b7ff6bcbe598e072a86d595a3621924c8612c7e6dc6a82e919abe89707d7e3f468e616b5635630680dd1e98fc362ae5051728406700e6274c5ed1ad92bea52a2

To use werf locally in your terminal, we recommend to enable its automatic activation. To make werf available in all new shell sessions, you need to execute this command (just once):

echo 'command -v trdl &>/dev/null && source $(trdl use werf 1.1 ea)' >> ~/.bashrc

Now, if you log out and log in to the system again, werf will be always available. You can make sure of that by executing:

werf version

To get werf running in your current terminal only (before any logout/login is done), you can simply execute the source $(trdl use werf 1.1 ea command.

In CI, you need a different approaching with activating werf explicitly in the beginning of each job/pipeline by executing:

source $(trdl use werf 1.1 ea)

Make sure you have Git 2.18.0 or newer and Docker installed.

To run werf as a regular user, you should have access to the Docker daemon. First, make sure the docker group exists:

sudo groupadd docker

Add your current user to the docker group:

sudo usermod -aG docker $USER
newgrp docker

Setup trdl which will manage werf installation and updates:

# Add ~/bin to the PATH.
echo 'export PATH=$HOME/bin:$PATH' >> ~/.bash_profile
export PATH="$HOME/bin:$PATH"

# Install trdl.
curl -L "https://tuf.trdl.dev/targets/releases/0.1.3/linux-arm64/bin/trdl" -o /tmp/trdl
mkdir -p ~/bin
install /tmp/trdl ~/bin/trdl

Add werf repo:

trdl add werf https://tuf.werf.io 1 b7ff6bcbe598e072a86d595a3621924c8612c7e6dc6a82e919abe89707d7e3f468e616b5635630680dd1e98fc362ae5051728406700e6274c5ed1ad92bea52a2

To use werf locally in your terminal, we recommend to enable its automatic activation. To make werf available in all new shell sessions, you need to execute this command (just once):

echo 'command -v trdl &>/dev/null && source $(trdl use werf 1.1 ea)' >> ~/.bashrc

Now, if you log out and log in to the system again, werf will be always available. You can make sure of that by executing:

werf version

To get werf running in your current terminal only (before any logout/login is done), you can simply execute the source $(trdl use werf 1.1 ea command.

In CI, you need a different approaching with activating werf explicitly in the beginning of each job/pipeline by executing:

source $(trdl use werf 1.1 ea)

Make sure you have Git 2.18.0 or newer and Docker installed.

To run werf as a regular user, you should have access to the Docker daemon. First, make sure the docker group exists:

sudo groupadd docker

Add your current user to the docker group:

sudo usermod -aG docker $USER
newgrp docker

Setup trdl which will manage werf installation and updates:

# Add ~/bin to the PATH.
echo 'export PATH=$HOME/bin:$PATH' >> ~/.bash_profile
export PATH="$HOME/bin:$PATH"

# Install trdl.
curl -L "https://tuf.trdl.dev/targets/releases/0.1.3/linux-amd64/bin/trdl" -o /tmp/trdl
mkdir -p ~/bin
install /tmp/trdl ~/bin/trdl

Add werf repo:

trdl add werf https://tuf.werf.io 1 b7ff6bcbe598e072a86d595a3621924c8612c7e6dc6a82e919abe89707d7e3f468e616b5635630680dd1e98fc362ae5051728406700e6274c5ed1ad92bea52a2

To use werf locally in your terminal, we recommend to enable its automatic activation. To make werf available in all new shell sessions, you need to execute this command (just once):

echo 'command -v trdl &>/dev/null && source $(trdl use werf 1.1 stable)' >> ~/.bashrc

Now, if you log out and log in to the system again, werf will be always available. You can make sure of that by executing:

werf version

To get werf running in your current terminal only (before any logout/login is done), you can simply execute the source $(trdl use werf 1.1 stable command.

In CI, you need a different approaching with activating werf explicitly in the beginning of each job/pipeline by executing:

source $(trdl use werf 1.1 stable)

Make sure you have Git 2.18.0 or newer and Docker installed.

To run werf as a regular user, you should have access to the Docker daemon. First, make sure the docker group exists:

sudo groupadd docker

Add your current user to the docker group:

sudo usermod -aG docker $USER
newgrp docker

Setup trdl which will manage werf installation and updates:

# Add ~/bin to the PATH.
echo 'export PATH=$HOME/bin:$PATH' >> ~/.bash_profile
export PATH="$HOME/bin:$PATH"

# Install trdl.
curl -L "https://tuf.trdl.dev/targets/releases/0.1.3/linux-arm64/bin/trdl" -o /tmp/trdl
mkdir -p ~/bin
install /tmp/trdl ~/bin/trdl

Add werf repo:

trdl add werf https://tuf.werf.io 1 b7ff6bcbe598e072a86d595a3621924c8612c7e6dc6a82e919abe89707d7e3f468e616b5635630680dd1e98fc362ae5051728406700e6274c5ed1ad92bea52a2

To use werf locally in your terminal, we recommend to enable its automatic activation. To make werf available in all new shell sessions, you need to execute this command (just once):

echo 'command -v trdl &>/dev/null && source $(trdl use werf 1.1 stable)' >> ~/.bashrc

Now, if you log out and log in to the system again, werf will be always available. You can make sure of that by executing:

werf version

To get werf running in your current terminal only (before any logout/login is done), you can simply execute the source $(trdl use werf 1.1 stable command.

In CI, you need a different approaching with activating werf explicitly in the beginning of each job/pipeline by executing:

source $(trdl use werf 1.1 stable)

Make sure you have Git 2.18.0 or newer and Docker installed.

To run werf as a regular user, you should have access to the Docker daemon. First, make sure the docker group exists:

sudo groupadd docker

Add your current user to the docker group:

sudo usermod -aG docker $USER
newgrp docker

Setup trdl which will manage werf installation and updates:

# Add ~/bin to the PATH.
echo 'export PATH=$HOME/bin:$PATH' >> ~/.bash_profile
export PATH="$HOME/bin:$PATH"

# Install trdl.
curl -L "https://tuf.trdl.dev/targets/releases/0.1.3/linux-amd64/bin/trdl" -o /tmp/trdl
mkdir -p ~/bin
install /tmp/trdl ~/bin/trdl

Add werf repo:

trdl add werf https://tuf.werf.io 1 b7ff6bcbe598e072a86d595a3621924c8612c7e6dc6a82e919abe89707d7e3f468e616b5635630680dd1e98fc362ae5051728406700e6274c5ed1ad92bea52a2

To use werf locally in your terminal, we recommend to enable its automatic activation. To make werf available in all new shell sessions, you need to execute this command (just once):

echo 'command -v trdl &>/dev/null && source $(trdl use werf 1.1 rock-solid)' >> ~/.bashrc

Now, if you log out and log in to the system again, werf will be always available. You can make sure of that by executing:

werf version

To get werf running in your current terminal only (before any logout/login is done), you can simply execute the source $(trdl use werf 1.1 rock-solid command.

In CI, you need a different approaching with activating werf explicitly in the beginning of each job/pipeline by executing:

source $(trdl use werf 1.1 rock-solid)

Make sure you have Git 2.18.0 or newer and Docker installed.

To run werf as a regular user, you should have access to the Docker daemon. First, make sure the docker group exists:

sudo groupadd docker

Add your current user to the docker group:

sudo usermod -aG docker $USER
newgrp docker

Setup trdl which will manage werf installation and updates:

# Add ~/bin to the PATH.
echo 'export PATH=$HOME/bin:$PATH' >> ~/.bash_profile
export PATH="$HOME/bin:$PATH"

# Install trdl.
curl -L "https://tuf.trdl.dev/targets/releases/0.1.3/linux-arm64/bin/trdl" -o /tmp/trdl
mkdir -p ~/bin
install /tmp/trdl ~/bin/trdl

Add werf repo:

trdl add werf https://tuf.werf.io 1 b7ff6bcbe598e072a86d595a3621924c8612c7e6dc6a82e919abe89707d7e3f468e616b5635630680dd1e98fc362ae5051728406700e6274c5ed1ad92bea52a2

To use werf locally in your terminal, we recommend to enable its automatic activation. To make werf available in all new shell sessions, you need to execute this command (just once):

echo 'command -v trdl &>/dev/null && source $(trdl use werf 1.1 rock-solid)' >> ~/.bashrc

Now, if you log out and log in to the system again, werf will be always available. You can make sure of that by executing:

werf version

To get werf running in your current terminal only (before any logout/login is done), you can simply execute the source $(trdl use werf 1.1 rock-solid command.

In CI, you need a different approaching with activating werf explicitly in the beginning of each job/pipeline by executing:

source $(trdl use werf 1.1 rock-solid)

Make sure you have Git 2.18.0 or newer and Docker installed.

Setup trdl which will manage werf installation and updates:

# Add ~/bin to the PATH.
echo 'export PATH=$HOME/bin:$PATH' >> ~/.zprofile
export PATH="$HOME/bin:$PATH"

# Install trdl.
curl -L "https://tuf.trdl.dev/targets/releases/0.1.3/darwin-amd64/bin/trdl" -o /tmp/trdl
mkdir -p ~/bin
install /tmp/trdl ~/bin/trdl

Add werf repo:

trdl add werf https://tuf.werf.io 1 b7ff6bcbe598e072a86d595a3621924c8612c7e6dc6a82e919abe89707d7e3f468e616b5635630680dd1e98fc362ae5051728406700e6274c5ed1ad92bea52a2

To use werf locally in your terminal, we recommend to enable its automatic activation. To make werf available in all new shell sessions, you need to execute this command (just once):

echo 'source $(trdl use werf 1.2 alpha)' >> ~/.zshrc

Now, if you log out and log in to the system again, werf will be always available. You can make sure of that by executing:

werf version

To get werf running in your current terminal only (before any logout/login is done), you can simply execute the source $(trdl use werf 1.2 alpha) command.

In CI, you need a different approaching with activating werf explicitly in the beginning of each job/pipeline by executing:

source $(trdl use werf 1.2 alpha)

Make sure you have Git 2.18.0 or newer and Docker installed.

Setup trdl which will manage werf installation and updates:

# Add ~/bin to the PATH.
echo 'export PATH=$HOME/bin:$PATH' >> ~/.zprofile
export PATH="$HOME/bin:$PATH"

# Install trdl.
curl -L "https://tuf.trdl.dev/targets/releases/0.1.3/darwin-arm64/bin/trdl" -o /tmp/trdl
mkdir -p ~/bin
install /tmp/trdl ~/bin/trdl

Add werf repo:

trdl add werf https://tuf.werf.io 1 b7ff6bcbe598e072a86d595a3621924c8612c7e6dc6a82e919abe89707d7e3f468e616b5635630680dd1e98fc362ae5051728406700e6274c5ed1ad92bea52a2

To use werf locally in your terminal, we recommend to enable its automatic activation. To make werf available in all new shell sessions, you need to execute this command (just once):

echo 'source $(trdl use werf 1.2 alpha)' >> ~/.zshrc

Now, if you log out and log in to the system again, werf will be always available. You can make sure of that by executing:

werf version

To get werf running in your current terminal only (before any logout/login is done), you can simply execute the source $(trdl use werf 1.2 alpha) command.

In CI, you need a different approaching with activating werf explicitly in the beginning of each job/pipeline by executing:

source $(trdl use werf 1.2 alpha)

Make sure you have Git 2.18.0 or newer and Docker installed.

Setup trdl which will manage werf installation and updates:

# Add ~/bin to the PATH.
echo 'export PATH=$HOME/bin:$PATH' >> ~/.zprofile
export PATH="$HOME/bin:$PATH"

# Install trdl.
curl -L "https://tuf.trdl.dev/targets/releases/0.1.3/darwin-amd64/bin/trdl" -o /tmp/trdl
mkdir -p ~/bin
install /tmp/trdl ~/bin/trdl

Add werf repo:

trdl add werf https://tuf.werf.io 1 b7ff6bcbe598e072a86d595a3621924c8612c7e6dc6a82e919abe89707d7e3f468e616b5635630680dd1e98fc362ae5051728406700e6274c5ed1ad92bea52a2

To use werf locally in your terminal, we recommend to enable its automatic activation. To make werf available in all new shell sessions, you need to execute this command (just once):

echo 'source $(trdl use werf 1.2 beta)' >> ~/.zshrc

Now, if you log out and log in to the system again, werf will be always available. You can make sure of that by executing:

werf version

To get werf running in your current terminal only (before any logout/login is done), you can simply execute the source $(trdl use werf 1.2 beta) command.

In CI, you need a different approaching with activating werf explicitly in the beginning of each job/pipeline by executing:

source $(trdl use werf 1.2 beta)

Make sure you have Git 2.18.0 or newer and Docker installed.

Setup trdl which will manage werf installation and updates:

# Add ~/bin to the PATH.
echo 'export PATH=$HOME/bin:$PATH' >> ~/.zprofile
export PATH="$HOME/bin:$PATH"

# Install trdl.
curl -L "https://tuf.trdl.dev/targets/releases/0.1.3/darwin-arm64/bin/trdl" -o /tmp/trdl
mkdir -p ~/bin
install /tmp/trdl ~/bin/trdl

Add werf repo:

trdl add werf https://tuf.werf.io 1 b7ff6bcbe598e072a86d595a3621924c8612c7e6dc6a82e919abe89707d7e3f468e616b5635630680dd1e98fc362ae5051728406700e6274c5ed1ad92bea52a2

To use werf locally in your terminal, we recommend to enable its automatic activation. To make werf available in all new shell sessions, you need to execute this command (just once):

echo 'source $(trdl use werf 1.2 beta)' >> ~/.zshrc

Now, if you log out and log in to the system again, werf will be always available. You can make sure of that by executing:

werf version

To get werf running in your current terminal only (before any logout/login is done), you can simply execute the source $(trdl use werf 1.2 beta) command.

In CI, you need a different approaching with activating werf explicitly in the beginning of each job/pipeline by executing:

source $(trdl use werf 1.2 beta)

Make sure you have Git 2.18.0 or newer and Docker installed.

Setup trdl which will manage werf installation and updates:

# Add ~/bin to the PATH.
echo 'export PATH=$HOME/bin:$PATH' >> ~/.zprofile
export PATH="$HOME/bin:$PATH"

# Install trdl.
curl -L "https://tuf.trdl.dev/targets/releases/0.1.3/darwin-amd64/bin/trdl" -o /tmp/trdl
mkdir -p ~/bin
install /tmp/trdl ~/bin/trdl

Add werf repo:

trdl add werf https://tuf.werf.io 1 b7ff6bcbe598e072a86d595a3621924c8612c7e6dc6a82e919abe89707d7e3f468e616b5635630680dd1e98fc362ae5051728406700e6274c5ed1ad92bea52a2

To use werf locally in your terminal, we recommend to enable its automatic activation. To make werf available in all new shell sessions, you need to execute this command (just once):

echo 'source $(trdl use werf 1.2 ea)' >> ~/.zshrc

Now, if you log out and log in to the system again, werf will be always available. You can make sure of that by executing:

werf version

To get werf running in your current terminal only (before any logout/login is done), you can simply execute the source $(trdl use werf 1.2 ea) command.

In CI, you need a different approaching with activating werf explicitly in the beginning of each job/pipeline by executing:

source $(trdl use werf 1.2 ea)

Make sure you have Git 2.18.0 or newer and Docker installed.

Setup trdl which will manage werf installation and updates:

# Add ~/bin to the PATH.
echo 'export PATH=$HOME/bin:$PATH' >> ~/.zprofile
export PATH="$HOME/bin:$PATH"

# Install trdl.
curl -L "https://tuf.trdl.dev/targets/releases/0.1.3/darwin-arm64/bin/trdl" -o /tmp/trdl
mkdir -p ~/bin
install /tmp/trdl ~/bin/trdl

Add werf repo:

trdl add werf https://tuf.werf.io 1 b7ff6bcbe598e072a86d595a3621924c8612c7e6dc6a82e919abe89707d7e3f468e616b5635630680dd1e98fc362ae5051728406700e6274c5ed1ad92bea52a2

To use werf locally in your terminal, we recommend to enable its automatic activation. To make werf available in all new shell sessions, you need to execute this command (just once):

echo 'source $(trdl use werf 1.2 ea)' >> ~/.zshrc

Now, if you log out and log in to the system again, werf will be always available. You can make sure of that by executing:

werf version

To get werf running in your current terminal only (before any logout/login is done), you can simply execute the source $(trdl use werf 1.2 ea) command.

In CI, you need a different approaching with activating werf explicitly in the beginning of each job/pipeline by executing:

source $(trdl use werf 1.2 ea)

Make sure you have Git 2.18.0 or newer and Docker installed.

Setup trdl which will manage werf installation and updates:

# Add ~/bin to the PATH.
echo 'export PATH=$HOME/bin:$PATH' >> ~/.zprofile
export PATH="$HOME/bin:$PATH"

# Install trdl.
curl -L "https://tuf.trdl.dev/targets/releases/0.1.3/darwin-amd64/bin/trdl" -o /tmp/trdl
mkdir -p ~/bin
install /tmp/trdl ~/bin/trdl

Add werf repo:

trdl add werf https://tuf.werf.io 1 b7ff6bcbe598e072a86d595a3621924c8612c7e6dc6a82e919abe89707d7e3f468e616b5635630680dd1e98fc362ae5051728406700e6274c5ed1ad92bea52a2

To use werf locally in your terminal, we recommend to enable its automatic activation. To make werf available in all new shell sessions, you need to execute this command (just once):

echo 'source $(trdl use werf 1.2 stable)' >> ~/.zshrc

Now, if you log out and log in to the system again, werf will be always available. You can make sure of that by executing:

werf version

To get werf running in your current terminal only (before any logout/login is done), you can simply execute the source $(trdl use werf 1.2 stable) command.

In CI, you need a different approaching with activating werf explicitly in the beginning of each job/pipeline by executing:

source $(trdl use werf 1.2 stable)

Make sure you have Git 2.18.0 or newer and Docker installed.

Setup trdl which will manage werf installation and updates:

# Add ~/bin to the PATH.
echo 'export PATH=$HOME/bin:$PATH' >> ~/.zprofile
export PATH="$HOME/bin:$PATH"

# Install trdl.
curl -L "https://tuf.trdl.dev/targets/releases/0.1.3/darwin-arm64/bin/trdl" -o /tmp/trdl
mkdir -p ~/bin
install /tmp/trdl ~/bin/trdl

Add werf repo:

trdl add werf https://tuf.werf.io 1 b7ff6bcbe598e072a86d595a3621924c8612c7e6dc6a82e919abe89707d7e3f468e616b5635630680dd1e98fc362ae5051728406700e6274c5ed1ad92bea52a2

To use werf locally in your terminal, we recommend to enable its automatic activation. To make werf available in all new shell sessions, you need to execute this command (just once):

echo 'source $(trdl use werf 1.2 stable)' >> ~/.zshrc

Now, if you log out and log in to the system again, werf will be always available. You can make sure of that by executing:

werf version

To get werf running in your current terminal only (before any logout/login is done), you can simply execute the source $(trdl use werf 1.2 stable) command.

In CI, you need a different approaching with activating werf explicitly in the beginning of each job/pipeline by executing:

source $(trdl use werf 1.2 stable)

Make sure you have Git 2.18.0 or newer and Docker installed.

Setup trdl which will manage werf installation and updates:

# Add ~/bin to the PATH.
echo 'export PATH=$HOME/bin:$PATH' >> ~/.zprofile
export PATH="$HOME/bin:$PATH"

# Install trdl.
curl -L "https://tuf.trdl.dev/targets/releases/0.1.3/darwin-amd64/bin/trdl" -o /tmp/trdl
mkdir -p ~/bin
install /tmp/trdl ~/bin/trdl

Add werf repo:

trdl add werf https://tuf.werf.io 1 b7ff6bcbe598e072a86d595a3621924c8612c7e6dc6a82e919abe89707d7e3f468e616b5635630680dd1e98fc362ae5051728406700e6274c5ed1ad92bea52a2

To use werf locally in your terminal, we recommend to enable its automatic activation. To make werf available in all new shell sessions, you need to execute this command (just once):

echo 'source $(trdl use werf 1.2 rock-solid)' >> ~/.zshrc

Now, if you log out and log in to the system again, werf will be always available. You can make sure of that by executing:

werf version

To get werf running in your current terminal only (before any logout/login is done), you can simply execute the source $(trdl use werf 1.2 rock-solid) command.

In CI, you need a different approaching with activating werf explicitly in the beginning of each job/pipeline by executing:

source $(trdl use werf 1.2 rock-solid)

Make sure you have Git 2.18.0 or newer and Docker installed.

Setup trdl which will manage werf installation and updates:

# Add ~/bin to the PATH.
echo 'export PATH=$HOME/bin:$PATH' >> ~/.zprofile
export PATH="$HOME/bin:$PATH"

# Install trdl.
curl -L "https://tuf.trdl.dev/targets/releases/0.1.3/darwin-arm64/bin/trdl" -o /tmp/trdl
mkdir -p ~/bin
install /tmp/trdl ~/bin/trdl

Add werf repo:

trdl add werf https://tuf.werf.io 1 b7ff6bcbe598e072a86d595a3621924c8612c7e6dc6a82e919abe89707d7e3f468e616b5635630680dd1e98fc362ae5051728406700e6274c5ed1ad92bea52a2

To use werf locally in your terminal, we recommend to enable its automatic activation. To make werf available in all new shell sessions, you need to execute this command (just once):

echo 'source $(trdl use werf 1.2 rock-solid)' >> ~/.zshrc

Now, if you log out and log in to the system again, werf will be always available. You can make sure of that by executing:

werf version

To get werf running in your current terminal only (before any logout/login is done), you can simply execute the source $(trdl use werf 1.2 rock-solid) command.

In CI, you need a different approaching with activating werf explicitly in the beginning of each job/pipeline by executing:

source $(trdl use werf 1.2 rock-solid)

Make sure you have Git 2.18.0 or newer and Docker installed.

Setup trdl which will manage werf installation and updates:

# Add ~/bin to the PATH.
echo 'export PATH=$HOME/bin:$PATH' >> ~/.zprofile
export PATH="$HOME/bin:$PATH"

# Install trdl.
curl -L "https://tuf.trdl.dev/targets/releases/0.1.3/darwin-amd64/bin/trdl" -o /tmp/trdl
mkdir -p ~/bin
install /tmp/trdl ~/bin/trdl

Add werf repo:

trdl add werf https://tuf.werf.io 1 b7ff6bcbe598e072a86d595a3621924c8612c7e6dc6a82e919abe89707d7e3f468e616b5635630680dd1e98fc362ae5051728406700e6274c5ed1ad92bea52a2

To use werf locally in your terminal, we recommend to enable its automatic activation. To make werf available in all new shell sessions, you need to execute this command (just once):

echo 'source $(trdl use werf 1.1 alpha)' >> ~/.zshrc

Now, if you log out and log in to the system again, werf will be always available. You can make sure of that by executing:

werf version

To get werf running in your current terminal only (before any logout/login is done), you can simply execute the source $(trdl use werf 1.1 alpha) command.

In CI, you need a different approaching with activating werf explicitly in the beginning of each job/pipeline by executing:

source $(trdl use werf 1.1 alpha)

Make sure you have Git 2.18.0 or newer and Docker installed.

Setup trdl which will manage werf installation and updates:

# Add ~/bin to the PATH.
echo 'export PATH=$HOME/bin:$PATH' >> ~/.zprofile
export PATH="$HOME/bin:$PATH"

# Install trdl.
curl -L "https://tuf.trdl.dev/targets/releases/0.1.3/darwin-arm64/bin/trdl" -o /tmp/trdl
mkdir -p ~/bin
install /tmp/trdl ~/bin/trdl

Add werf repo:

trdl add werf https://tuf.werf.io 1 b7ff6bcbe598e072a86d595a3621924c8612c7e6dc6a82e919abe89707d7e3f468e616b5635630680dd1e98fc362ae5051728406700e6274c5ed1ad92bea52a2

To use werf locally in your terminal, we recommend to enable its automatic activation. To make werf available in all new shell sessions, you need to execute this command (just once):

echo 'source $(trdl use werf 1.1 alpha)' >> ~/.zshrc

Now, if you log out and log in to the system again, werf will be always available. You can make sure of that by executing:

werf version

To get werf running in your current terminal only (before any logout/login is done), you can simply execute the source $(trdl use werf 1.1 alpha) command.

In CI, you need a different approaching with activating werf explicitly in the beginning of each job/pipeline by executing:

source $(trdl use werf 1.1 alpha)

Make sure you have Git 2.18.0 or newer and Docker installed.

Setup trdl which will manage werf installation and updates:

# Add ~/bin to the PATH.
echo 'export PATH=$HOME/bin:$PATH' >> ~/.zprofile
export PATH="$HOME/bin:$PATH"

# Install trdl.
curl -L "https://tuf.trdl.dev/targets/releases/0.1.3/darwin-amd64/bin/trdl" -o /tmp/trdl
mkdir -p ~/bin
install /tmp/trdl ~/bin/trdl

Add werf repo:

trdl add werf https://tuf.werf.io 1 b7ff6bcbe598e072a86d595a3621924c8612c7e6dc6a82e919abe89707d7e3f468e616b5635630680dd1e98fc362ae5051728406700e6274c5ed1ad92bea52a2

To use werf locally in your terminal, we recommend to enable its automatic activation. To make werf available in all new shell sessions, you need to execute this command (just once):

echo 'source $(trdl use werf 1.1 beta)' >> ~/.zshrc

Now, if you log out and log in to the system again, werf will be always available. You can make sure of that by executing:

werf version

To get werf running in your current terminal only (before any logout/login is done), you can simply execute the source $(trdl use werf 1.1 beta) command.

In CI, you need a different approaching with activating werf explicitly in the beginning of each job/pipeline by executing:

source $(trdl use werf 1.1 beta)

Make sure you have Git 2.18.0 or newer and Docker installed.

Setup trdl which will manage werf installation and updates:

# Add ~/bin to the PATH.
echo 'export PATH=$HOME/bin:$PATH' >> ~/.zprofile
export PATH="$HOME/bin:$PATH"

# Install trdl.
curl -L "https://tuf.trdl.dev/targets/releases/0.1.3/darwin-arm64/bin/trdl" -o /tmp/trdl
mkdir -p ~/bin
install /tmp/trdl ~/bin/trdl

Add werf repo:

trdl add werf https://tuf.werf.io 1 b7ff6bcbe598e072a86d595a3621924c8612c7e6dc6a82e919abe89707d7e3f468e616b5635630680dd1e98fc362ae5051728406700e6274c5ed1ad92bea52a2

To use werf locally in your terminal, we recommend to enable its automatic activation. To make werf available in all new shell sessions, you need to execute this command (just once):

echo 'source $(trdl use werf 1.1 beta)' >> ~/.zshrc

Now, if you log out and log in to the system again, werf will be always available. You can make sure of that by executing:

werf version

To get werf running in your current terminal only (before any logout/login is done), you can simply execute the source $(trdl use werf 1.1 beta) command.

In CI, you need a different approaching with activating werf explicitly in the beginning of each job/pipeline by executing:

source $(trdl use werf 1.1 beta)

Make sure you have Git 2.18.0 or newer and Docker installed.

Setup trdl which will manage werf installation and updates:

# Add ~/bin to the PATH.
echo 'export PATH=$HOME/bin:$PATH' >> ~/.zprofile
export PATH="$HOME/bin:$PATH"

# Install trdl.
curl -L "https://tuf.trdl.dev/targets/releases/0.1.3/darwin-amd64/bin/trdl" -o /tmp/trdl
mkdir -p ~/bin
install /tmp/trdl ~/bin/trdl

Add werf repo:

trdl add werf https://tuf.werf.io 1 b7ff6bcbe598e072a86d595a3621924c8612c7e6dc6a82e919abe89707d7e3f468e616b5635630680dd1e98fc362ae5051728406700e6274c5ed1ad92bea52a2

To use werf locally in your terminal, we recommend to enable its automatic activation. To make werf available in all new shell sessions, you need to execute this command (just once):

echo 'source $(trdl use werf 1.1 ea)' >> ~/.zshrc

Now, if you log out and log in to the system again, werf will be always available. You can make sure of that by executing:

werf version

To get werf running in your current terminal only (before any logout/login is done), you can simply execute the source $(trdl use werf 1.1 ea) command.

In CI, you need a different approaching with activating werf explicitly in the beginning of each job/pipeline by executing:

source $(trdl use werf 1.1 ea)

Make sure you have Git 2.18.0 or newer and Docker installed.

Setup trdl which will manage werf installation and updates:

# Add ~/bin to the PATH.
echo 'export PATH=$HOME/bin:$PATH' >> ~/.zprofile
export PATH="$HOME/bin:$PATH"

# Install trdl.
curl -L "https://tuf.trdl.dev/targets/releases/0.1.3/darwin-arm64/bin/trdl" -o /tmp/trdl
mkdir -p ~/bin
install /tmp/trdl ~/bin/trdl

Add werf repo:

trdl add werf https://tuf.werf.io 1 b7ff6bcbe598e072a86d595a3621924c8612c7e6dc6a82e919abe89707d7e3f468e616b5635630680dd1e98fc362ae5051728406700e6274c5ed1ad92bea52a2

To use werf locally in your terminal, we recommend to enable its automatic activation. To make werf available in all new shell sessions, you need to execute this command (just once):

echo 'source $(trdl use werf 1.1 ea)' >> ~/.zshrc

Now, if you log out and log in to the system again, werf will be always available. You can make sure of that by executing:

werf version

To get werf running in your current terminal only (before any logout/login is done), you can simply execute the source $(trdl use werf 1.1 ea) command.

In CI, you need a different approaching with activating werf explicitly in the beginning of each job/pipeline by executing:

source $(trdl use werf 1.1 ea)

Make sure you have Git 2.18.0 or newer and Docker installed.

Setup trdl which will manage werf installation and updates:

# Add ~/bin to the PATH.
echo 'export PATH=$HOME/bin:$PATH' >> ~/.zprofile
export PATH="$HOME/bin:$PATH"

# Install trdl.
curl -L "https://tuf.trdl.dev/targets/releases/0.1.3/darwin-amd64/bin/trdl" -o /tmp/trdl
mkdir -p ~/bin
install /tmp/trdl ~/bin/trdl

Add werf repo:

trdl add werf https://tuf.werf.io 1 b7ff6bcbe598e072a86d595a3621924c8612c7e6dc6a82e919abe89707d7e3f468e616b5635630680dd1e98fc362ae5051728406700e6274c5ed1ad92bea52a2

To use werf locally in your terminal, we recommend to enable its automatic activation. To make werf available in all new shell sessions, you need to execute this command (just once):

echo 'source $(trdl use werf 1.1 stable)' >> ~/.zshrc

Now, if you log out and log in to the system again, werf will be always available. You can make sure of that by executing:

werf version

To get werf running in your current terminal only (before any logout/login is done), you can simply execute the source $(trdl use werf 1.1 stable) command.

In CI, you need a different approaching with activating werf explicitly in the beginning of each job/pipeline by executing:

source $(trdl use werf 1.1 stable)

Make sure you have Git 2.18.0 or newer and Docker installed.

Setup trdl which will manage werf installation and updates:

# Add ~/bin to the PATH.
echo 'export PATH=$HOME/bin:$PATH' >> ~/.zprofile
export PATH="$HOME/bin:$PATH"

# Install trdl.
curl -L "https://tuf.trdl.dev/targets/releases/0.1.3/darwin-arm64/bin/trdl" -o /tmp/trdl
mkdir -p ~/bin
install /tmp/trdl ~/bin/trdl

Add werf repo:

trdl add werf https://tuf.werf.io 1 b7ff6bcbe598e072a86d595a3621924c8612c7e6dc6a82e919abe89707d7e3f468e616b5635630680dd1e98fc362ae5051728406700e6274c5ed1ad92bea52a2

To use werf locally in your terminal, we recommend to enable its automatic activation. To make werf available in all new shell sessions, you need to execute this command (just once):

echo 'source $(trdl use werf 1.1 stable)' >> ~/.zshrc

Now, if you log out and log in to the system again, werf will be always available. You can make sure of that by executing:

werf version

To get werf running in your current terminal only (before any logout/login is done), you can simply execute the source $(trdl use werf 1.1 stable) command.

In CI, you need a different approaching with activating werf explicitly in the beginning of each job/pipeline by executing:

source $(trdl use werf 1.1 stable)

Make sure you have Git 2.18.0 or newer and Docker installed.

Setup trdl which will manage werf installation and updates:

# Add ~/bin to the PATH.
echo 'export PATH=$HOME/bin:$PATH' >> ~/.zprofile
export PATH="$HOME/bin:$PATH"

# Install trdl.
curl -L "https://tuf.trdl.dev/targets/releases/0.1.3/darwin-amd64/bin/trdl" -o /tmp/trdl
mkdir -p ~/bin
install /tmp/trdl ~/bin/trdl

Add werf repo:

trdl add werf https://tuf.werf.io 1 b7ff6bcbe598e072a86d595a3621924c8612c7e6dc6a82e919abe89707d7e3f468e616b5635630680dd1e98fc362ae5051728406700e6274c5ed1ad92bea52a2

To use werf locally in your terminal, we recommend to enable its automatic activation. To make werf available in all new shell sessions, you need to execute this command (just once):

echo 'source $(trdl use werf 1.1 rock-solid)' >> ~/.zshrc

Now, if you log out and log in to the system again, werf will be always available. You can make sure of that by executing:

werf version

To get werf running in your current terminal only (before any logout/login is done), you can simply execute the source $(trdl use werf 1.1 rock-solid) command.

In CI, you need a different approaching with activating werf explicitly in the beginning of each job/pipeline by executing:

source $(trdl use werf 1.1 rock-solid)

Make sure you have Git 2.18.0 or newer and Docker installed.

Setup trdl which will manage werf installation and updates:

# Add ~/bin to the PATH.
echo 'export PATH=$HOME/bin:$PATH' >> ~/.zprofile
export PATH="$HOME/bin:$PATH"

# Install trdl.
curl -L "https://tuf.trdl.dev/targets/releases/0.1.3/darwin-arm64/bin/trdl" -o /tmp/trdl
mkdir -p ~/bin
install /tmp/trdl ~/bin/trdl

Add werf repo:

trdl add werf https://tuf.werf.io 1 b7ff6bcbe598e072a86d595a3621924c8612c7e6dc6a82e919abe89707d7e3f468e616b5635630680dd1e98fc362ae5051728406700e6274c5ed1ad92bea52a2

To use werf locally in your terminal, we recommend to enable its automatic activation. To make werf available in all new shell sessions, you need to execute this command (just once):

echo 'source $(trdl use werf 1.1 rock-solid)' >> ~/.zshrc

Now, if you log out and log in to the system again, werf will be always available. You can make sure of that by executing:

werf version

To get werf running in your current terminal only (before any logout/login is done), you can simply execute the source $(trdl use werf 1.1 rock-solid) command.

In CI, you need a different approaching with activating werf explicitly in the beginning of each job/pipeline by executing:

source $(trdl use werf 1.1 rock-solid)

Make sure you have Git 2.18.0 or newer and Docker installed.

Following instructions should be executed in the PowerShell.

Setup trdl which will manage werf installation and updates:

# Add %USERPROFILE%\bin to the PATH.
[Environment]::SetEnvironmentVariable("Path", "$env:USERPROFILE\bin" + [Environment]::GetEnvironmentVariable("Path", "User"), "User")
$env:Path = "$env:USERPROFILE\bin;$env:Path"

# Install trdl.
mkdir -Force "$env:USERPROFILE\bin"
Invoke-WebRequest -Uri "https://tuf.trdl.dev/targets/releases/0.1.3/windows-amd64/bin/trdl.exe" -OutFile "$env:USERPROFILE\bin\trdl.exe"

Add werf repo:

trdl add werf https://tuf.werf.io 1 b7ff6bcbe598e072a86d595a3621924c8612c7e6dc6a82e919abe89707d7e3f468e616b5635630680dd1e98fc362ae5051728406700e6274c5ed1ad92bea52a2

To use werf locally in your terminal, we recommend to enable its automatic activation. To make werf available in all new PowerShell sessions, you need to execute this command (just once, run under Administrator):

# Allow execution of locally created scripts.
Set-ExecutionPolicy RemoteSigned -Scope CurrentUser

# Activate werf binary automatically during PowerShell initializations.
if (!(Test-Path "$profile")) {
  New-Item -Path "$profile" -Force
}
Add-Content -Path "$profile" -Value '. $(trdl use werf 1.2 alpha)'

Now, if you log out and log in to the system again, werf will be always available. You can make sure of that by executing:

werf version

To get werf running in your current terminal only (before any logout/login is done), you can simply execute the . $(trdl use werf 1.2 alpha) command.

In CI, you need a different approaching with activating werf explicitly in the beginning of each job/pipeline by executing:

. $(trdl use werf 1.2 alpha)

Make sure you have Git 2.18.0 or newer and Docker installed.

Following instructions should be executed in the PowerShell.

Setup trdl which will manage werf installation and updates:

# Add %USERPROFILE%\bin to the PATH.
[Environment]::SetEnvironmentVariable("Path", "$env:USERPROFILE\bin" + [Environment]::GetEnvironmentVariable("Path", "User"), "User")
$env:Path = "$env:USERPROFILE\bin;$env:Path"

# Install trdl.
mkdir -Force "$env:USERPROFILE\bin"
Invoke-WebRequest -Uri "https://tuf.trdl.dev/targets/releases/0.1.3/windows-arm64/bin/trdl.exe" -OutFile "$env:USERPROFILE\bin\trdl.exe"

Add werf repo:

trdl add werf https://tuf.werf.io 1 b7ff6bcbe598e072a86d595a3621924c8612c7e6dc6a82e919abe89707d7e3f468e616b5635630680dd1e98fc362ae5051728406700e6274c5ed1ad92bea52a2

To use werf locally in your terminal, we recommend to enable its automatic activation. To make werf available in all new PowerShell sessions, you need to execute this command (just once, run under Administrator):

# Allow execution of locally created scripts.
Set-ExecutionPolicy RemoteSigned -Scope CurrentUser

# Activate werf binary automatically during PowerShell initializations.
if (!(Test-Path "$profile")) {
  New-Item -Path "$profile" -Force
}
Add-Content -Path "$profile" -Value '. $(trdl use werf 1.2 alpha)'

Now, if you log out and log in to the system again, werf will be always available. You can make sure of that by executing:

werf version

To get werf running in your current terminal only (before any logout/login is done), you can simply execute the . $(trdl use werf 1.2 alpha) command.

In CI, you need a different approaching with activating werf explicitly in the beginning of each job/pipeline by executing:

. $(trdl use werf 1.2 alpha)

Make sure you have Git 2.18.0 or newer and Docker installed.

Following instructions should be executed in the PowerShell.

Setup trdl which will manage werf installation and updates:

# Add %USERPROFILE%\bin to the PATH.
[Environment]::SetEnvironmentVariable("Path", "$env:USERPROFILE\bin" + [Environment]::GetEnvironmentVariable("Path", "User"), "User")
$env:Path = "$env:USERPROFILE\bin;$env:Path"

# Install trdl.
mkdir -Force "$env:USERPROFILE\bin"
Invoke-WebRequest -Uri "https://tuf.trdl.dev/targets/releases/0.1.3/windows-amd64/bin/trdl.exe" -OutFile "$env:USERPROFILE\bin\trdl.exe"

Add werf repo:

trdl add werf https://tuf.werf.io 1 b7ff6bcbe598e072a86d595a3621924c8612c7e6dc6a82e919abe89707d7e3f468e616b5635630680dd1e98fc362ae5051728406700e6274c5ed1ad92bea52a2

To use werf locally in your terminal, we recommend to enable its automatic activation. To make werf available in all new PowerShell sessions, you need to execute this command (just once, run under Administrator):

# Allow execution of locally created scripts.
Set-ExecutionPolicy RemoteSigned -Scope CurrentUser

# Activate werf binary automatically during PowerShell initializations.
if (!(Test-Path "$profile")) {
  New-Item -Path "$profile" -Force
}
Add-Content -Path "$profile" -Value '. $(trdl use werf 1.2 beta)'

Now, if you log out and log in to the system again, werf will be always available. You can make sure of that by executing:

werf version

To get werf running in your current terminal only (before any logout/login is done), you can simply execute the . $(trdl use werf 1.2 beta) command.

In CI, you need a different approaching with activating werf explicitly in the beginning of each job/pipeline by executing:

. $(trdl use werf 1.2 beta)

Make sure you have Git 2.18.0 or newer and Docker installed.

Following instructions should be executed in the PowerShell.

Setup trdl which will manage werf installation and updates:

# Add %USERPROFILE%\bin to the PATH.
[Environment]::SetEnvironmentVariable("Path", "$env:USERPROFILE\bin" + [Environment]::GetEnvironmentVariable("Path", "User"), "User")
$env:Path = "$env:USERPROFILE\bin;$env:Path"

# Install trdl.
mkdir -Force "$env:USERPROFILE\bin"
Invoke-WebRequest -Uri "https://tuf.trdl.dev/targets/releases/0.1.3/windows-arm64/bin/trdl.exe" -OutFile "$env:USERPROFILE\bin\trdl.exe"

Add werf repo:

trdl add werf https://tuf.werf.io 1 b7ff6bcbe598e072a86d595a3621924c8612c7e6dc6a82e919abe89707d7e3f468e616b5635630680dd1e98fc362ae5051728406700e6274c5ed1ad92bea52a2

To use werf locally in your terminal, we recommend to enable its automatic activation. To make werf available in all new PowerShell sessions, you need to execute this command (just once, run under Administrator):

# Allow execution of locally created scripts.
Set-ExecutionPolicy RemoteSigned -Scope CurrentUser

# Activate werf binary automatically during PowerShell initializations.
if (!(Test-Path "$profile")) {
  New-Item -Path "$profile" -Force
}
Add-Content -Path "$profile" -Value '. $(trdl use werf 1.2 beta)'

Now, if you log out and log in to the system again, werf will be always available. You can make sure of that by executing:

werf version

To get werf running in your current terminal only (before any logout/login is done), you can simply execute the . $(trdl use werf 1.2 beta) command.

In CI, you need a different approaching with activating werf explicitly in the beginning of each job/pipeline by executing:

. $(trdl use werf 1.2 beta)

Make sure you have Git 2.18.0 or newer and Docker installed.

Following instructions should be executed in the PowerShell.

Setup trdl which will manage werf installation and updates:

# Add %USERPROFILE%\bin to the PATH.
[Environment]::SetEnvironmentVariable("Path", "$env:USERPROFILE\bin" + [Environment]::GetEnvironmentVariable("Path", "User"), "User")
$env:Path = "$env:USERPROFILE\bin;$env:Path"

# Install trdl.
mkdir -Force "$env:USERPROFILE\bin"
Invoke-WebRequest -Uri "https://tuf.trdl.dev/targets/releases/0.1.3/windows-amd64/bin/trdl.exe" -OutFile "$env:USERPROFILE\bin\trdl.exe"

Add werf repo:

trdl add werf https://tuf.werf.io 1 b7ff6bcbe598e072a86d595a3621924c8612c7e6dc6a82e919abe89707d7e3f468e616b5635630680dd1e98fc362ae5051728406700e6274c5ed1ad92bea52a2

To use werf locally in your terminal, we recommend to enable its automatic activation. To make werf available in all new PowerShell sessions, you need to execute this command (just once, run under Administrator):

# Allow execution of locally created scripts.
Set-ExecutionPolicy RemoteSigned -Scope CurrentUser

# Activate werf binary automatically during PowerShell initializations.
if (!(Test-Path "$profile")) {
  New-Item -Path "$profile" -Force
}
Add-Content -Path "$profile" -Value '. $(trdl use werf 1.2 ea)'

Now, if you log out and log in to the system again, werf will be always available. You can make sure of that by executing:

werf version

To get werf running in your current terminal only (before any logout/login is done), you can simply execute the . $(trdl use werf 1.2 ea) command.

In CI, you need a different approaching with activating werf explicitly in the beginning of each job/pipeline by executing:

. $(trdl use werf 1.2 ea)

Make sure you have Git 2.18.0 or newer and Docker installed.

Following instructions should be executed in the PowerShell.

Setup trdl which will manage werf installation and updates:

# Add %USERPROFILE%\bin to the PATH.
[Environment]::SetEnvironmentVariable("Path", "$env:USERPROFILE\bin" + [Environment]::GetEnvironmentVariable("Path", "User"), "User")
$env:Path = "$env:USERPROFILE\bin;$env:Path"

# Install trdl.
mkdir -Force "$env:USERPROFILE\bin"
Invoke-WebRequest -Uri "https://tuf.trdl.dev/targets/releases/0.1.3/windows-arm64/bin/trdl.exe" -OutFile "$env:USERPROFILE\bin\trdl.exe"

Add werf repo:

trdl add werf https://tuf.werf.io 1 b7ff6bcbe598e072a86d595a3621924c8612c7e6dc6a82e919abe89707d7e3f468e616b5635630680dd1e98fc362ae5051728406700e6274c5ed1ad92bea52a2

To use werf locally in your terminal, we recommend to enable its automatic activation. To make werf available in all new PowerShell sessions, you need to execute this command (just once, run under Administrator):

# Allow execution of locally created scripts.
Set-ExecutionPolicy RemoteSigned -Scope CurrentUser

# Activate werf binary automatically during PowerShell initializations.
if (!(Test-Path "$profile")) {
  New-Item -Path "$profile" -Force
}
Add-Content -Path "$profile" -Value '. $(trdl use werf 1.2 ea)'

Now, if you log out and log in to the system again, werf will be always available. You can make sure of that by executing:

werf version

To get werf running in your current terminal only (before any logout/login is done), you can simply execute the . $(trdl use werf 1.2 ea) command.

In CI, you need a different approaching with activating werf explicitly in the beginning of each job/pipeline by executing:

. $(trdl use werf 1.2 ea)

Make sure you have Git 2.18.0 or newer and Docker installed.

Following instructions should be executed in the PowerShell.

Setup trdl which will manage werf installation and updates:

# Add %USERPROFILE%\bin to the PATH.
[Environment]::SetEnvironmentVariable("Path", "$env:USERPROFILE\bin" + [Environment]::GetEnvironmentVariable("Path", "User"), "User")
$env:Path = "$env:USERPROFILE\bin;$env:Path"

# Install trdl.
mkdir -Force "$env:USERPROFILE\bin"
Invoke-WebRequest -Uri "https://tuf.trdl.dev/targets/releases/0.1.3/windows-amd64/bin/trdl.exe" -OutFile "$env:USERPROFILE\bin\trdl.exe"

Add werf repo:

trdl add werf https://tuf.werf.io 1 b7ff6bcbe598e072a86d595a3621924c8612c7e6dc6a82e919abe89707d7e3f468e616b5635630680dd1e98fc362ae5051728406700e6274c5ed1ad92bea52a2

To use werf locally in your terminal, we recommend to enable its automatic activation. To make werf available in all new PowerShell sessions, you need to execute this command (just once, run under Administrator):

# Allow execution of locally created scripts.
Set-ExecutionPolicy RemoteSigned -Scope CurrentUser

# Activate werf binary automatically during PowerShell initializations.
if (!(Test-Path "$profile")) {
  New-Item -Path "$profile" -Force
}
Add-Content -Path "$profile" -Value '. $(trdl use werf 1.2 stable)'

Now, if you log out and log in to the system again, werf will be always available. You can make sure of that by executing:

werf version

To get werf running in your current terminal only (before any logout/login is done), you can simply execute the . $(trdl use werf 1.2 stable) command.

In CI, you need a different approaching with activating werf explicitly in the beginning of each job/pipeline by executing:

. $(trdl use werf 1.2 stable)

Make sure you have Git 2.18.0 or newer and Docker installed.

Following instructions should be executed in the PowerShell.

Setup trdl which will manage werf installation and updates:

# Add %USERPROFILE%\bin to the PATH.
[Environment]::SetEnvironmentVariable("Path", "$env:USERPROFILE\bin" + [Environment]::GetEnvironmentVariable("Path", "User"), "User")
$env:Path = "$env:USERPROFILE\bin;$env:Path"

# Install trdl.
mkdir -Force "$env:USERPROFILE\bin"
Invoke-WebRequest -Uri "https://tuf.trdl.dev/targets/releases/0.1.3/windows-arm64/bin/trdl.exe" -OutFile "$env:USERPROFILE\bin\trdl.exe"

Add werf repo:

trdl add werf https://tuf.werf.io 1 b7ff6bcbe598e072a86d595a3621924c8612c7e6dc6a82e919abe89707d7e3f468e616b5635630680dd1e98fc362ae5051728406700e6274c5ed1ad92bea52a2

To use werf locally in your terminal, we recommend to enable its automatic activation. To make werf available in all new PowerShell sessions, you need to execute this command (just once, run under Administrator):

# Allow execution of locally created scripts.
Set-ExecutionPolicy RemoteSigned -Scope CurrentUser

# Activate werf binary automatically during PowerShell initializations.
if (!(Test-Path "$profile")) {
  New-Item -Path "$profile" -Force
}
Add-Content -Path "$profile" -Value '. $(trdl use werf 1.2 stable)'

Now, if you log out and log in to the system again, werf will be always available. You can make sure of that by executing:

werf version

To get werf running in your current terminal only (before any logout/login is done), you can simply execute the . $(trdl use werf 1.2 stable) command.

In CI, you need a different approaching with activating werf explicitly in the beginning of each job/pipeline by executing:

. $(trdl use werf 1.2 stable)

Make sure you have Git 2.18.0 or newer and Docker installed.

Following instructions should be executed in the PowerShell.

Setup trdl which will manage werf installation and updates:

# Add %USERPROFILE%\bin to the PATH.
[Environment]::SetEnvironmentVariable("Path", "$env:USERPROFILE\bin" + [Environment]::GetEnvironmentVariable("Path", "User"), "User")
$env:Path = "$env:USERPROFILE\bin;$env:Path"

# Install trdl.
mkdir -Force "$env:USERPROFILE\bin"
Invoke-WebRequest -Uri "https://tuf.trdl.dev/targets/releases/0.1.3/windows-amd64/bin/trdl.exe" -OutFile "$env:USERPROFILE\bin\trdl.exe"

Add werf repo:

trdl add werf https://tuf.werf.io 1 b7ff6bcbe598e072a86d595a3621924c8612c7e6dc6a82e919abe89707d7e3f468e616b5635630680dd1e98fc362ae5051728406700e6274c5ed1ad92bea52a2

To use werf locally in your terminal, we recommend to enable its automatic activation. To make werf available in all new PowerShell sessions, you need to execute this command (just once, run under Administrator):

# Allow execution of locally created scripts.
Set-ExecutionPolicy RemoteSigned -Scope CurrentUser

# Activate werf binary automatically during PowerShell initializations.
if (!(Test-Path "$profile")) {
  New-Item -Path "$profile" -Force
}
Add-Content -Path "$profile" -Value '. $(trdl use werf 1.2 rock-solid)'

Now, if you log out and log in to the system again, werf will be always available. You can make sure of that by executing:

werf version

To get werf running in your current terminal only (before any logout/login is done), you can simply execute the . $(trdl use werf 1.2 rock-solid) command.

In CI, you need a different approaching with activating werf explicitly in the beginning of each job/pipeline by executing:

. $(trdl use werf 1.2 rock-solid)

Make sure you have Git 2.18.0 or newer and Docker installed.

Following instructions should be executed in the PowerShell.

Setup trdl which will manage werf installation and updates:

# Add %USERPROFILE%\bin to the PATH.
[Environment]::SetEnvironmentVariable("Path", "$env:USERPROFILE\bin" + [Environment]::GetEnvironmentVariable("Path", "User"), "User")
$env:Path = "$env:USERPROFILE\bin;$env:Path"

# Install trdl.
mkdir -Force "$env:USERPROFILE\bin"
Invoke-WebRequest -Uri "https://tuf.trdl.dev/targets/releases/0.1.3/windows-arm64/bin/trdl.exe" -OutFile "$env:USERPROFILE\bin\trdl.exe"

Add werf repo:

trdl add werf https://tuf.werf.io 1 b7ff6bcbe598e072a86d595a3621924c8612c7e6dc6a82e919abe89707d7e3f468e616b5635630680dd1e98fc362ae5051728406700e6274c5ed1ad92bea52a2

To use werf locally in your terminal, we recommend to enable its automatic activation. To make werf available in all new PowerShell sessions, you need to execute this command (just once, run under Administrator):

# Allow execution of locally created scripts.
Set-ExecutionPolicy RemoteSigned -Scope CurrentUser

# Activate werf binary automatically during PowerShell initializations.
if (!(Test-Path "$profile")) {
  New-Item -Path "$profile" -Force
}
Add-Content -Path "$profile" -Value '. $(trdl use werf 1.2 rock-solid)'

Now, if you log out and log in to the system again, werf will be always available. You can make sure of that by executing:

werf version

To get werf running in your current terminal only (before any logout/login is done), you can simply execute the . $(trdl use werf 1.2 rock-solid) command.

In CI, you need a different approaching with activating werf explicitly in the beginning of each job/pipeline by executing:

. $(trdl use werf 1.2 rock-solid)

Make sure you have Git 2.18.0 or newer and Docker installed.

Following instructions should be executed in the PowerShell.

Setup trdl which will manage werf installation and updates:

# Add %USERPROFILE%\bin to the PATH.
[Environment]::SetEnvironmentVariable("Path", "$env:USERPROFILE\bin" + [Environment]::GetEnvironmentVariable("Path", "User"), "User")
$env:Path = "$env:USERPROFILE\bin;$env:Path"

# Install trdl.
mkdir -Force "$env:USERPROFILE\bin"
Invoke-WebRequest -Uri "https://tuf.trdl.dev/targets/releases/0.1.3/windows-amd64/bin/trdl.exe" -OutFile "$env:USERPROFILE\bin\trdl.exe"

Add werf repo:

trdl add werf https://tuf.werf.io 1 b7ff6bcbe598e072a86d595a3621924c8612c7e6dc6a82e919abe89707d7e3f468e616b5635630680dd1e98fc362ae5051728406700e6274c5ed1ad92bea52a2

To use werf locally in your terminal, we recommend to enable its automatic activation. To make werf available in all new PowerShell sessions, you need to execute this command (just once, run under Administrator):

# Allow execution of locally created scripts.
Set-ExecutionPolicy RemoteSigned -Scope CurrentUser

# Activate werf binary automatically during PowerShell initializations.
if (!(Test-Path "$profile")) {
  New-Item -Path "$profile" -Force
}
Add-Content -Path "$profile" -Value '. $(trdl use werf 1.1 alpha)'

Now, if you log out and log in to the system again, werf will be always available. You can make sure of that by executing:

werf version

To get werf running in your current terminal only (before any logout/login is done), you can simply execute the . $(trdl use werf 1.1 alpha) command.

In CI, you need a different approaching with activating werf explicitly in the beginning of each job/pipeline by executing:

. $(trdl use werf 1.1 alpha)

Make sure you have Git 2.18.0 or newer and Docker installed.

Following instructions should be executed in the PowerShell.

Setup trdl which will manage werf installation and updates:

# Add %USERPROFILE%\bin to the PATH.
[Environment]::SetEnvironmentVariable("Path", "$env:USERPROFILE\bin" + [Environment]::GetEnvironmentVariable("Path", "User"), "User")
$env:Path = "$env:USERPROFILE\bin;$env:Path"

# Install trdl.
mkdir -Force "$env:USERPROFILE\bin"
Invoke-WebRequest -Uri "https://tuf.trdl.dev/targets/releases/0.1.3/windows-arm64/bin/trdl.exe" -OutFile "$env:USERPROFILE\bin\trdl.exe"

Add werf repo:

trdl add werf https://tuf.werf.io 1 b7ff6bcbe598e072a86d595a3621924c8612c7e6dc6a82e919abe89707d7e3f468e616b5635630680dd1e98fc362ae5051728406700e6274c5ed1ad92bea52a2

To use werf locally in your terminal, we recommend to enable its automatic activation. To make werf available in all new PowerShell sessions, you need to execute this command (just once, run under Administrator):

# Allow execution of locally created scripts.
Set-ExecutionPolicy RemoteSigned -Scope CurrentUser

# Activate werf binary automatically during PowerShell initializations.
if (!(Test-Path "$profile")) {
  New-Item -Path "$profile" -Force
}
Add-Content -Path "$profile" -Value '. $(trdl use werf 1.1 alpha)'

Now, if you log out and log in to the system again, werf will be always available. You can make sure of that by executing:

werf version

To get werf running in your current terminal only (before any logout/login is done), you can simply execute the . $(trdl use werf 1.1 alpha) command.

In CI, you need a different approaching with activating werf explicitly in the beginning of each job/pipeline by executing:

. $(trdl use werf 1.1 alpha)

Make sure you have Git 2.18.0 or newer and Docker installed.

Following instructions should be executed in the PowerShell.

Setup trdl which will manage werf installation and updates:

# Add %USERPROFILE%\bin to the PATH.
[Environment]::SetEnvironmentVariable("Path", "$env:USERPROFILE\bin" + [Environment]::GetEnvironmentVariable("Path", "User"), "User")
$env:Path = "$env:USERPROFILE\bin;$env:Path"

# Install trdl.
mkdir -Force "$env:USERPROFILE\bin"
Invoke-WebRequest -Uri "https://tuf.trdl.dev/targets/releases/0.1.3/windows-amd64/bin/trdl.exe" -OutFile "$env:USERPROFILE\bin\trdl.exe"

Add werf repo:

trdl add werf https://tuf.werf.io 1 b7ff6bcbe598e072a86d595a3621924c8612c7e6dc6a82e919abe89707d7e3f468e616b5635630680dd1e98fc362ae5051728406700e6274c5ed1ad92bea52a2

To use werf locally in your terminal, we recommend to enable its automatic activation. To make werf available in all new PowerShell sessions, you need to execute this command (just once, run under Administrator):

# Allow execution of locally created scripts.
Set-ExecutionPolicy RemoteSigned -Scope CurrentUser

# Activate werf binary automatically during PowerShell initializations.
if (!(Test-Path "$profile")) {
  New-Item -Path "$profile" -Force
}
Add-Content -Path "$profile" -Value '. $(trdl use werf 1.1 beta)'

Now, if you log out and log in to the system again, werf will be always available. You can make sure of that by executing:

werf version

To get werf running in your current terminal only (before any logout/login is done), you can simply execute the . $(trdl use werf 1.1 beta) command.

In CI, you need a different approaching with activating werf explicitly in the beginning of each job/pipeline by executing:

. $(trdl use werf 1.1 beta)

Make sure you have Git 2.18.0 or newer and Docker installed.

Following instructions should be executed in the PowerShell.

Setup trdl which will manage werf installation and updates:

# Add %USERPROFILE%\bin to the PATH.
[Environment]::SetEnvironmentVariable("Path", "$env:USERPROFILE\bin" + [Environment]::GetEnvironmentVariable("Path", "User"), "User")
$env:Path = "$env:USERPROFILE\bin;$env:Path"

# Install trdl.
mkdir -Force "$env:USERPROFILE\bin"
Invoke-WebRequest -Uri "https://tuf.trdl.dev/targets/releases/0.1.3/windows-arm64/bin/trdl.exe" -OutFile "$env:USERPROFILE\bin\trdl.exe"

Add werf repo:

trdl add werf https://tuf.werf.io 1 b7ff6bcbe598e072a86d595a3621924c8612c7e6dc6a82e919abe89707d7e3f468e616b5635630680dd1e98fc362ae5051728406700e6274c5ed1ad92bea52a2

To use werf locally in your terminal, we recommend to enable its automatic activation. To make werf available in all new PowerShell sessions, you need to execute this command (just once, run under Administrator):

# Allow execution of locally created scripts.
Set-ExecutionPolicy RemoteSigned -Scope CurrentUser

# Activate werf binary automatically during PowerShell initializations.
if (!(Test-Path "$profile")) {
  New-Item -Path "$profile" -Force
}
Add-Content -Path "$profile" -Value '. $(trdl use werf 1.1 beta)'

Now, if you log out and log in to the system again, werf will be always available. You can make sure of that by executing:

werf version

To get werf running in your current terminal only (before any logout/login is done), you can simply execute the . $(trdl use werf 1.1 beta) command.

In CI, you need a different approaching with activating werf explicitly in the beginning of each job/pipeline by executing:

. $(trdl use werf 1.1 beta)

Make sure you have Git 2.18.0 or newer and Docker installed.

Following instructions should be executed in the PowerShell.

Setup trdl which will manage werf installation and updates:

# Add %USERPROFILE%\bin to the PATH.
[Environment]::SetEnvironmentVariable("Path", "$env:USERPROFILE\bin" + [Environment]::GetEnvironmentVariable("Path", "User"), "User")
$env:Path = "$env:USERPROFILE\bin;$env:Path"

# Install trdl.
mkdir -Force "$env:USERPROFILE\bin"
Invoke-WebRequest -Uri "https://tuf.trdl.dev/targets/releases/0.1.3/windows-amd64/bin/trdl.exe" -OutFile "$env:USERPROFILE\bin\trdl.exe"

Add werf repo:

trdl add werf https://tuf.werf.io 1 b7ff6bcbe598e072a86d595a3621924c8612c7e6dc6a82e919abe89707d7e3f468e616b5635630680dd1e98fc362ae5051728406700e6274c5ed1ad92bea52a2

To use werf locally in your terminal, we recommend to enable its automatic activation. To make werf available in all new PowerShell sessions, you need to execute this command (just once, run under Administrator):

# Allow execution of locally created scripts.
Set-ExecutionPolicy RemoteSigned -Scope CurrentUser

# Activate werf binary automatically during PowerShell initializations.
if (!(Test-Path "$profile")) {
  New-Item -Path "$profile" -Force
}
Add-Content -Path "$profile" -Value '. $(trdl use werf 1.1 ea)'

Now, if you log out and log in to the system again, werf will be always available. You can make sure of that by executing:

werf version

To get werf running in your current terminal only (before any logout/login is done), you can simply execute the . $(trdl use werf 1.1 ea) command.

In CI, you need a different approaching with activating werf explicitly in the beginning of each job/pipeline by executing:

. $(trdl use werf 1.1 ea)

Make sure you have Git 2.18.0 or newer and Docker installed.

Following instructions should be executed in the PowerShell.

Setup trdl which will manage werf installation and updates:

# Add %USERPROFILE%\bin to the PATH.
[Environment]::SetEnvironmentVariable("Path", "$env:USERPROFILE\bin" + [Environment]::GetEnvironmentVariable("Path", "User"), "User")
$env:Path = "$env:USERPROFILE\bin;$env:Path"

# Install trdl.
mkdir -Force "$env:USERPROFILE\bin"
Invoke-WebRequest -Uri "https://tuf.trdl.dev/targets/releases/0.1.3/windows-arm64/bin/trdl.exe" -OutFile "$env:USERPROFILE\bin\trdl.exe"

Add werf repo:

trdl add werf https://tuf.werf.io 1 b7ff6bcbe598e072a86d595a3621924c8612c7e6dc6a82e919abe89707d7e3f468e616b5635630680dd1e98fc362ae5051728406700e6274c5ed1ad92bea52a2

To use werf locally in your terminal, we recommend to enable its automatic activation. To make werf available in all new PowerShell sessions, you need to execute this command (just once, run under Administrator):

# Allow execution of locally created scripts.
Set-ExecutionPolicy RemoteSigned -Scope CurrentUser

# Activate werf binary automatically during PowerShell initializations.
if (!(Test-Path "$profile")) {
  New-Item -Path "$profile" -Force
}
Add-Content -Path "$profile" -Value '. $(trdl use werf 1.1 ea)'

Now, if you log out and log in to the system again, werf will be always available. You can make sure of that by executing:

werf version

To get werf running in your current terminal only (before any logout/login is done), you can simply execute the . $(trdl use werf 1.1 ea) command.

In CI, you need a different approaching with activating werf explicitly in the beginning of each job/pipeline by executing:

. $(trdl use werf 1.1 ea)

Make sure you have Git 2.18.0 or newer and Docker installed.

Following instructions should be executed in the PowerShell.

Setup trdl which will manage werf installation and updates:

# Add %USERPROFILE%\bin to the PATH.
[Environment]::SetEnvironmentVariable("Path", "$env:USERPROFILE\bin" + [Environment]::GetEnvironmentVariable("Path", "User"), "User")
$env:Path = "$env:USERPROFILE\bin;$env:Path"

# Install trdl.
mkdir -Force "$env:USERPROFILE\bin"
Invoke-WebRequest -Uri "https://tuf.trdl.dev/targets/releases/0.1.3/windows-amd64/bin/trdl.exe" -OutFile "$env:USERPROFILE\bin\trdl.exe"

Add werf repo:

trdl add werf https://tuf.werf.io 1 b7ff6bcbe598e072a86d595a3621924c8612c7e6dc6a82e919abe89707d7e3f468e616b5635630680dd1e98fc362ae5051728406700e6274c5ed1ad92bea52a2

To use werf locally in your terminal, we recommend to enable its automatic activation. To make werf available in all new PowerShell sessions, you need to execute this command (just once, run under Administrator):

# Allow execution of locally created scripts.
Set-ExecutionPolicy RemoteSigned -Scope CurrentUser

# Activate werf binary automatically during PowerShell initializations.
if (!(Test-Path "$profile")) {
  New-Item -Path "$profile" -Force
}
Add-Content -Path "$profile" -Value '. $(trdl use werf 1.1 stable)'

Now, if you log out and log in to the system again, werf will be always available. You can make sure of that by executing:

werf version

To get werf running in your current terminal only (before any logout/login is done), you can simply execute the . $(trdl use werf 1.1 stable) command.

In CI, you need a different approaching with activating werf explicitly in the beginning of each job/pipeline by executing:

. $(trdl use werf 1.1 stable)

Make sure you have Git 2.18.0 or newer and Docker installed.

Following instructions should be executed in the PowerShell.

Setup trdl which will manage werf installation and updates:

# Add %USERPROFILE%\bin to the PATH.
[Environment]::SetEnvironmentVariable("Path", "$env:USERPROFILE\bin" + [Environment]::GetEnvironmentVariable("Path", "User"), "User")
$env:Path = "$env:USERPROFILE\bin;$env:Path"

# Install trdl.
mkdir -Force "$env:USERPROFILE\bin"
Invoke-WebRequest -Uri "https://tuf.trdl.dev/targets/releases/0.1.3/windows-arm64/bin/trdl.exe" -OutFile "$env:USERPROFILE\bin\trdl.exe"

Add werf repo:

trdl add werf https://tuf.werf.io 1 b7ff6bcbe598e072a86d595a3621924c8612c7e6dc6a82e919abe89707d7e3f468e616b5635630680dd1e98fc362ae5051728406700e6274c5ed1ad92bea52a2

To use werf locally in your terminal, we recommend to enable its automatic activation. To make werf available in all new PowerShell sessions, you need to execute this command (just once, run under Administrator):

# Allow execution of locally created scripts.
Set-ExecutionPolicy RemoteSigned -Scope CurrentUser

# Activate werf binary automatically during PowerShell initializations.
if (!(Test-Path "$profile")) {
  New-Item -Path "$profile" -Force
}
Add-Content -Path "$profile" -Value '. $(trdl use werf 1.1 stable)'

Now, if you log out and log in to the system again, werf will be always available. You can make sure of that by executing:

werf version

To get werf running in your current terminal only (before any logout/login is done), you can simply execute the . $(trdl use werf 1.1 stable) command.

In CI, you need a different approaching with activating werf explicitly in the beginning of each job/pipeline by executing:

. $(trdl use werf 1.1 stable)

Make sure you have Git 2.18.0 or newer and Docker installed.

Following instructions should be executed in the PowerShell.

Setup trdl which will manage werf installation and updates:

# Add %USERPROFILE%\bin to the PATH.
[Environment]::SetEnvironmentVariable("Path", "$env:USERPROFILE\bin" + [Environment]::GetEnvironmentVariable("Path", "User"), "User")
$env:Path = "$env:USERPROFILE\bin;$env:Path"

# Install trdl.
mkdir -Force "$env:USERPROFILE\bin"
Invoke-WebRequest -Uri "https://tuf.trdl.dev/targets/releases/0.1.3/windows-amd64/bin/trdl.exe" -OutFile "$env:USERPROFILE\bin\trdl.exe"

Add werf repo:

trdl add werf https://tuf.werf.io 1 b7ff6bcbe598e072a86d595a3621924c8612c7e6dc6a82e919abe89707d7e3f468e616b5635630680dd1e98fc362ae5051728406700e6274c5ed1ad92bea52a2

To use werf locally in your terminal, we recommend to enable its automatic activation. To make werf available in all new PowerShell sessions, you need to execute this command (just once, run under Administrator):

# Allow execution of locally created scripts.
Set-ExecutionPolicy RemoteSigned -Scope CurrentUser

# Activate werf binary automatically during PowerShell initializations.
if (!(Test-Path "$profile")) {
  New-Item -Path "$profile" -Force
}
Add-Content -Path "$profile" -Value '. $(trdl use werf 1.1 rock-solid)'

Now, if you log out and log in to the system again, werf will be always available. You can make sure of that by executing:

werf version

To get werf running in your current terminal only (before any logout/login is done), you can simply execute the . $(trdl use werf 1.1 rock-solid) command.

In CI, you need a different approaching with activating werf explicitly in the beginning of each job/pipeline by executing:

. $(trdl use werf 1.1 rock-solid)

Make sure you have Git 2.18.0 or newer and Docker installed.

Following instructions should be executed in the PowerShell.

Setup trdl which will manage werf installation and updates:

# Add %USERPROFILE%\bin to the PATH.
[Environment]::SetEnvironmentVariable("Path", "$env:USERPROFILE\bin" + [Environment]::GetEnvironmentVariable("Path", "User"), "User")
$env:Path = "$env:USERPROFILE\bin;$env:Path"

# Install trdl.
mkdir -Force "$env:USERPROFILE\bin"
Invoke-WebRequest -Uri "https://tuf.trdl.dev/targets/releases/0.1.3/windows-arm64/bin/trdl.exe" -OutFile "$env:USERPROFILE\bin\trdl.exe"

Add werf repo:

trdl add werf https://tuf.werf.io 1 b7ff6bcbe598e072a86d595a3621924c8612c7e6dc6a82e919abe89707d7e3f468e616b5635630680dd1e98fc362ae5051728406700e6274c5ed1ad92bea52a2

To use werf locally in your terminal, we recommend to enable its automatic activation. To make werf available in all new PowerShell sessions, you need to execute this command (just once, run under Administrator):

# Allow execution of locally created scripts.
Set-ExecutionPolicy RemoteSigned -Scope CurrentUser

# Activate werf binary automatically during PowerShell initializations.
if (!(Test-Path "$profile")) {
  New-Item -Path "$profile" -Force
}
Add-Content -Path "$profile" -Value '. $(trdl use werf 1.1 rock-solid)'

Now, if you log out and log in to the system again, werf will be always available. You can make sure of that by executing:

werf version

To get werf running in your current terminal only (before any logout/login is done), you can simply execute the . $(trdl use werf 1.1 rock-solid) command.

In CI, you need a different approaching with activating werf explicitly in the beginning of each job/pipeline by executing:

. $(trdl use werf 1.1 rock-solid)

Make sure you have Git 2.18.0 or newer and Docker installed.

Execute in shell:

curl -L "https://tuf.werf.io/targets/releases/1.2.36/linux-amd64/bin/werf" -o /tmp/werf
sudo install /tmp/werf /usr/local/bin/werf

Make sure you have Git 2.18.0 or newer and Docker installed.

Execute in shell:

curl -L "https://tuf.werf.io/targets/releases/1.2.36/linux-arm64/bin/werf" -o /tmp/werf
sudo install /tmp/werf /usr/local/bin/werf

Make sure you have Git 2.18.0 or newer and Docker installed.

Execute in shell:

curl -L "https://tuf.werf.io/targets/releases/1.2.36/linux-amd64/bin/werf" -o /tmp/werf
sudo install /tmp/werf /usr/local/bin/werf

Make sure you have Git 2.18.0 or newer and Docker installed.

Execute in shell:

curl -L "https://tuf.werf.io/targets/releases/1.2.36/linux-arm64/bin/werf" -o /tmp/werf
sudo install /tmp/werf /usr/local/bin/werf

Make sure you have Git 2.18.0 or newer and Docker installed.

Execute in shell:

curl -L "https://tuf.werf.io/targets/releases/1.2.36/linux-amd64/bin/werf" -o /tmp/werf
sudo install /tmp/werf /usr/local/bin/werf

Make sure you have Git 2.18.0 or newer and Docker installed.

Execute in shell:

curl -L "https://tuf.werf.io/targets/releases/1.2.36/linux-arm64/bin/werf" -o /tmp/werf
sudo install /tmp/werf /usr/local/bin/werf

Make sure you have Git 2.18.0 or newer and Docker installed.

Execute in shell:

curl -L "https://tuf.werf.io/targets/releases//linux-amd64/bin/werf" -o /tmp/werf
sudo install /tmp/werf /usr/local/bin/werf

Make sure you have Git 2.18.0 or newer and Docker installed.

Execute in shell:

curl -L "https://tuf.werf.io/targets/releases//linux-arm64/bin/werf" -o /tmp/werf
sudo install /tmp/werf /usr/local/bin/werf

Make sure you have Git 2.18.0 or newer and Docker installed.

Execute in shell:

curl -L "https://tuf.werf.io/targets/releases//linux-amd64/bin/werf" -o /tmp/werf
sudo install /tmp/werf /usr/local/bin/werf

Make sure you have Git 2.18.0 or newer and Docker installed.

Execute in shell:

curl -L "https://tuf.werf.io/targets/releases//linux-arm64/bin/werf" -o /tmp/werf
sudo install /tmp/werf /usr/local/bin/werf

Make sure you have Git 2.18.0 or newer and Docker installed.

Execute in shell:

curl -L "https://tuf.werf.io/targets/releases/1.1.23+fix50/linux-amd64/bin/werf" -o /tmp/werf
sudo install /tmp/werf /usr/local/bin/werf

Make sure you have Git 2.18.0 or newer and Docker installed.

Execute in shell:

curl -L "https://tuf.werf.io/targets/releases/1.1.23+fix50/linux-arm64/bin/werf" -o /tmp/werf
sudo install /tmp/werf /usr/local/bin/werf

Make sure you have Git 2.18.0 or newer and Docker installed.

Execute in shell:

curl -L "https://tuf.werf.io/targets/releases/1.1.23+fix50/linux-amd64/bin/werf" -o /tmp/werf
sudo install /tmp/werf /usr/local/bin/werf

Make sure you have Git 2.18.0 or newer and Docker installed.

Execute in shell:

curl -L "https://tuf.werf.io/targets/releases/1.1.23+fix50/linux-arm64/bin/werf" -o /tmp/werf
sudo install /tmp/werf /usr/local/bin/werf

Make sure you have Git 2.18.0 or newer and Docker installed.

Execute in shell:

curl -L "https://tuf.werf.io/targets/releases/1.1.23+fix50/linux-amd64/bin/werf" -o /tmp/werf
sudo install /tmp/werf /usr/local/bin/werf

Make sure you have Git 2.18.0 or newer and Docker installed.

Execute in shell:

curl -L "https://tuf.werf.io/targets/releases/1.1.23+fix50/linux-arm64/bin/werf" -o /tmp/werf
sudo install /tmp/werf /usr/local/bin/werf

Make sure you have Git 2.18.0 or newer and Docker installed.

Execute in shell:

curl -L "https://tuf.werf.io/targets/releases/1.1.23+fix50/linux-amd64/bin/werf" -o /tmp/werf
sudo install /tmp/werf /usr/local/bin/werf

Make sure you have Git 2.18.0 or newer and Docker installed.

Execute in shell:

curl -L "https://tuf.werf.io/targets/releases/1.1.23+fix50/linux-arm64/bin/werf" -o /tmp/werf
sudo install /tmp/werf /usr/local/bin/werf

Make sure you have Git 2.18.0 or newer and Docker installed.

Execute in shell:

curl -L "https://tuf.werf.io/targets/releases/1.1.23+fix50/linux-amd64/bin/werf" -o /tmp/werf
sudo install /tmp/werf /usr/local/bin/werf

Make sure you have Git 2.18.0 or newer and Docker installed.

Execute in shell:

curl -L "https://tuf.werf.io/targets/releases/1.1.23+fix50/linux-arm64/bin/werf" -o /tmp/werf
sudo install /tmp/werf /usr/local/bin/werf

Make sure you have Git 2.18.0 or newer and Docker installed.

Execute in shell:

curl -L "https://tuf.werf.io/targets/releases/1.2.36/darwin-amd64/bin/werf" -o /tmp/werf
sudo install /tmp/werf /usr/local/bin/werf

Make sure you have Git 2.18.0 or newer and Docker installed.

Execute in shell:

curl -L "https://tuf.werf.io/targets/releases/1.2.36/darwin-arm64/bin/werf" -o /tmp/werf
sudo install /tmp/werf /usr/local/bin/werf

Make sure you have Git 2.18.0 or newer and Docker installed.

Execute in shell:

curl -L "https://tuf.werf.io/targets/releases/1.2.36/darwin-amd64/bin/werf" -o /tmp/werf
sudo install /tmp/werf /usr/local/bin/werf

Make sure you have Git 2.18.0 or newer and Docker installed.

Execute in shell:

curl -L "https://tuf.werf.io/targets/releases/1.2.36/darwin-arm64/bin/werf" -o /tmp/werf
sudo install /tmp/werf /usr/local/bin/werf

Make sure you have Git 2.18.0 or newer and Docker installed.

Execute in shell:

curl -L "https://tuf.werf.io/targets/releases/1.2.36/darwin-amd64/bin/werf" -o /tmp/werf
sudo install /tmp/werf /usr/local/bin/werf

Make sure you have Git 2.18.0 or newer and Docker installed.

Execute in shell:

curl -L "https://tuf.werf.io/targets/releases/1.2.36/darwin-arm64/bin/werf" -o /tmp/werf
sudo install /tmp/werf /usr/local/bin/werf

Make sure you have Git 2.18.0 or newer and Docker installed.

Execute in shell:

curl -L "https://tuf.werf.io/targets/releases//darwin-amd64/bin/werf" -o /tmp/werf
sudo install /tmp/werf /usr/local/bin/werf

Make sure you have Git 2.18.0 or newer and Docker installed.

Execute in shell:

curl -L "https://tuf.werf.io/targets/releases//darwin-arm64/bin/werf" -o /tmp/werf
sudo install /tmp/werf /usr/local/bin/werf

Make sure you have Git 2.18.0 or newer and Docker installed.

Execute in shell:

curl -L "https://tuf.werf.io/targets/releases//darwin-amd64/bin/werf" -o /tmp/werf
sudo install /tmp/werf /usr/local/bin/werf

Make sure you have Git 2.18.0 or newer and Docker installed.

Execute in shell:

curl -L "https://tuf.werf.io/targets/releases//darwin-arm64/bin/werf" -o /tmp/werf
sudo install /tmp/werf /usr/local/bin/werf

Make sure you have Git 2.18.0 or newer and Docker installed.

Execute in shell:

curl -L "https://tuf.werf.io/targets/releases/1.1.23+fix50/darwin-amd64/bin/werf" -o /tmp/werf
sudo install /tmp/werf /usr/local/bin/werf

Make sure you have Git 2.18.0 or newer and Docker installed.

Execute in shell:

curl -L "https://tuf.werf.io/targets/releases/1.1.23+fix50/darwin-arm64/bin/werf" -o /tmp/werf
sudo install /tmp/werf /usr/local/bin/werf

Make sure you have Git 2.18.0 or newer and Docker installed.

Execute in shell:

curl -L "https://tuf.werf.io/targets/releases/1.1.23+fix50/darwin-amd64/bin/werf" -o /tmp/werf
sudo install /tmp/werf /usr/local/bin/werf

Make sure you have Git 2.18.0 or newer and Docker installed.

Execute in shell:

curl -L "https://tuf.werf.io/targets/releases/1.1.23+fix50/darwin-arm64/bin/werf" -o /tmp/werf
sudo install /tmp/werf /usr/local/bin/werf

Make sure you have Git 2.18.0 or newer and Docker installed.

Execute in shell:

curl -L "https://tuf.werf.io/targets/releases/1.1.23+fix50/darwin-amd64/bin/werf" -o /tmp/werf
sudo install /tmp/werf /usr/local/bin/werf

Make sure you have Git 2.18.0 or newer and Docker installed.

Execute in shell:

curl -L "https://tuf.werf.io/targets/releases/1.1.23+fix50/darwin-arm64/bin/werf" -o /tmp/werf
sudo install /tmp/werf /usr/local/bin/werf

Make sure you have Git 2.18.0 or newer and Docker installed.

Execute in shell:

curl -L "https://tuf.werf.io/targets/releases/1.1.23+fix50/darwin-amd64/bin/werf" -o /tmp/werf
sudo install /tmp/werf /usr/local/bin/werf

Make sure you have Git 2.18.0 or newer and Docker installed.

Execute in shell:

curl -L "https://tuf.werf.io/targets/releases/1.1.23+fix50/darwin-arm64/bin/werf" -o /tmp/werf
sudo install /tmp/werf /usr/local/bin/werf

Make sure you have Git 2.18.0 or newer and Docker installed.

Execute in shell:

curl -L "https://tuf.werf.io/targets/releases/1.1.23+fix50/darwin-amd64/bin/werf" -o /tmp/werf
sudo install /tmp/werf /usr/local/bin/werf

Make sure you have Git 2.18.0 or newer and Docker installed.

Execute in shell:

curl -L "https://tuf.werf.io/targets/releases/1.1.23+fix50/darwin-arm64/bin/werf" -o /tmp/werf
sudo install /tmp/werf /usr/local/bin/werf

Make sure you have Git 2.18.0 or newer and Docker installed.

Execute in PowerShell:

# Add %USERPROFILE%\bin to the PATH.
[Environment]::SetEnvironmentVariable("Path", "$env:USERPROFILE\bin" + [Environment]::GetEnvironmentVariable("Path", "User"), "User")
$env:Path = "$env:USERPROFILE\bin;$env:Path"

# Install werf.
mkdir -Force "$env:USERPROFILE\bin"
Invoke-WebRequest -Uri "https://tuf.werf.io/targets/releases/1.2.36/windows-amd64/bin/werf.exe" -OutFile "$env:USERPROFILE\bin\werf.exe"

Make sure you have Git 2.18.0 or newer and Docker installed.

Execute in PowerShell:

# Add %USERPROFILE%\bin to the PATH.
[Environment]::SetEnvironmentVariable("Path", "$env:USERPROFILE\bin" + [Environment]::GetEnvironmentVariable("Path", "User"), "User")
$env:Path = "$env:USERPROFILE\bin;$env:Path"

# Install werf.
mkdir -Force "$env:USERPROFILE\bin"
Invoke-WebRequest -Uri "https://tuf.werf.io/targets/releases/1.2.36/windows-arm64/bin/werf.exe" -OutFile "$env:USERPROFILE\bin\werf.exe"

Make sure you have Git 2.18.0 or newer and Docker installed.

Execute in PowerShell:

# Add %USERPROFILE%\bin to the PATH.
[Environment]::SetEnvironmentVariable("Path", "$env:USERPROFILE\bin" + [Environment]::GetEnvironmentVariable("Path", "User"), "User")
$env:Path = "$env:USERPROFILE\bin;$env:Path"

# Install werf.
mkdir -Force "$env:USERPROFILE\bin"
Invoke-WebRequest -Uri "https://tuf.werf.io/targets/releases/1.2.36/windows-amd64/bin/werf.exe" -OutFile "$env:USERPROFILE\bin\werf.exe"

Make sure you have Git 2.18.0 or newer and Docker installed.

Execute in PowerShell:

# Add %USERPROFILE%\bin to the PATH.
[Environment]::SetEnvironmentVariable("Path", "$env:USERPROFILE\bin" + [Environment]::GetEnvironmentVariable("Path", "User"), "User")
$env:Path = "$env:USERPROFILE\bin;$env:Path"

# Install werf.
mkdir -Force "$env:USERPROFILE\bin"
Invoke-WebRequest -Uri "https://tuf.werf.io/targets/releases/1.2.36/windows-arm64/bin/werf.exe" -OutFile "$env:USERPROFILE\bin\werf.exe"

Make sure you have Git 2.18.0 or newer and Docker installed.

Execute in PowerShell:

# Add %USERPROFILE%\bin to the PATH.
[Environment]::SetEnvironmentVariable("Path", "$env:USERPROFILE\bin" + [Environment]::GetEnvironmentVariable("Path", "User"), "User")
$env:Path = "$env:USERPROFILE\bin;$env:Path"

# Install werf.
mkdir -Force "$env:USERPROFILE\bin"
Invoke-WebRequest -Uri "https://tuf.werf.io/targets/releases/1.2.36/windows-amd64/bin/werf.exe" -OutFile "$env:USERPROFILE\bin\werf.exe"

Make sure you have Git 2.18.0 or newer and Docker installed.

Execute in PowerShell:

# Add %USERPROFILE%\bin to the PATH.
[Environment]::SetEnvironmentVariable("Path", "$env:USERPROFILE\bin" + [Environment]::GetEnvironmentVariable("Path", "User"), "User")
$env:Path = "$env:USERPROFILE\bin;$env:Path"

# Install werf.
mkdir -Force "$env:USERPROFILE\bin"
Invoke-WebRequest -Uri "https://tuf.werf.io/targets/releases/1.2.36/windows-arm64/bin/werf.exe" -OutFile "$env:USERPROFILE\bin\werf.exe"

Make sure you have Git 2.18.0 or newer and Docker installed.

Execute in PowerShell:

# Add %USERPROFILE%\bin to the PATH.
[Environment]::SetEnvironmentVariable("Path", "$env:USERPROFILE\bin" + [Environment]::GetEnvironmentVariable("Path", "User"), "User")
$env:Path = "$env:USERPROFILE\bin;$env:Path"

# Install werf.
mkdir -Force "$env:USERPROFILE\bin"
Invoke-WebRequest -Uri "https://tuf.werf.io/targets/releases//windows-amd64/bin/werf.exe" -OutFile "$env:USERPROFILE\bin\werf.exe"

Make sure you have Git 2.18.0 or newer and Docker installed.

Execute in PowerShell:

# Add %USERPROFILE%\bin to the PATH.
[Environment]::SetEnvironmentVariable("Path", "$env:USERPROFILE\bin" + [Environment]::GetEnvironmentVariable("Path", "User"), "User")
$env:Path = "$env:USERPROFILE\bin;$env:Path"

# Install werf.
mkdir -Force "$env:USERPROFILE\bin"
Invoke-WebRequest -Uri "https://tuf.werf.io/targets/releases//windows-arm64/bin/werf.exe" -OutFile "$env:USERPROFILE\bin\werf.exe"

Make sure you have Git 2.18.0 or newer and Docker installed.

Execute in PowerShell:

# Add %USERPROFILE%\bin to the PATH.
[Environment]::SetEnvironmentVariable("Path", "$env:USERPROFILE\bin" + [Environment]::GetEnvironmentVariable("Path", "User"), "User")
$env:Path = "$env:USERPROFILE\bin;$env:Path"

# Install werf.
mkdir -Force "$env:USERPROFILE\bin"
Invoke-WebRequest -Uri "https://tuf.werf.io/targets/releases//windows-amd64/bin/werf.exe" -OutFile "$env:USERPROFILE\bin\werf.exe"

Make sure you have Git 2.18.0 or newer and Docker installed.

Execute in PowerShell:

# Add %USERPROFILE%\bin to the PATH.
[Environment]::SetEnvironmentVariable("Path", "$env:USERPROFILE\bin" + [Environment]::GetEnvironmentVariable("Path", "User"), "User")
$env:Path = "$env:USERPROFILE\bin;$env:Path"

# Install werf.
mkdir -Force "$env:USERPROFILE\bin"
Invoke-WebRequest -Uri "https://tuf.werf.io/targets/releases//windows-arm64/bin/werf.exe" -OutFile "$env:USERPROFILE\bin\werf.exe"

Make sure you have Git 2.18.0 or newer and Docker installed.

Execute in PowerShell:

# Add %USERPROFILE%\bin to the PATH.
[Environment]::SetEnvironmentVariable("Path", "$env:USERPROFILE\bin" + [Environment]::GetEnvironmentVariable("Path", "User"), "User")
$env:Path = "$env:USERPROFILE\bin;$env:Path"

# Install werf.
mkdir -Force "$env:USERPROFILE\bin"
Invoke-WebRequest -Uri "https://tuf.werf.io/targets/releases/1.1.23+fix50/windows-amd64/bin/werf.exe" -OutFile "$env:USERPROFILE\bin\werf.exe"