Server Paths and Locations

Package Config Locations

When you provision a server using SpinupWP we use best practices to set up and install all of the required software packages your server will need to run WordPress properly. This includes installing packages (such as PHP, Nginx, MySQL/MariaDB etc.) in default locations and not using customized packages as some other hosts might do. This means that package configs should always be in their default locations.

PHP

{php_version} will be the PHP version number you chose to install when you provisioned your server (e.g. “7.2”).

/etc/php/{php_version}/fpm/php.ini

Each site will have it’s own PHP pool:

/etc/php/{php_version}/fpm/pool.d/{site_user}.conf

Nginx

/etc/nginx/nginx.conf

MySQL/MariaDB

/etc/mysql/my.cnf

Site Paths

When you create a new site in SpinupWP the domain name will be used as a folder name and created in the /sites directory. For example, if you created a site with the domain name example.com the site path would be:

/sites/example.com

Inside the site directory, SpinupWP creates two directories that serve different purposes:

/sites/{domain}/logs

The logs directory is where PHP and Nginx will store any log files for this site. We also move the WordPress debug.log file to this directory and enable log rotation on all log files.

/sites/{domain}/files

The files directory is where we store your WordPress site files. If your public folder is set to “/” then this directory will be your web root. If you changed your public folder to “/public” the absolute path to that folder would be:

/sites/{domain}/files/public

If you’ve enabled page caching, the following directory will also be created to store Nginx cache files:

/cache/{domain}

Ready to give SpinupWP a try?

Not sure if SpinupWP is the right fit for you? Send us an email at sudo@spinupwp.com and we’ll give you our no-BS opinion.