Fully featured and highly configurable SFTP server with optional FTP/S and WebDAV support - S3, Google Cloud Storage, Azure Blob

SFTPGo

CI Status Code Coverage Go Report Card License: GPL v3 Docker Pulls Mentioned in Awesome Go

Fully featured and highly configurable SFTP server with optional FTP/S and WebDAV support, written in Go. Several storage backends are supported: local filesystem, encrypted local filesystem, S3 (compatible) Object Storage, Google Cloud Storage, Azure Blob Storage, SFTP.

Features

  • SFTPGo uses virtual accounts stored inside a "data provider".
  • SQLite, MySQL, PostgreSQL, bbolt (key/value store in pure Go) and in-memory data providers are supported.
  • Each local account is chrooted in its home directory, for cloud-based accounts you can restrict access to a certain base path.
  • Public key and password authentication. Multiple public keys per user are supported.
  • SSH user certificate authentication.
  • Keyboard interactive authentication. You can easily setup a customizable multi-factor authentication.
  • Partial authentication. You can configure multi-step authentication requiring, for example, the user password after successful public key authentication.
  • Per user authentication methods. You can configure the allowed authentication methods for each user.
  • Custom authentication via external programs/HTTP API is supported.
  • Data At Rest Encryption is supported.
  • Dynamic user modification before login via external programs/HTTP API is supported.
  • Quota support: accounts can have individual quota expressed as max total size and/or max number of files.
  • Bandwidth throttling is supported, with distinct settings for upload and download.
  • Per user maximum concurrent sessions.
  • Per user and per directory permission management: list directory contents, upload, overwrite, download, delete, rename, create directories, create symlinks, change owner/group and mode, change access and modification times.
  • Per user files/folders ownership mapping: you can map all the users to the system account that runs SFTPGo (all platforms are supported) or you can run SFTPGo as root user and map each user or group of users to a different system account (*NIX only).
  • Per user IP filters are supported: login can be restricted to specific ranges of IP addresses or to a specific IP address.
  • Per user and per directory shell like patterns filters are supported: files can be allowed or denied based on shell like patterns.
  • Virtual folders are supported: directories outside the user home directory can be exposed as virtual folders.
  • Configurable custom commands and/or HTTP notifications on file upload, download, pre-delete, delete, rename, on SSH commands and on user add, update and delete.
  • Automatically terminating idle connections.
  • Automatic blocklist management is supported using the built-in defender.
  • Atomic uploads are configurable.
  • Support for Git repositories over SSH.
  • SCP and rsync are supported.
  • FTP/S is supported. You can configure the FTP service to require TLS for both control and data connections.
  • WebDAV is supported.
  • Two-Way TLS authentication, aka TLS with client certificate authentication, is supported for REST API/Web Admin, FTPS and WebDAV over HTTPS.
  • Support for serving local filesystem, encrypted local filesystem, S3 Compatible Object Storage, Google Cloud Storage, Azure Blob Storage or other SFTP accounts over SFTP/SCP/FTP/WebDAV.
  • Per user protocols restrictions. You can configure the allowed protocols (SSH/FTP/WebDAV) for each user.
  • Prometheus metrics are exposed.
  • Support for HAProxy PROXY protocol: you can proxy and/or load balance the SFTP/SCP/FTP/WebDAV service without losing the information about the client's address.
  • REST API for users and folders management, backup, restore and real time reports of the active connections with possibility of forcibly closing a connection.
  • Web based administration interface to easily manage users, folders and connections.
  • Easy migration from Linux system user accounts.
  • Portable mode: a convenient way to share a single directory on demand.
  • SFTP subsystem mode: you can use SFTPGo as OpenSSH's SFTP subsystem.
  • Performance analysis using built-in profiler.
  • Configuration format is at your choice: JSON, TOML, YAML, HCL, envfile are supported.
  • Log files are accurate and they are saved in the easily parsable JSON format (more information).

Platforms

