A word from the core team...

Since more than ten years, Pydio is commited to Open Source. Starting with AjaXplorer, then Pydio and now Pydio Cells, we have been happily publishing our code on Github under OSI-compatible licenses. We always do our best to publish a clean, documented code as well as up-to-date administrative and developer guides, but of course some time you may hit a bug or an unexpected behaviour. Don't panic, there are many places to communicate with the core team, and with the community!

First, please read our community guidelines, that are described inside the CODE_OF_CONDUCT document inside the Github repositories. To make it short, we embrace openness, we accept constructive criticism but of course we will not tolerate harassing or abusive language. Also, check the informations below to make sure to post at the right place, thus avoiding wasting your time and making sure to have a proper answer to your questions!

Thank you in behalf of the core team
Charles - Project Founder

Transparent Background: 

Installing Pydio Cells

Being a pre-compiled binary, deploying Pydio Cells on any server is (really) a piece of cake. Below is a summary of what has to be done:

Download the binary for your server OS, place it under e.g. /home/pydio and make it executable with

chmod +x cells

Prepare access to a MySQL database.

Run ./cell install command and follow the steps either via command line or inside a browser

Restart cells using ./cells start

You should be good to go! If not (os-specific issues, using proxies, etc..) make sure to check the Administration Guide for more complete instructions.

Using Docker Container

We provide an easy to use Docker container to deploy Pydio Cells even more easily. It is published on the Docker Hub as pydio/cells. Basically, it all starts with: 

docker run -d -p 8080:8080 pydio/cells

The hub page gives advanced informat about how to use it, and a sample docker-compose file to attach a DB container as well.

Building from source

Cells has a vendoring approach allowing the build from sources through simple steps.

Make sure to have a properly configured Go environment set up, then go get github.com/pydio/cells and use the various commands of the Makefile to build pydio (generally make dev).

Transparent Background: 

Pre-built binaries vs. Sources

Depending on what you need, you can use our pre-built binaries / archives or grab the source and built the software by yourself!

Transparent Background: 

Stable Releases

For those who don't want to rebuild from scratch...

Get Sources

All our sources are published under the github pydio organisation. Star the repositories to be notified and to promote Pydio!

Continuous Integration

Our CI/CD toolchain automatically builds and tests our packages each time a commit is pushed to Github.

This builds are available at the following addresses:

Be aware that these build may be unstable and should not be used in production!

Transparent Background: 

Contributing

Fork Pydio on Github and help us improve the code, the translation or even the documentations!

Transparent Background: 
CORE, PLUGINS & LANGUAGES

As an open source project, we strongly value your contribution. If you are used to Github standard mechanisms (fork / pull requests), you will feel at home very quickly. The developer docs are definitely a good start.

In any case please first read our contribution guidelines and sign the Contributor License Agreement.

IMPROVE DOCUMENTATION

Our docs are open-source too ! They are published under the Creative Commons v3 License. To contribute, please use the standard github Pull Requests mechanism, and help us make them more accurate.

All the guides and How-to's are published in our public repositories, starting with pydio-doc-*

Transparent Background: