Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docker image without built-in webserver or reverse proxy #437

Open
CyprusSocialite opened this issue Mar 8, 2025 · 1 comment
Open

Docker image without built-in webserver or reverse proxy #437

CyprusSocialite opened this issue Mar 8, 2025 · 1 comment
Labels

Comments

@CyprusSocialite
Copy link

Since Docker is the one and only officially supported deployment method from 12.0, it should be made more flexible and more compliant with containerisation "best practices".

To that end I would propose that there needs to be a Docker image running only Seafile components inside (or perhaps separate images for seahub and the server), allowing users to mix and match them with external, manually configured webservers/reverse proxies.

The existing images that come pre-packaged with Nginx could be made to inherit from these smaller, Seafile-only images, so there will still be a simple "out of the box" deployment option.

@CyprusSocialite
Copy link
Author

This issue has been raised and gained support in the past as #200, and there is a pull request #203 that was approved but remains open

@CyprusSocialite CyprusSocialite changed the title Docker image without build-in webserver or reverse proxy Docker image without built-in webserver or reverse proxy Mar 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants