Skip to content
Avaloi

Deploys, rollback, and where the Code tab went

The Code tab is gone. The Code card (staging and multidevs) and the Deploys card (live) are the first cards on Info. Builds and avaloi.yml are one click away.

Files used to have a Code sub-tab. Everything it held now sits where you already look, so old links to it open Info.

You want to Go to
See or change the development mode (SFTP or Git) Staging or a multidev, Info, card Code, the SFTP | Git switch. New environments start in Git mode
Clone the site Info, card Code, Clone with Git
Add an SSH key or an HTTPS token Info, card Avaloi Git
Commit the changes made on staging in SFTP mode, or pull new commits Info, card Code: Commit changes and Pull latest commits
Read a commit's diff Info, card Code, Commit history, Diff
Connect GitHub, GitLab, Bitbucket, or another Git host Info, card Connect an external repository
Deploy staging to live Live, Info, card Deploys, Deploy to live (or Promote to live in the Environment details card)
Merge a multidev into staging The multidev's Info, card Code, Merge into staging, or Merge on Manage environments
Create or delete a multidev Manage environments, from the environment switcher
Copy a database or uploads between environments Staging or a multidev, Info, card Clone database and files
Roll back live Live, Info, card Deploys, Deployment history
Read build logs, check avaloi.yml Info, card Deploys, Builds and details (or Deploys in Environment details)
Set environment variables Info, card Environment variables

Git mode and SFTP mode

New staging and multidev environments start in Git mode: a read-only release of their branch. Code changes only through Git, by a push to the branch, a merge, a pull from a connected repository, a promote, or a reset from live. wp-admin cannot install or update plugins or themes, but you can still activate and deactivate them. Uploads and cache folders stay writable.

To install from wp-admin or edit files over SFTP, switch that environment to SFTP mode with the SFTP | Git switch. Nothing is lost: the working tree starts as a copy of the code the environment runs now. To switch back, commit your changes first. If changes are waiting, Avaloi says how many and offers Commit and switch (with a commit message) or Discard and switch. Environments made before this default keep the mode they had.

Roll back

Avaloi keeps ten releases on live. To go back:

  1. Pick Live in the environment switcher.
  2. On Info, the Deploys card lists the Deployment history.
  3. Next to an earlier release, click Roll back and confirm.

The older code goes live without a new build. Rollback changes code only: the database and uploads stay as they are. Right after a promote, the promote dialog also offers Undo.

Read commits and builds

The Code card lists the commits on the environment's branch with a Diff button on each, and the Deploys card on live has the same button on every commit that is ready to deploy. In the Deploys dialog, the Commits tab lists them too. The Builds tab lists builds with their logs, and avaloi.yml shows the build file and explains any problem in it.

API

  • GET /v1/sites/{id}/releases and POST /v1/releases/{id}/activate
  • GET /v1/sites/{id}/commits and GET /v1/sites/{id}/commits/{sha}
  • GET /v1/environments/{id}/builds and GET /v1/builds/{id}/log
  • GET /v1/sites/{id}/promote/preview and POST /v1/sites/{id}/promote
  • GET /v1/environments/{id}/merge-check and POST /v1/environments/{id}/merge
  • GET /v1/environments/{id}/git and PUT /v1/environments/{id}/connection-mode (see Git access)

Still stuck?

Email [email protected] with your site name and what you tried, or send us a message.