This is somewhat possible without symlinks.

We are using relative paths /home/ploi/../../mnt/<somevolume>/sitename. Not ideal, but it works. In the nginx config we then strip the path to /mnt/sitename.

Hey!

In my suggested workaround you move and symlink the Ploi folder only once after provisioning. It works well and is all you need to do but it would be nice if you could do this from the UI and have Ploi monitoring keep an eye out on disk usage.

I'm not sure what you're doing. Can you explain to me the steps your taking. Happy to learn!

I think Ploi just monitors the disk space of the system disk. Maybe we can have a setting to set which volume we would like to track. Maybe even multiple volumes. Or maybe just track whatever volume is mounted to /home.

Any news on this - i dont know how to install to a different volume - is there a guide?

If you want to move a single site to a mounted volume then you can do the following:

Lets assume you have an a site called example.com and it lives in /home/ploi/example.com and lets also assume you have a mounted volume under /mnt/ploi

You can do the following:

mv /home/ploi/example.com /mnt/ploi/
ln -s /mnt/ploi/example.com /home/ploi/example.com

I haven't found any issues with this but one thing to note is that file backups will only backup the symlink. The workaround is to append "/." to the "Path to backup", e.g. /home/ploi/example.com/.

Even though this works it would be nice to have this functionality built into Ploi.

I would also really like to see this feature in Ploi UI, so that we can easily move a site to a mounted volume.

Does the symlink solution work when the laravel "no-downtime" option is enabled? I assume it's fine to just mount the example.com-deploy folder in that case, to create a two symlink chain.

Cause the default the folder structure already symlinks: example.com -> example.com-deploy/example.com/...... example.com-deploy