AT FIELD CICD Dashboard
You have been logged out.
A deployment machine is the server where AT Field CI/CD will run your deployment commands.
Go to:
Machines → Add Machine
Enter:
| Field | Example |
|---|---|
| Name | Production |
| Host | 192.168.1.50 |
| Port | 22 |
| Username | deploy |
The server must have SSH enabled and the selected user must be able to log in through SSH.
If AT Field CI/CD is running on your home server with Docker, you can add that same server as a deployment machine.
Use:
| Field | Value |
|---|---|
| Name | Home Docker Host |
| Host | host.docker.internal |
| Port | 22 |
| Username | Your Linux username |
host.docker.internal is already configured in the Docker Compose setup and points from the AT Field container to the Docker host.
After adding it, AT Field can run commands directly on your Docker host, such as:
docker compose pull docker compose up -d
Make sure the SSH user has permission to run Docker commands.
AT Field CI/CD uses SSH keys to connect to your deployment machines.
You need two files:
Run this on your computer:
ssh-keygen -t ed25519 -f ~/.ssh/at-field-deploy
When asked for a passphrase, you can leave it empty by pressing Enter.
This creates:
~/.ssh/at-field-deploy ← Private key ~/.ssh/at-field-deploy.pub ← Public key
Copy the contents of:
cat ~/.ssh/at-field-deploy.pub
Then add that entire line to the deployment user's:
~/.ssh/authorized_keys
on the target server.
For example:
ssh-copy-id -i ~/.ssh/at-field-deploy.pub user@your-server
Before adding it to AT Field CI/CD, verify that it works:
ssh -i ~/.ssh/at-field-deploy user@your-server
If you can connect without entering a password, the key is ready.
Open:
Machines → Add Machine
Enter:
22~/.ssh/at-field-deployNever upload at-field-deploy.pub as the private key.
The .pub file belongs on the server. The file without .pub is the private key used by AT Field CI/CD.
Keep the private key secret. Anyone who obtains it may be able to access your deployment server.
Copy into your git host webhook settings.
Are you sure?