Direct code access

# As alternative to Git deployment

We usually recommend to use Git deployment. But not every developer is used to Git yet and it has steep learning curve. Also not all software is ready to be used with Git and Composer. Use rsync, to upload your website.

# SSH

SSH (Secure Shell) is a network protocol to login to remote web servers. SSH is used in the terminal. It's pre-installed with most operating systems. With SSH you login to have an interactive session on the remote server - the environment in our case. SSH is not suited for transferring files from your computer to the server. See the SSH guide for more details.

# SFTP

SFTP (Secure File Transfer Protocol) is a network protocol to transfer files to and from web servers. It's build on top of SSH. You will usually use it with a graphical interface. See the SFTP guide.

# SSH key authentication

To access code by either method, SSH keys are required. Upload your public SSH keys to your personal account with the dashboard. Read more about SSH keys here.

Your code access credentials are stored with your personal account on fortrabbit. This way you always have up-to-date code access on each environment you have access on. It also makes managing the team easy — add/remove collaborators and code access is handled "automagically".