This guide describes the steps required to have Pydio Cells running on macOS.
You can skip this step if you already have a database.
You can use either MySQL (>= 5.6) or MariaDB as your Database Management System. Both are available in Homebrew.
brew install mysql
brew install mariadb
Download Pydio Cells Binary on your server/machine using the following command:
wget https://download.pydio.com/pub/cells/release/1.2.5/darwin-amd64/cells chmod +x cells
Port 80 & 443
You can only use these ports if you are connected as root.
By default, Apache is running on macOS, so you need to ensure that it - or no other webservers - is bound to these ports.
To stop the default Apache, you can use:
sudo apachectl stop
To prevent Apache from starting during launch, you may use:
sudo launchctl unload -w /System/Library/LaunchDaemons/org.apache.httpd.plist
In this section, we assume you have installed MySql server. Adapt the following steps to your current installation.
# Go to mysql mode sudo mysql -u root # Create new user and set password CREATE USER 'pydio'@'localhost' IDENTIFIED BY 'your password goes here';
Starting with Pydio
First, give execution rights to the binary. For instance, you can use
sudo chmod u+x <binary>.
Then, to launch the installer, type:
Before you start installing here's two of the most important parameters that you need to understand:
CELLS_BIND : address where the application http server is bound to. It MUST contain a server name and a port. CELLS_EXTERNAL : url the end user will use to connect to the application. Example: If you want your application to run on the localhost at port 8080 and use the url mycells.mypydio.com, then set CELLS_BIND to localhost:8080 and CELLS_EXTERNAL to mycells.mypydio.com After the install is successfully done, if you ever have to stop Pydio Cells and want to run it again just run:
You can refer to this page to get more details on the installation process.
After the install is successfully done, if you ever have to stop Pydio Cells and want to run it again, just run:
- The database service might not be started, you can look at its status using :
brew services listand then
brew services start mysqlif needed.
- You can look at the webserver's error file located in