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

Seafile #2650

Open
wants to merge 50 commits into
base: main
Choose a base branch
from
Open

Seafile #2650

wants to merge 50 commits into from

Conversation

dave-yap
Copy link
Contributor

✍️ 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.

dave-yap and others added 30 commits February 7, 2025 23:46
Edit reference back to upstream build.func
Co-authored-by: Slaviša Arežina <[email protected]>
Co-authored-by: Slaviša Arežina <[email protected]>
Co-authored-by: Slaviša Arežina <[email protected]>
Co-authored-by: Slaviša Arežina <[email protected]>
Co-authored-by: Slaviša Arežina <[email protected]>
Co-authored-by: Slaviša Arežina <[email protected]>
Co-authored-by: Slaviša Arežina <[email protected]>
Co-authored-by: bvdberg01 <[email protected]>
Co-authored-by: bvdberg01 <[email protected]>
Include mc for install; removal of variable ARCH and put into direct links; correct the default resources required
Co-authored-by: bvdberg01 <[email protected]>
correct version output
Copy link
Contributor

⚠️ The script ct/seafile.sh failed with the following message:


Failure in line 189 while executing command 'sudo su - seafile -c bash /opt/seafile/seafile-server-latest/seafile.sh start'

Comment on lines 64 to 83
$STD pip3 install \
django==4.2.* \
future==0.18.* \
mysqlclient==2.1.* \
pymysql \
pillow==10.2.* \
pylibmc \
captcha==0.5.* \
markupsafe==2.0.1 \
jinja2 \
sqlalchemy==2.0.18 \
psd-tools \
django-pylibmc \
django_simple_captcha==0.6.* \
djangosaml2==1.5.* \
pysaml2==7.2.* \
pycryptodome==3.16.* \
cffi==1.15.1 \
lxml \
python-ldap==3.4.3
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed versions? Who will be able to maintain this in the next few months?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Simply the instructions based on their documentations, not sure why they pinned the versions. It is however, the latest Seafile CE v11 version. They have moved to v12 and even v13 but v12 bare metal installation does not exist yet.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this strange project have no requirements.txt? I don't allow a script with such a number of fixed deps. As an example Django 4.2 has been EOL for 3 months and offers no protection.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not that I can see... Their Github's last release was 27 Feb 2024 too. It seems that most of their releases are simply through their website. I can try digging around and testing to see if updated deps will still allow the software to work.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Alright just tested it out, managed to get an installation up without any fixed versions after adding pkg-config to apt installation process. Will push the change I've made.

mkdir -p /home/seafile
sudo chown seafile: /home/seafile
sudo chown seafile: /opt/seafile
sudo su - seafile -c "wget -qc https://s3.eu-central-1.amazonaws.com/download.seadrive.org/seafile-server_11.0.13_x86-64.tar.gz"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed version? Who will be able to maintain this in the next few months?

Copy link
Contributor Author

@dave-yap dave-yap Feb 27, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Latest version as of now with no new bare-metal installation of the new version in sight... The Docker version has been released since November 2024 so no upgrading till when they decide to release the bare-metal version. It is already on v12.0.9 apparently too.

Removed sudo and tarball when cleaning up.
Copy link
Contributor

⚠️ The script ct/seafile.sh failed with the following message:


Failure in line 189 while executing command 'su - seafile -c bash /opt/seafile/seafile-server-latest/seafile.sh start'

Corrected source and remove comments
Move Python installation and dependencies down to Python block. Fix typos.
Copy link
Contributor

⚠️ The script ct/seafile.sh failed with the following message:


Failure in line 190 while executing command 'su - seafile -c bash /opt/seafile/seafile-server-latest/seafile.sh start'

Copy link
Contributor

⚠️ The script ct/seafile.sh failed with the following message:


Failure in line 57 while executing command 'apt-get install python3 python3-dev python3-setuptools python3-pip libmariadb-dev ldap-utils libldap2-dev libsasl2-dev'

Copy link
Contributor

⚠️ The script ct/seafile.sh failed with the following message:


Failure in line 191 while executing command 'su - seafile -c bash /opt/seafile/seafile-server-latest/seafile.sh start'

Copy link
Contributor

⚠️ The script ct/seafile.sh failed with the following message:


Failure in line 191 while executing command 'su - seafile -c bash /opt/seafile/seafile-server-latest/seafile.sh start'

@MickLesk MickLesk changed the title New Script: Seafile Seafile Feb 27, 2025
Copy link
Contributor

⚠️ The script ct/seafile.sh failed with the following message:


Failure in line 191 while executing command 'su - seafile -c bash /opt/seafile/seafile-server-latest/seafile.sh start'

1 similar comment
Copy link
Contributor

⚠️ The script ct/seafile.sh failed with the following message:


Failure in line 191 while executing command 'su - seafile -c bash /opt/seafile/seafile-server-latest/seafile.sh start'

Copy link
Contributor

⚠️ The script ct/seafile.sh failed with the following message:


Failure in line 192 while executing command 'su - seafile -c bash /opt/seafile/seafile-server-latest/seafile.sh start'

1 similar comment
Copy link
Contributor

⚠️ The script ct/seafile.sh failed with the following message:


Failure in line 192 while executing command 'su - seafile -c bash /opt/seafile/seafile-server-latest/seafile.sh start'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
general new script A change that adds a new script website A change to the website
Projects
Status: In PR
Development

Successfully merging this pull request may close these issues.

4 participants