#SEAFILE ON RASPBERRY PI INSTALL#
#SEAFILE ON RASPBERRY PI MANUAL#
#SEAFILE ON RASPBERRY PI ARCHIVE#
#SEAFILE ON RASPBERRY PI CODE#

ccnet-server, seafile-server, and seahub would all have a v6.0.1-sever tag.

Seafile manages the releases in tags on github.Īssume we are packaging for seafile server 6.0.1, then the tags are:

Then run a build-server.py script to build the server package from the source tarballs.įetch git tags and prepare source tarballs ¶.

First, fetch the tags of each projects, and make a soruce tarball for each of them.

To build seafile server, there are four sub projects involved:

#SEAFILE ON RASPBERRY PI INSTALL#

gz pip install - t ~/ dev / seahub_thirdpart / / tmp / openpyxl - 2.3. gz pip install - t ~/ dev / seahub_thirdpart / / tmp / et_xmlfile - 1.0. zip pip install - t ~/ dev / seahub_thirdpart / / tmp / jdcal - 1.2. zip pip install - t ~/ dev / seahub_thirdpart / / tmp / django_constance.

#SEAFILE ON RASPBERRY PI ARCHIVE#

com / haiwen / django - constance / archive / bde7f7c. gz pip install - t ~/ dev / seahub_thirdpart / / tmp / django - picklefield - 0.3.

gz pip install - t ~/ dev / seahub_thirdpart / / tmp / six - 1.9. gz pip install - t ~/ dev / seahub_thirdpart / / tmp / python - dateutil - 1.5. gz pip install - t ~/ dev / seahub_thirdpart / / tmp / chardet - 2.3. gz pip install - t ~/ dev / seahub_thirdpart / / tmp / flup - 1.0. gz pip install - t ~/ dev / seahub_thirdpart / / tmp / gunicorn - 19.4. gz pip install - t ~/ dev / seahub_thirdpart / / tmp / django - post_office - 2.0. gz pip install - t ~/ dev / seahub_thirdpart / / tmp / jsonfield - 1.0.

gz pip install - t ~/ dev / seahub_thirdpart / / tmp / django_compressor - 1.4. gz pip install - t ~/ dev / seahub_thirdpart / / tmp / djangorestframework - 3.3. gz pip install - t ~/ dev / seahub_thirdpart / / tmp / django - statici18n - 1.1. gz pip install - t ~/ dev / seahub_thirdpart / / tmp / Django - 1.8. pip install - t ~/ dev / seahub_thirdpart / / tmp / pytz - 2016.1. With a limit of 100 MiB they can safely upload files of any size.įinally, make sure your seafile.Fetch git tags and prepare source tarballsĬopy the source tar balls to the same folderĬd ~/ dev / seahub_thirdpart export PYTHONPATH =. Client uploads are only partly effected by this limit. Optionally, the value can also be set to 0 to disable this feature. It is recommended to syncronize the value of client_max_body_size with the parameter max_upload_size in section of nf.

#SEAFILE ON RASPBERRY PI CODE#

Uploading larger files will result in an error message HTTP error code 413 ('Request Entity Too Large'). The default value for client_max_body_size is 1M. Maximum allowed size of the client request body (client_max_body_size).Proxy pass for location /seafhttp - if seaf-server is configured to start on a different port than 8082.Proxy pass for location / - if Seahub is configured to start on a different port than 8000.Server listening port (listen) - if Seafile server should be available on a non-standard port.Optional customizable options in the nf are: The following options must be modified in the CONF file: Log_format seafileformat ' $http_x_forwarded_for $remote_addr ' $request' $status $body_bytes_sent ' $http_referer' ' $http_user_agent' $upstream_response_time' server

Install Nginx using the package repositories: If your setup differs from thes requirements, adjust the following instructions accordingly.

A host name points at the IP address of the server and the server is available on port 80.

#SEAFILE ON RASPBERRY PI MANUAL#

Seafile Server Community Edition/Professional Edition was setup according to the instructions in this manual (i.e., a dedicated user seafile exists and all Seafile files are stored in /opt/seafile).These instructions assume the following requirements: The configuration of Seafile behind Nginx as a reverse proxy is demonstrated using the sample host name. Nginx, a popular and resource-friendly HTTP server and reverse proxy, is a good option. A reverse proxy increases the performance of Seafile and allows the encryption of inbound and outbound traffic.įor production use, a setup with a reverse proxy and HTTPS encryption is a MUST. Both components of Seafile Server, Seahub and seaf-server, can be configured to run behind a reverse proxy.

Seafile on raspberry pi