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

[FEAT] Seafile config file #498

Closed
1 task done
isvein opened this issue Aug 12, 2024 · 5 comments
Closed
1 task done

[FEAT] Seafile config file #498

isvein opened this issue Aug 12, 2024 · 5 comments

Comments

@isvein
Copy link

isvein commented Aug 12, 2024

Is this a new feature request?

  • I have searched the existing issues

Wanted change

Hi :)
Will it someday be an config file for Seafile included?

Reason for change

I try to get seafile to work behind swag.
I can get it to work just fine behind NPM, but not swag
Tried every config file I can find out there, some work and I can log in, but then download/upload does not work with any, even if I set URL correct in seafile settings.

I use unraid and used the "dglb99" image of Seafile

Proposed code change

No response

@isvein isvein added the enhancement New feature or request label Aug 12, 2024
Copy link

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

@j0nnymoe
Copy link
Member

We used to have one included but it got removed to numerous people reporting issues with it and no one within the team uses seafile, we could not test this.

@isvein
Copy link
Author

isvein commented Aug 12, 2024

We used to have one included but it got removed to numerous people reporting issues with it and no one within the team uses seafile, we could not test this.

sad!
Seems like seafile is hard to get to work correctly behind swag :(
I would not mind testing the config and report back what happens, but I get that if no one on the team uses seafile, its harder to get it to work.

@LinuxServer-CI
Copy link
Contributor

This issue 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.

@LinuxServer-CI LinuxServer-CI closed this as not planned Won't fix, can't repro, duplicate, stale Nov 11, 2024
@LinuxServer-CI LinuxServer-CI moved this from Issues to Done in Issue & PR Tracker Nov 11, 2024
Copy link

This issue is locked due to inactivity

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 11, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
Archived in project
Development

No branches or pull requests

3 participants