SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-03-31 06:34:17 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

[PR #2987] [MERGED] Seafile #4014

New Issue
Closed
opened 2025-11-20 06:07:52 -05:00 by saavagebueno · 0 comments
saavagebueno commented 2025-11-20 06:07:52 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/community-scripts/ProxmoxVE/pull/2987
Author: @dave-yap
Created: 3/10/2025
Status: ✅ Merged
Merged: 3/11/2025
Merged by: @michelroegl-brunner

Base: main ← Head: seafile

📝 Commits (10+)

📊 Changes

3 files changed (+371 additions, -0 deletions)

View changed files

➕ ct/seafile.sh (+43 -0)
➕ install/seafile-install.sh (+281 -0)
➕ json/seafile.json (+47 -0)

📄 Description

✍️ Description

Seafile is an open source file sync and share platform, focusing on reliability and performance.

🔗 Related PR / Discussion / Issue

Link: #

✅ Prerequisites

Before this PR can be reviewed, the following must be completed:

  • [✅] Self-review performed – Code follows established patterns and conventions.
  • [✅] Testing performed – Changes have been thoroughly tested and verified.

🛠️ Type of Change

Select all that apply:

  • [] 🐞 Bug fix – Resolves an issue without breaking functionality.
  • [] ✨ New feature – Adds new, non-breaking functionality.
  • [] 💥 Breaking change – Alters existing functionality in a way that may require updates.
  • [✅] 🆕 New script – A fully functional and tested script or script set.

📋 Additional Information (optional)

This script exposes port 8000 without TLS for the frontend for users. It can be changed manually via config files. I included a simple script so that users can easily shift from internal storage to external storage for the files that are hosted. Useful credentials are simply found at seafile.creds as usual. The admin password can be changed upon login as well so no harm in being plaintext just for initial setup. However, there are currently no upgrade paths as v12 binary installation is not released yet as per this post: Seafile Forum Edits will need to be done in order to include upgrade process as well as difference in future dependencies.

Edits were made so minimal version pinning for python dependencies is used.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/community-scripts/ProxmoxVE/pull/2987 **Author:** [@dave-yap](https://github.com/dave-yap) **Created:** 3/10/2025 **Status:** ✅ Merged **Merged:** 3/11/2025 **Merged by:** [@michelroegl-brunner](https://github.com/michelroegl-brunner) **Base:** `main` ← **Head:** `seafile` --- ### 📝 Commits (10+) - [`80eb4ae`](https://github.com/community-scripts/ProxmoxVE/commit/80eb4ae0bccaeec548cf86182c9ce89021c523bf) Create zitadel-install.sh - [`d84ae0b`](https://github.com/community-scripts/ProxmoxVE/commit/d84ae0b197f18dd3e28a8118de2b7b5fdc93840e) Create zitadel.json - [`e07d54a`](https://github.com/community-scripts/ProxmoxVE/commit/e07d54ae280068c880567fba435d47ed1401af33) Create zitadel.sh - [`3875f1c`](https://github.com/community-scripts/ProxmoxVE/commit/3875f1c0d049a2961fcce6b26f82ab4646122e1f) Update zitadel.sh - [`43d1337`](https://github.com/community-scripts/ProxmoxVE/commit/43d1337187c7bb0b085744f32709c3ade8f7a00c) Update zitadel.json - [`568f6de`](https://github.com/community-scripts/ProxmoxVE/commit/568f6de72f50dc8b067d5ad9f5498e9b38283810) Update zitadel.sh - [`603127f`](https://github.com/community-scripts/ProxmoxVE/commit/603127f8734bbe54c86f04351bd10b14fb685112) Update zitadel.sh - [`523a243`](https://github.com/community-scripts/ProxmoxVE/commit/523a243fd0642f251800ae39ca02325cf29d28a9) Update zitadel.sh - [`ac794b9`](https://github.com/community-scripts/ProxmoxVE/commit/ac794b946654d32c7fff5d73fa54299986f5b324) Update zitadel.sh - [`37b60fe`](https://github.com/community-scripts/ProxmoxVE/commit/37b60fea41c979268914ba09a0dd4722ae75c1cd) Update zitadel.sh ### 📊 Changes **3 files changed** (+371 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `ct/seafile.sh` (+43 -0) ➕ `install/seafile-install.sh` (+281 -0) ➕ `json/seafile.json` (+47 -0) </details> ### 📄 Description ## ✍️ Description <!-- Provide a clear and concise description of your changes. --> Seafile is an open source file sync and share platform, focusing on reliability and performance. ## 🔗 Related PR / Discussion / Issue Link: # ## ✅ Prerequisites Before this PR can be reviewed, the following must be completed: - [✅] **Self-review performed** – Code follows established patterns and conventions. - [✅] **Testing performed** – Changes have been thoroughly tested and verified. ## 🛠️ Type of Change Select all that apply: - [] 🐞 **Bug fix** – Resolves an issue without breaking functionality. - [] ✨ **New feature** – Adds new, non-breaking functionality. - [] 💥 **Breaking change** – Alters existing functionality in a way that may require updates. - [✅] 🆕 **New script** – A fully functional and tested script or script set. ## 📋 Additional Information (optional) <!-- Provide extra context, screenshots, or references if needed. --> This script exposes port 8000 without TLS for the frontend for users. It can be changed manually via config files. I included a simple script so that users can easily shift from internal storage to external storage for the files that are hosted. Useful credentials are simply found at `seafile.creds` as usual. The admin password can be changed upon login as well so no harm in being plaintext just for initial setup. However, there are currently no upgrade paths as v12 binary installation is not released yet as per this post: [Seafile Forum](https://forum.seafile.com/t/seafile-community-edition-12-0-is-production-ready-new-navigation-and-viewing-experience-enhanced-seadoc-functions-new-knowledge-base-and-more/23084/4) Edits will need to be done in order to include upgrade process as well as difference in future dependencies. Edits were made so minimal version pinning for python dependencies is used. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
saavagebueno added the pull-request label 2025-11-20 06:07:52 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#4014
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?