#SEAFILE ON RASPBERRY PI UPDATE#

For complete control, you can buy a server and manage it yourself. Self-hosting your cloud means owning the servers you use. The company providing the service has a bunch of servers that they maintain in-house and offer remote access to the servers for a recurring fee. Whether it’s a cloud computing service like SaaS or PaaS, or cloud storage, they work the same way.

comment out or delete the db-section inside the Does it Mean to Self-Host Cloud Storage?įirst, you need to understand how cloud services work.

However, if you already have a mysql database in place, it may make more sense to use that instance for seafile. Therefore, the most straightforward option is taken here, which is to ship the application database with Seafile and run it in another container alongside seafile. The idea behind this project is to have Seafile set up as simple as possible. Also, you would have to create a seafile/haiwen/seafile-server-latest symlink to seafile/haiwen/seafile-server yourself. ⚠️ Notice: If you have your project up and running with either build or pull method, you can't switch to the other one, unless you know what you are doing! At the very least, you would have to back up your data, then rename your seafile/haiwen folder to say seafile/haiwen-old/ and after the switch, move your old config ( seafile/haiwen-old/ccnet, seafile/haiwen-old/conf, etc.) back to the new seafile/haiwen folder. The resulting docker image will be ~1 GB in size. This will not take as long, also you don't need as much RAM. In that case, a precompiled seafile server will be downloaded from the official Github repo ( Seafile on Raspberry Pi) and you don't need to compile seafile on your hardware. If you want to avoid waiting that long, you can also use BUILD_METHOD=pull (see also below). Also, the resulting docker image will be only about ~300 MB in size, because we can use alpine as a base image. However, can can in theory enjoy the latest version of seafile, even if there is no official ARM-version now. Note that building seafile may take ~1h (~30 min. env file, or pull a precompiled version from the official Github repo. You can either compile the whole seafile server yourself, using BUILD_METHOD=build in your. Then you just follow the instructions to do the configuration, incorporating your old config from configuration.old into.

#SEAFILE ON RASPBERRY PI UPDATE#

Afterwards, git pull and update the repo to the latest commit. In that case, just rename your docker-compose.yml to say configuration.old. If you want to switch to the new method, you are likely some commits behind the master branch. env-file, the configuration gets much easier and you wont have to update variables in two places. Previously, the configuration for this project was done in the docker-compose.yml. env and adapt everything to your needs (The least thing you probably want to do is change the server name). Note the instructions and hints inside the.Otherwise you will have to put sudo in front of every docker command. It's heavily recommended to add your user to the docker group, Specifically, this setup has been tested on: Note: If your Hardware doesn't have enough RAM, you won't be able toīuild seafile and thus cannot enjoy the latest version. Recommended: >= 30 GB of disk space per user.>= 1 GB of RAM, Recommended: ~= 4 GB of RAM (needed for compilation of lxml).CPU with ARMv8 64-bit architecture (e.g.Note: Building and packaging is done seperately, inside the build image.

Seafile is the main application, built and packaged using the procedure described in the official manual.

Nginx acts as a reverse proxy for the main seafile server w/ seahub. We use three main docker images to separate the different components from each other. The Seafile Maintainers provide a dockerized setup themselves ( ), but that one is not compatible with ARM devices. This is a set of scripts and Dockerfiles for setting up Seafile in docker.

Seafile on raspberry pi