Resources · 4 guides
File Transfer for Developers and Servers
Getting files out of servers, containers and CI pipelines from the command line, without opening inbound ports.
Last updated
About this topic
Getting a file off a machine you reach only through a terminal is a common chore: a log from a production VM, a database dump from a container, a build from a CI runner. SSH-based tools work when you can reach the machine inbound; many environments do not allow that, and cloud buckets add credentials and a copy that must be cleaned up.
These guides compare the options for servers, containers and pipelines, with commands you can run, and explain the security trade-offs of each, including outbound-only links such as srift quick-share.
Guides
- Get Files Off a Remote Server Without Opening Inbound PortsPull logs, dumps and builds from Linux servers, cloud VMs and headless boxes when SSH is not an option: outbound-only methods and their trade-offs.
- Moving Files Out of Docker Containers and Kubernetes Podsdocker cp, kubectl cp, volumes and outbound links compared for getting files out of containers and pods, including distroless and restricted clusters.
- Sharing CI/CD Build Artifacts SecurelyHow to hand a build artifact from a CI job to a person: built-in artifact stores, object storage links and short-lived streamed links compared.
- Automating Secure File Transfer: the SRIFT REST API and SDKsWhat makes a file-transfer API secure, and how to send and receive files from code with SRIFT: local REST endpoints, events and Python and Node.js SDKs.
