You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to figure out how (if) I can use sftpgo as a server in my Docker (K8s) environment to receive uploads and store them in an S3 bucket: I need to be able to deploy a sftpgo-based upload service container without any interaction: it should start up and be ready to receive files and save them to a pre-defined S3 bucket. I see that I can configure the protocols via the JSON config file, and it looks as if I can use a REST API to create the necessary user and specify its filesystem (s3config?); can I create the necessary admin user the same way? Is that secure? Basically I'm asking: what's the best practice for deploying sftpgo in this manner (fully pre-configured or programmatically configured via a startup script in the Dockerfile)? ie. I should never have to touch the admin web app.
support requestrequest for free support. Check out our support policy
1 participant
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I'm trying to figure out how (if) I can use sftpgo as a server in my Docker (K8s) environment to receive uploads and store them in an S3 bucket: I need to be able to deploy a sftpgo-based upload service container without any interaction: it should start up and be ready to receive files and save them to a pre-defined S3 bucket. I see that I can configure the protocols via the JSON config file, and it looks as if I can use a REST API to create the necessary user and specify its filesystem (s3config?); can I create the necessary admin user the same way? Is that secure? Basically I'm asking: what's the best practice for deploying sftpgo in this manner (fully pre-configured or programmatically configured via a startup script in the Dockerfile)? ie. I should never have to touch the admin web app.
Beta Was this translation helpful? Give feedback.
All reactions