Fully featured and highly configurable SFTP server with optional FTP/S and WebDAV support - S3, Google Cloud Storage, Azure Blob
git
go
docker
portable
ftp
rsync
s3
google-cloud-storage
sftp
webdav
cloud-storage
prometheus
sftp-server
scp
ftp-server
webdav-server
multi-factor-authentication
proxy-protocol
azure-blob
data-at-rest-encryption
-
Updated
Jul 31, 2021 - Go
The authentication step that produces the link to follow in a browser to authenticate gdfa uses a callback URI. The port that it listens to seems to be random each time the service is started. Could that be standardized, or is there a way to predict what port it will listen to?