SFTPGo is developed and tested on Linux. After each commit, the code is automatically built and tested on Linux, macOS and Windows using a GitHub Action. The test cases are regularly manually executed and passed on FreeBSD. Other *BSD variants should work too.

Requirements

  • Go 1.15 or higher as build only dependency.
  • A suitable SQL server to use as data provider: PostgreSQL 9.4+ or MySQL 5.6+ or SQLite 3.x.
  • The SQL server is optional: you can choose to use an embedded bolt database as key/value store or an in memory data provider.

Installation

Binary releases for Linux, macOS, and Windows are available. Please visit the releases page.

An official Docker image is available. Documentation is here.

Some Linux distro packages are available:

  • For Arch Linux via AUR:
    • sftpgo. This package follows stable releases. It requires git, gcc and go to build.
    • sftpgo-bin. This package follows stable releases downloading the prebuilt linux binary from GitHub. It does not require git, gcc and go to build.
    • sftpgo-git. This package builds and installs the latest git master. It requires git, gcc and go to build.
  • Deb and RPM packages are built after each commit and for each release.
  • For Ubuntu a PPA is available here.

You can easily test new features selecting a commit from the Actions page and downloading the matching build artifacts for Linux, macOS or Windows. GitHub stores artifacts for 90 days.

Alternately, you can build from source.

Configuration

A full explanation of all configuration methods can be found here.

Please make sure to initialize the data provider before running the daemon!

To start SFTPGo with the default settings, simply run:

sftpgo serve

Check out this documentation if you want to run SFTPGo as a service.

Data provider initialization and management

Before starting the SFTPGo server please ensure that the configured data provider is properly initialized/updated.

For PostgreSQL and MySQL providers, you need to create the configured database. For SQLite, the configured database will be automatically created at startup. Memory and bolt data providers do not require an initialization but they could require an update to the existing data after upgrading SFTPGo.

SFTPGo will attempt to automatically detect if the data provider is initialized/updated and if not, will attempt to initialize/ update it on startup as needed.

Alternately, you can create/update the required data provider structures yourself using the initprovider command.

For example, you can simply execute the following command from the configuration directory:

sftpgo initprovider

Take a look at the CLI usage to learn how to specify a different configuration file:

sftpgo initprovider --help

You can disable automatic data provider checks/updates at startup by setting the update_mode configuration key to 1.

If for some reason you want to downgrade SFTPGo, you may need to downgrade your data provider schema and data as well. You can use the revertprovider command for this task.

We support the follwing schema versions:

  • 6, this is the latest version
  • 4, this is the schema for v1.0.0-v1.2.x

So, if you plan to downgrade from git master to 1.2.x, you can prepare your data provider executing the following command from the configuration directory:

sftpgo revertprovider --to-version 4

Take a look at the CLI usage to learn how to specify a different configuration file:

sftpgo revertprovider --help

The revertprovider command is not supported for the memory provider.

Users and folders management

After starting SFTPGo you can manage users and folders using:

To support embedded data providers like bolt and SQLite we can't have a CLI that directly write users and folders to the data provider, we always have to use the REST API.

Tutorials

Some step-to-step tutorials can be found inside the source tree howto directory.

Authentication options

External Authentication

Custom authentication methods can easily be added. SFTPGo supports external authentication modules, and writing a new backend can be as simple as a few lines of shell script. More information can be found here.

Keyboard Interactive Authentication

Keyboard interactive authentication is, in general, a series of questions asked by the server with responses provided by the client. This authentication method is typically used for multi-factor authentication.

More information can be found here.

Dynamic user creation or modification

A user can be created or modified by an external program just before the login. More information about this can be found here.

Custom Actions

SFTPGo allows to configure custom commands and/or HTTP notifications on file upload, download, delete, rename, on SSH commands and on user add, update and delete.

More information about custom actions can be found here.

Virtual folders

Directories outside the user home directory can be exposed as virtual folders, more information here.

Other hooks

You can get notified as soon as a new connection is established using the Post-connect hook and after each login using the Post-login hook. You can use your own hook to check passwords.

Storage backends

