Add "S3 Management"

What problem will this feature address?

Applications often need more than just a database. Object storage is another common dependency, especially for user uploads, media, backups, and other large files.

Dokploy already makes it easy to deploy services such as databases, but managing S3-compatible storage currently feels much more manual.

Describe the solution you'd like

Add an "S3 Management" section to Dokploy, similar to how databases are managed.

Users should be able to:

• Create and manage S3-compatible storage instances
• Deploy S3 servers such as MinIO or Garage
• Easily retrieve the connection details for an S3 instance
• View the endpoint, access key, secret key, bucket information, and other relevant credentials
• Ideally have Dokploy generate or expose an S3 connection string / environment variables that can be directly used by applications

For example, an application could reference an S3 resource and receive the required environment variables automatically, similar to how database connection details can be provided.

Why?

I know that S3-compatible servers such as MinIO and Garage can already be deployed through templates. However, after deploying them, getting all of the required connection details is still unnecessarily difficult.

The goal would be to make S3 storage feel like a first-class resource in Dokploy, rather than something users have to manually configure after deploying a template.

Describe alternatives you've considered

Continue using templates such as the Garage template and manually configure the connection details.

This works, but the experience is significantly more cumbersome than having S3 storage managed directly by Dokploy.

Additional context

This would be particularly useful for applications that need object storage alongside their application and database, making the typical:

Application + Database + Object Storage

stack much easier to deploy and configure.

Will you send a PR to implement it?

Yes

Start by reviewing Dokploy’s existing database management and template flows, since the request aims to provide a similar first-class resource. No files, tests, or entry points are identified in the issue. Done would include creating and managing S3-compatible instances, exposing endpoint and credentials, and providing usable connection details or environment variables to applications.