You can deploy almost any Git repository URL with Fuse, using either HTTPS or SSH (git@). However, to use git@ URLs, you must ensure your server has access to your repositories.
To grant access, you typically register your server’s public SSH key with your source provider, such as GitHub. Previously, to obtain the public SSH key, you had to log in to your server via SSH and manually retrieve the key—a tedious process that could be improved.
Now, when you provision a server with Fuse, the system automatically retrieves your generated public SSH key during the final provisioning step. This key is then stored and displayed to you when adding a new site.
This serves as a reminder to grant your server access to your Git repositories. You can easily copy your server’s public SSH key and add it to your source provider if needed.
To grant access, you typically register your server’s public SSH key with your source provider, such as GitHub. Previously, to obtain the public SSH key, you had to log in to your server via SSH and manually retrieve the key—a tedious process that could be improved.
Now, when you provision a server with Fuse, the system automatically retrieves your generated public SSH key during the final provisioning step. This key is then stored and displayed to you when adding a new site.
This serves as a reminder to grant your server access to your Git repositories. You can easily copy your server’s public SSH key and add it to your source provider if needed.
This quality-of-life improvement saves you the time and effort of logging into your server and manually retrieving the public SSH key.