S3 Compatible Object Storage backends

Each user can be mapped to the whole bucket or to a bucket virtual folder. This way, the mapped bucket/virtual folder is exposed over SFTP/SCP/FTP/WebDAV. More information about S3 integration can be found here.

Google Cloud Storage backend

Each user can be mapped with a Google Cloud Storage bucket or a bucket virtual folder. This way, the mapped bucket/virtual folder is exposed over SFTP/SCP/FTP/WebDAV. More information about Google Cloud Storage integration can be found here.

Azure Blob Storage backend

Each user can be mapped with an Azure Blob Storage container or a container virtual folder. This way, the mapped container/virtual folder is exposed over SFTP/SCP/FTP/WebDAV. More information about Azure Blob Storage integration can be found here.

SFTP backend

Each user can be mapped to another SFTP server account or a subfolder of it. More information can be found here.

Encrypted backend

Data at-rest encryption is supported via the cryptfs backend.

Other Storage backends

Adding new storage backends is quite easy:

  • implement the Fs interface.
  • update the user method GetFilesystem to return the new backend
  • update the web interface and the REST API CLI
  • add the flags for the new storage backed to the portable mode

Anyway, some backends require a pay per use account (or they offer free account for a limited time period only). To be able to add support for such backends or to review pull requests, please provide a test account. The test account must be available for enough time to be able to maintain the backend and do basic tests before each new release.

Brute force protection

The connection failed logs can be used for integration in tools such as Fail2ban. Example of jails and filters working with systemd/journald are available in fail2ban directory.

You can also use the built-in defender.

Account's configuration properties

Details information about account configuration properties can be found here.

Performance

SFTPGo can easily saturate a Gigabit connection on low end hardware with no special configuration, this is generally enough for most use cases.

More in-depth analysis of performance can be found here.

Release Cadence

SFTPGo releases are feature-driven, we don't have a fixed time based schedule. As a rough estimate, you can expect 1 or 2 new releases per year.

Acknowledgements

SFTPGo makes use of the third party libraries listed inside go.mod.

We are very grateful to all the people who contributed with ideas and/or pull requests.

Thank you ysura for granting me stable access to a test AWS S3 account.

Sponsors

I'd like to make SFTPGo into a sustainable long term project and your sponsorship will really help ❤️

Bronze, Silver and Gold sponsors will be listed here (if they wish).

License

GNU GPLv3

Owner
Comments
  • Occasional Malfunction of Connection

    Occasional Malfunction of Connection

    Occasionally (about once every 12-18 hours) the server will stop accepting the correct username and password. It requires a service reboot to fix. This is the closest set of logs to the latest attempt to login while in this error state:

    {"level":"debug","sender":"sftpd","connection_id":"","time":"2019-09-11T03:27.05.832","message":"idle connections check ticker 2019-09-11 03:27:05.832582724 +0000 UTC m=+44100.001673267"}
    {"level":"info","sender":"sftpd","connection_id":"6508f97ceb9b67f8e7fc4928cd9b0cd10615a47024a8279611e9e8f3f6ef24b4","time":"2019-09-11T03:27.05.832","message":"close idle connection, idle time: 6h27m4.548987039s"}
    {"level":"warn","sender":"sftpd","connection_id":"6508f97ceb9b67f8e7fc4928cd9b0cd10615a47024a8279611e9e8f3f6ef24b4","time":"2019-09-11T03:27.05.832","message":"idle connection close failed: close tcp 172.31.18.230:22->148.59.44.16:64168: use of closed network connection"}
    {"level":"info","sender":"sftpd","connection_id":"8fe250f6489ada67fcb4161871743f4358892324ce8841dcbe4903eabfcc2a59","time":"2019-09-11T03:27.05.832","message":"close idle connection, idle time: 6h27m4.535060735s"}
    {"level":"warn","sender":"sftpd","connection_id":"8fe250f6489ada67fcb4161871743f4358892324ce8841dcbe4903eabfcc2a59","time":"2019-09-11T03:27.05.832","message":"idle connection close failed: close tcp 172.31.18.230:22->148.59.44.16:64169: use of closed network connection"}
    {"level":"debug","sender":"sftpd","connection_id":"","time":"2019-09-11T03:27.05.832","message":"check idle connections ended"}
    

    Any ideas? Is there any way to stop it trying to close idle connections? Perhaps that's the problem?

  • Relatively lower performance than OpenSSH

    Relatively lower performance than OpenSSH

    Hi, Thanks for this great project !

    I did some test in my environment and the transfer speed is much lower than OpenSSH.

    Server || --- | --- | OS| Debian 10.2 x64 | CPU| Ryzen5 3600 | RAM| 64GB ECC | Disk| 3* Intel P4510 4TB RAID0 | Ethernet| Mellanox ConnectX-3 40GbE|

    Client || --- | --- | OS| Windows 10 1909 x64 | CPU| Threadripper 1920X | RAM| 64GB ECC | Disk| Samsung 960EVO 1TB | Ethernet| Mellanox ConnectX-3 40GbE|

    Under Filezilla I can get 500MB/s with OpenSSH, but only about 200MB/s with sftpgo.

    In both case I'm using AES256-CTR as cipher and SHA-256 as MAC, I've also tried AES128-CTR but nothing changes.

    CPU usage of sftpgo is higher than OpenSSH:

      PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND 
     4527 sftp      20   0 1795576  52044   8628 R 133.5   0.6   2:12.13 sftpgo 
    
      PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND 
    27934 xxxxxx    20   0   17112   5360   4188 R  67.8   0.1   0:10.01 sshd                                                  
    27942 xxxxxx    20   0   17112   5344   4176 R  27.4   0.1   0:12.52 sshd 
    

    In both case I've got a maximum TCP window size of 4MB.

  • Account Permissions and sub-dirs

    Account Permissions and sub-dirs

    I have a strange issue with an account:

    My user defitinion is as follows:

          {
            "id": 1,
            "status": 1,
            "username": "test",
            "password": "***",
            "home_dir": "/sftp",
            "uid": 1100,
            "gid": 1100,
            "permissions": {
              "/": [
                "list"
              ],
              "/sftp/test/upload: [
                "list",
                "upload",
                "download",
                "rename",
                "create_dirs",
                "delete"
              ]
            }
          },
    

    Although I can list in all directories in /sftp, I wanted to be able to upload to /sftp/test/upload with the above definition. Am i doing something incorrect here?

    Using edge

  • Add Dockerfile and GitHub Actions workflow

    Add Dockerfile and GitHub Actions workflow

    This PR adds a Dockerfile to the project. It's largely based on my previous Go applications and the existing examples in the repo. It's not perfect though, so we might need some fine tuning in the future, particularly around volumes and configuration.

    Open questions:

    • What are backups? Are they supposed to be saved to persistent storage or are they only meaningful during the lifecycle of the application?
    • Where does the credential path point? What's being read from there? (Existing dockerfiles contain no reference)

    Currently the above settings can only be overridden from environment variables, because defaults are defined for them in env vars. (I think that's an acceptable compromise though).

    I'll work with this image anyway, so I'll provide patches along the way.

    The PR also adds a GitHub Actions workflow for building Docker images based on the official example (I removed a few parts):

    https://github.com/docker/build-push-action#complete-workflow

    After merging the PR, @drakkan , you'll need to do some manual steps though:

    1. Login to ghcr.io: docker login ghcr.io. You'll need a GH PAT for that (with package write scope)
    2. Build the image locally: docker build -t ghcr.io/drakkan/sftpgo:edge .
    3. Push the image docker push ghcr.io/drakkan/sftpgo:edge
    4. Go to packages under your account
    5. Make the package public
    6. Configure a secret called CR_PAT with package write scope under secrets
    7. Uncomment the relevant parts in docker.yml (login and push) (happy to review a PR)

    These steps are necessary, because GitHub packages seem to be super private for the first time, so you need to push and publish manually. (Although rereading the above: you should also be fine to do step 6 and 7 first, since CR_PAT will be your token anyway, and then step 5 to publish the package. I had some trouble with packages under organizations, but this is under your personal account, so it should be fine)

    Sorry about the complicated process, let me know if you need any help.

  • How to install sftpGO with Traefik

    How to install sftpGO with Traefik

    Hello, I would like to install SftpGO with Traefik, the problem is that it does not work,

    I access the dashboard without problem but when I connect with Filezilla in SFTP it doesn't work and I really don't understand why...?

    My configuration :

    traefik.yml image

    docker-compose.yml

    `version: '3.3' services:

    ftp: container_name: ftp image: drakkan/sftpgo:edge-alpine-slim networks: network-traefik: ipv4_address: 192.168.128.xxx labels: - "traefik.enable=true" - "traefik.tcp.routers.ftp.rule=HostSNI(*)" - "traefik.tcp.routers.ftp.entrypoints=sftp" - "traefik.tcp.services.ftp.loadbalancer.server.port=2022" - "traefik.http.routers.uiftp.rule=Host(MYDOMAIN.FR)" - "traefik.http.routers.uiftp.entrypoints=https" - "traefik.http.routers.uiftp.tls.certresolver=http" - "traefik.http.services.uiftp.loadbalancer.server.port=8080"

    networks: network-traefik: external: true`

    I'm really stuck help me! :D

  • Error with WebDAV to SFTP Backend, works with SFTP to SFTP Backend

    Error with WebDAV to SFTP Backend, works with SFTP to SFTP Backend

    Hey there @drakkan, thank so much for your work on this, it's a great tool!

    I'm trying to connect to an SFTP server on the backend (server using OpenSSH) but am getting error SSH_FX_FAILURE when doing so. It only affects WebDAV. Without changing any settings, if I open the virtual folder using an SFTP connection, it shows the backend server's file structure fine.

    Computer via SFTP > SFTPGo > Virtual Folder SFTP Backend > Success Computer via WebDAV > SFTPGo > Virtual Folder SFTP Backend > Fails with SSH_FX_FAILURE


    Figured out what is causing this. If a folder is symlinked, SFTP doesn't find out about it until that folder is opened, whereas WebDAV, at least in Windows, tries to access that folder upon opening its parent folder.

    Computer via SFTP > SFTPGo > Virtual Folder SFTP Backend: accessing /parent with /parent/inaccessible subdirectory inside of it works until I open /parent/inaccessible any accessible folders are fine

    Computer via WebDAV > SFTPGo > Virtual Folder SFTP Backend: accessing /parent with /parent/inaccessible subdirectory inside of it does not let me open /parent at all cannot access any folders as long as at least 1 folder is inaccessible

    Error from log: Oct 16 00:07:35 control sftpgo[29746]: {"level":"info","time":"2021-10-16T00:07:35.724","sender":"webdavd","elapsed_ms":86,"method":"PROPFIND","proto":"HTTP/2.0","remote_addr":"<redacted>","request_id":"c5l5s5p6q9grffh6gui0","uri":"https://mySFTPGOserver/virtualfolder","user_agent":"Microsoft-WebDAV-MiniRedir/10.0.19043","error":"sftp: \"Failure\" (SSH_FX_FAILURE)"}

    Oct 16 00:43:43 control sftpgo[31376]: {"level":"warn","time":"2021-10-16T00:43:43.931","sender":"sftpfs \"<redacted>"","connection_id":"DAV_c5l6d3p6q9gri73uier0","message":"Invalid path resolution, dir \"/real/path/to/404\" original path \"/website/public_html/404\" resolved \"/home/user/web/website/public_html/404\" err: path \"/real/path/to/404\" is not inside: \"/home/user/web\""}


    Also discovered another issue. If you're using WebDAV -> SFTPGo -> S3 Backend, a password of Abcde!+ will not work but Abcde will work. If using Abcde!+ logs say "invalid credentials". If you remove the S3 Backend virtual folder, without changing anything, you can successfully login without error (local folders work fine).

    Thank you

  • Consider making the sdk package a separate module

    Consider making the sdk package a separate module

    It's a common practice to make packages that are supposed to be consumed by third party code (eg. plugins) separate modules. (Example: api packages in most Hashicorp software).

    This would make the SDK package lighter in terms of dependencies (it doesn't need all deps of SFTPGo).

    At the same time, until plugins are experimental, it might be easier to keep it in the same module (although making an existing package a module later has it's own quirks).

  • Symlinks are not supported

    Symlinks are not supported

    I am running a server on a local dir:

    sftpgo portable -d ~/Base/shared --permissions 'list,download' --username 'x' --password 'x' --webdav-port 8114 --sftpd-port 8115 --ftpd-port 8116 --log-verbose --log-file-path sftpgo.log
    

    I symlink other directories I want to share into ~/Base/shared, but sftpgo does not handle the symlinks correctly. (I know sftpgo supports virtual dirs, but I use that ~/Base/shared for other services, too, and I do not want to duplicate my config.)

    PS: That command also does not start the webdav server, saying

    {"level":"debug","time":"2021-03-05T10:49:41.514","sender":"service","message":"WebDAV server not started, disabled in config file"}
    
  • [FTP] Invalid passive IP gives error `index out of range`

    [FTP] Invalid passive IP gives error `index out of range`

    I configured the passive port range, but first forgot, then misplaced the passive ip configuration. Sftpgo then gives a confusing "index out of range" error, probably because it's searching for the passive ip and not finding it?

  • Simplify configuration file/dir

    Simplify configuration file/dir

    Currently configuring SFTPGo is a bit complicated in the various environments it might run in (thanks to the available Docker image).

    Namely, the fact that the config dir is tied to a bunch of other things (host keys, sqlite, etc) and that you cannot pass a full path to a config file is a bit uncomfortable.

    To give you a concrete example: when running on Kubernetes, I can mount a config map to a certain path (eg. /etc/sftpgo), containing an sftpgo.yaml file. The problem is, by default, SFTPGo will try to write default host keys to the config dir, but that mount is read only. Right now I solve this by manually setting the path to host keys.

    I see two potential improvements:

    • allow passing a full path to SFTPGo as a flag (analogous to viper.SetConfigFile)
    • introduce a separate directory for host keys and other stuff (although there are already enough directories)

    The first approach would allow mounting a config map under something like /etc/sftpgo/config (and since --config-file is already taken it would allow passing --config-path /etc/sftpgo/config/sftpgo.yaml) and would not interfere with the current config dir concept (/etc/sftpgo would still be writable).

  • webdav

    webdav

    hello, I use sftpgo as a bridge to an s3 endpoint that when a file is uploaded moves it elsewhere. Using webdav and uploading a file with windows the explorer say:

    explorer_nfqgfjM0YX

    this happens because the file is no longer avilable and I guess it is done a stat that fails. Using Curl,for obvious reasons, is ok :

    > PUT /fake0/out/test.bin HTTP/1.1
    > Authorization: Basic XYZ
    > User-Agent: curl/7.29.0
    > Host: FQDN:2080
    > Accept: */*
    > Content-Length: 441
    > Expect: 100-continue
    >
    < HTTP/1.1 100 Continue
    * We are completely uploaded and fine
    < HTTP/1.1 201 Created
    < Etag: "1641d9285d8c3d961b9"
    < Date: Tue, 27 Oct 2020 12:28:29 GMT
    < Content-Length: 7
    < Content-Type: text/plain; charset=utf-8
    <
    * Connection #0 to host FQDN left intact
    
    

    could it be a cache problem (assuming you use it) of the driver that uses sftpgo?

    thnx a lot.

  • No easy way to access effective user properties in custom actions

    No easy way to access effective user properties in custom actions

    Hello,

    I'm currently implementing a custom provider hook (the executable kind) to make a set of directories on creating users. Those users are all members of a primary group suppliers, which has set the home directory to /srv/sftpgo/data/suppliers/%username%. The groups documentation states:

    home dir, if set for the group will replace the one defined for the user. The %username% placeholder is replaced with the username

    However, when recieving the user object within the hook the environment variable SFTPGO_PROVIDER_OBJECT contains the default path, in this context /srv/sftpgo/data/%username%.

    Now I see several ways to work around this:

    • Hard code the group home directory.
    • Query the group home directory via the sftpgo API and do the substitution by hand.
    • Create the directories via the sftpgo API.

    However, I'm wondering if the passed user object in the context of the provider hooks should contain the effective properties (with group inheritance applied) instead.

  • Feature Requests: Autocreate Home Directory, Multilanguage

    Feature Requests: Autocreate Home Directory, Multilanguage

    Hi,

    in first I'm glad for your project. Fantastic job 👍.

    Now, i have two more feature requests to think about.

    1. Autocreate Home Directory after user was created. Now, home dir is created after first login.
    2. Multilanguge for possible translate your project to another language than English.

    Thank's for your answer.

  • Upgrade from v2.2.3 to 2.3.1

    Upgrade from v2.2.3 to 2.3.1

    Hello Drakkan,

    I created a new environment with the same data and while migrating I got this error.

    Capture d’écran 2022-06-27 à 15 35 44

    Originally posted by @selimfek in https://github.com/drakkan/sftpgo/issues/871#issuecomment-1167394551

  • Feature request : Role account manager

    Feature request : Role account manager

    Hello. I have a need, maybe can be interesting / usefull for others : possibility to distinct a super admin role and admin role => account manager. Super admin will access to everytihing of course. Admin / Account manager will be allow to manage only users created by itself.

    Explanation : in my case, i want to delegate an access to some users to create/update/delete user accounts, but i would like they don't have access to accounts created by IT members or other admin / account managers.

    Bonus : Force user created by an admin / account manager with a template for expiration date (creation date + 2 month for example), force path of the user home_dir to a specific folder (/sftp/GroupA/%user_name%, specific permissions, specific protocol allowed, etc ...

  • Mount folder to two virtual folders

    Mount folder to two virtual folders

    • Running on: Docker
    • Version: v2-alpine
    • Build: SFTPGo 2.2.2-a7921500-2022-02-06T14:13:37Z +metrics +azblob +gcs +s3 +bolt +mysql +pgsql +sqlite +portable

    Hi. First off, I want to say that this is an amazing tool.

    Moving on, I'm testing it as a PoC and I encountered a weird situation, that granted, isn't something that most people would do. I was trying to mount a folder that I defined in folders to two different virtual folders of a user. At that point I got an error seen in the picture bellow.

    image

    I don't know if it's a bug or a feature, and I didn't quite find another ticket about this(feel free to close this if there's one already). The main reason why I'd want to do that is backwards compatibility to some legacy things that are setup.

    I can also provide logs generated during the process, in the case where it's a bug.

Simple wrapper for google/pprof to run as webserver
Simple wrapper for google/pprof to run as webserver

pprof-webserver simple wrapper for google/pprof to run as webserver left column shows list of profiles stored on the server new profiles can be upload

Jan 4, 2022
High Performance, Kubernetes Native Object Storage
High Performance, Kubernetes Native Object Storage

MinIO Quickstart Guide MinIO is a High Performance Object Storage released under Apache License v2.0. It is API compatible with Amazon S3 cloud storag

Aug 4, 2022
OpenAPI specs for your Go server, generated at server runtime. No CLI, no code generation, and no HTTP

Overview "oas" is short for "OpenAPI Spec". Go package for generating OpenAPI docs at runtime. Non-features: No code generation. No CLI. No magic comm

Dec 3, 2021
Go web server - A web server that can accept a GET request and serve a response.

go_web_server A web server that can accept a GET request and serve a response. Go is a great language for creating simple yet efficient web servers an

Jan 3, 2022
a simple http server as replacement of python -m http.server

ser a simple http server as replacement of python -m http.server

Feb 16, 2022
A Language Server Protocol (LSP) server for Jsonnet

Jsonnet Language Server A Language Server Protocol (LSP) server for Jsonnet. Features Jump to definition self-support.mp4 dollar-support.mp4 Error/War

Aug 3, 2022
ready-to-use RTSP / RTMP server and proxy that allows to read, publish and proxy video and audio streams
ready-to-use RTSP / RTMP server and proxy that allows to read, publish and proxy video and audio streams

rtsp-simple-server is a simple, ready-to-use and zero-dependency RTSP / RTMP server and proxy, a software that allows users to publish, read and proxy live video and audio streams. RTSP is a specification that describes how to perform these operations with the help of a server, that is contacted by both publishers and readers and relays the publisher's streams to the readers.

Aug 9, 2022
⚡ A fast, lightweight, and secure chat protocol, client and server, written in Go.

⚡ A fast, lightweight, and secure chat protocol, client and server, written in Go.

Jan 19, 2022
RBTI Golang Server uses PostgreSQL and for its main database and uses Elasticsearch

RBTI Golang Server This server is used for my thesis project, it uses PostgreSQL and for its main database and uses Elasticsearch for faster query spe

Jan 17, 2022
✨ A lightweight HTTP server based on GO, will try to detect your OS and architecture and return as SHELL script. ✨
✨ A lightweight HTTP server based on GO, will try to detect your OS and architecture and return as SHELL script. ✨

✨ A lightweight HTTP server based on GO, will try to detect your OS and architecture and return as SHELL script. ✨

May 5, 2022
A feature flag solution, with only a YAML file in the backend (S3, GitHub, HTTP, local file ...), no server to install, just add a file in a central system and refer to it. 🎛️
A feature flag solution, with only a YAML file in the backend (S3, GitHub, HTTP, local file ...), no server to install, just add a file in a central system and refer to it. 🎛️

??️ go-feature-flag A feature flag solution, with YAML file in the backend (S3, GitHub, HTTP, local file ...). No server to install, just add a file i

Aug 2, 2022
High-performance PHP application server, load-balancer and process manager written in Golang
High-performance PHP application server, load-balancer and process manager written in Golang

[RR2-BETA] RoadRunner is an open-source (MIT licensed) high-performance PHP application server, load balancer, and process manager. It supports runnin

Aug 3, 2022
Oogway is a simple web server with dynamic content generation and extendability in mind supporting a Git based workflow.

Oogway Oogway is a simple web server with dynamic content generation and extendability in mind supporting a Git based workflow. It's somewhere in betw

Jul 31, 2022
Opinionated boilerplate Golang HTTP server with CORS, OPA, Prometheus, rate-limiter for API and static website.
Opinionated boilerplate Golang HTTP server with CORS, OPA, Prometheus, rate-limiter for API and static website.

Teal.Finance/Server Opinionated boilerplate HTTP server with CORS, OPA, Prometheus, rate-limiter… for API and static website. Origin This library was

Mar 26, 2022
HTTP server receives events and publishes them to STAN
HTTP server receives events and publishes them to STAN

Publishes events to Nats Streaming(STAN) synchornously and asynchronously. Cache events's publish-state using Redis and Store events using MongoDB.

Jan 24, 2022
GRPC And REST Server Code challenge

Code challenge This repo contains 2 entry points. 1. GRPC Server (cmd/grpcserver/main.go) The grpc server exposes two rpcs: rpc SaveVLAN (VLAN) return

Nov 16, 2021
A very simple Golang server handling basic GET and POST requests

GOLANG SERVER INTRO As a true Blockchain enthusiast, I had to learn Solidity and Golang to participate to several projects. This repository consists o

Nov 17, 2021
RoadRunner: an open-source high-performance PHP application server, load balancer, and process manager
RoadRunner: an open-source high-performance PHP application server, load balancer, and process manager

RoadRunner is an open-source (MIT licensed) high-performance PHP application server, load balancer, and process manager. It supports running as a serv

Jan 13, 2022