Seafile Community Manual
I am happy to announce that the Seafile Community Manual was just released today (27.10.2018). It is now searchable via your favourite search engine as well.
Why another manual?
The idea of this community driven manual is to make it possible for new and existing Seafile users to get an easy start and be able to mantain their Seafile server. Another goal is to provide somewhat of a structure on each step required to reach a certain goal rather than a collection of information spread over a confusing and hard to read server manual.
Several people have tried in the past to motivate the Seafile devs to restructure the original manual but failed. Since Seafile CE is OpenSource we don’t have to wait and can create a manual of our own.
This manual might not contain all information that the original manual provides but it aims to provide what is necessary to keep Seafile running as best-practice setup.
The manual will only be as good as it’s contributors. It is not possible to mantain it with one or two contributors, we need a bunch of people from the community to do that.
I know that there are quiet a few people that invested their time into a manual of their own. It would be really nice if those people contributed their time and knowledge into the CE manual, even if it’s in small steps.
We are also looking for people that help maintain, check and approve Github pull requests as well. If you consider yourself a Seafile server advanced admin please let @DerDanilo know so that he can provide you with write access to the Github repository.
Please refrain from any discussion about Github or readthedocs in this threat as this is about the manual and not about personal oppinion. Those services were selected as they are free and support OpenSource projects.
How to contribute?
It helps a lot if you know how to use GIT or at least know your way arround usage of the Github GUI.
It is important that you issue “commits” for every page that you edit. This makes it easier to approve or deny certain things when double checking.
Please try to avoid huge pull requests as it’s generally harder to read and requires more time to go through.
Small steps are just fine.
This forum thread is not the right medium to find the (possible) tons of typos, broken links and logical erros.
The contributors of the manual are greatful for your effort of reporting the issue properly and can fix it soon.
Previous posts concerning this manual: