What it does

This action uploads your files from a Git / GitHub / Bitbucket repository or Buddy’s pipeline filesystem to UpCloud, the cloud hosting platform.

How it works

The action is aware about what is currently on the server and will upload only what has changed between revisions/pushes. It uploads new files, updates the changed ones and deletes everything that was deleted from the repository. The same applies to the deployments from the pipeline filesystem: only changes are deployed between executions.

The action uses the UpCloud API user credentials to connect to an UpCloud server.

Good to know

  • Directories with unversioned files (e.g. uploaded manually) will not be deleted from the server if they are deleted in the repository
  • The first execution deploys everything from scratch by default. If you have legacy files on the server, you can provide the Current Revision in the pipeline settings
  • If you roll back by selecting a previously deployed revision, the action will deploy what is necessary to revert the site to the previous state
  • In the pipeline settings is possible to provide a URL of the target server so it can be easily opened in a browser from the pipelines list
  • Poor & dropped connections are handled by automatic retries. The retries will continue in case the connection drops
  • The tool supports multithreading to speed up deployments
  • Sometimes it helps to select the passive mode for the connection, e.g. when the target server is behind a firewall or the connection isn't stable enough
  • It is possible to test the action before adding. Once the test is executed, it verifies the connection and permissions for creating and deleting files and directories. The test cleans up after itself

Action preview

screenshot

UpCloud Action Features

  • Directories with unversioned files (e.g. uploaded manually) will not be deleted from the server if they are deleted in the repository
  • The first execution deploys everything from scratch by default. If you have legacy files on the server, you can provide the Current Revision in the pipeline settings
  • If you roll back by selecting a previously deployed revision, the action will deploy what is necessary to revert the site to the previous state
  • You can provide the URL of the target server in the pipeline settings so it can be easily opened in a browser from the pipelines list
  • Poor & dropped connections are handled by automatic retries. The retries will continue in case the connection drops
  • The tool supports multithreading to speed up deployments
  • If several actions are connecting to the same server, use Environment Variables to manage user & password credentials instead of providing fixed values in the inputs
  • Once correct login details are provided, it is possible to browse the remote server and select the Remote path (target path for the deployments) from Buddy’s UI instead of typing it manually
  • Sometimes it helps to select the passive mode for the connection, e.g. when the target server is behind a firewall or the connection isn't stable enough
  • Buddy supports passwords, SSH keys, and Buddy's SSH keys as a means of authentication. Passphrases are supported, too
  • You can define SSH keys as ENV VARs and select them in the action details for authentication

More about UpCloud

UpCloud

Do more with UpCloud

Buddy allows you to instantly connect UpCloud with 100+ actions to automate your development and build better apps faster.

1 - 9 (of 107)