-
-
Notifications
You must be signed in to change notification settings - Fork 307
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
Add Subdomain Configuration for Seafile #691
base: master
Are you sure you want to change the base?
Add Subdomain Configuration for Seafile #691
Conversation
Signed-off-by: Stephon Parker <[email protected]>
Signed-off-by: Stephon Parker <[email protected]>
Signed-off-by: Stephon Parker <[email protected]>
Signed-off-by: Stephon Parker <[email protected]>
Signed-off-by: Stephon Parker <[email protected]>
Signed-off-by: Stephon Parker <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Needs to match the format of the other confs. Please use the template as a starting point and go from there.
Also please remove unnecessary headers, which are already included in other confs loaded (ie. proxy.conf)
This pull request has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
Description
Seafile is an open source file sync and share platform, focusing on reliability and performance. Seafile's built-in collaborative document SeaDoc, make it easy for collaborative writing and publishing documents. This configuration is to allow Seafile to work with SWAG, specifically allowing for file transfers to work.
Benefits of this PR and context
Credit for this goes to this issue here. Without this configuration it's unclear on how to get Seafile to load when fronted by SWAG. In addition file transfers fail even when the GUI of the service loads. Issue can be observed here in the Unraid Forum.
How Has This Been Tested?
I am running Unraid 6.12.11 with SWAG in front of any application exposed outside of my home LAN. I use Cloudflare for my DNS to manage resolutions for my domain. I have one custom docker network used for all services leveraging SWAG and I am using a different port in my setup.
I have tested loading the service from both my LAN and public networks. I have tested file transfers with 1mb, 10mb, 1000mb, and 2gb files to ensure the functionality continues to work.
Source / References
I've already linked a few sources above, but again was able to figure this out leveraging the following resources: