Running on Servd

[Please note, this page is a heavy work in progress]

---

Very little needs to be changed to run on Servd. But the below is how we like to roll...

Remove Async Queue

If you are running on Servd's Enhanced plan or above, there is no requirement for Async Queue as it's possible to run isolate tasks on a separate background thread (be aware of some caveats: https://servd.host/docs/background-task-isolation#troubleshooting-background-task-isolation).

Install Servd Assets and Helpers

Install Servd's Assets and Helpers plugin, this will be required to configure Volumes and other interactions with the platform.

Of course this step also requires configuring, or re-configuring, your Volumes to use Servd (unless you are already using AWS, Google Cloud or similar).

Configure Static Caching

For each environment in Servd, you can configure it to statically cache HTML responses. If turned on, the Exclusions paths should be carefully set up.

At a minimum, you'll want to include these in the Exclusions list:

• /admin (See cpTrigger)
• /actions (See actionTrigger)

If you haven't configured the Assets and Helpers plugin to inject CSRF tokens, be sure to include these paths as well:

• /setpassword (See setPasswordPath)
• /login (See loginPath)
• /logout (See slgoutPath)
• /verifyemail (See verifyEmailPath)