servd

Documentation

Documentation > Assets >

Upgrading to Asset Platform V3

Upgrading to the Servd Asset Platform V3 is a simple process but requires a small amount of preparation.

Important notes #

  • The URLs for your assets will change to use our new CDN and transform functions. If you have hard coded any asset URLs anywhere, they may need to be updated.
  • Asset URLs now have the project name included in the domain instead of the path. You may need to adjust any Custom URL Patterns set in the Servd Plugin's settings to remove this.
  • If you are using a proxy in front of our Asset Platform, such as a Cloudflare Worker, it will need to be updated to point to the new Asset Platform URLs.
  • The Asset Platform V3 supports custom domains for transforms and files. Using a proxy to achieve this is no longer required.
  • After the upgrade has completed we'll keep all of the existing files intact on the old Asset Platform for 30 days, giving you time to get everything updated and tested before old asset URLs will be deactivated, but any newly uploaded files after the Upgrade will only exist on the new Asset Platform.
  • If you need any help with the migration, just ask! We're happy to help.

  1. Ensure your project has been updated to use the Servd Plugin V3.4.0 (Craft 4) or V2.9.0 (Craft 3).

  2. Build a new bundle containing the updated plugin and roll out to all of your environments. This won't change anything immediately.

  3. In the Servd dashboard, visit your project's Assets page.

  4. Under the "Upgrade to Asset Platform V3" section, click the "Upgrade Now" button.

    The migration process might take a few minutes to complete if you have lots of files.

  5. Once done, visit each of your project's environments, starting with Production, and clear Craft's data cache.

    The Servd plugin will now automatically detect that the upgrade has taken place and update your file and image URLs appropriately.

  6. (Optional) You may wish to configure custom URLs for your assets at this point. If so, you can check how to do that here.

  7. If your project is using any form of caching (static, blitz or {% cache %} tags) clear them to refresh all of your project's HTML with the updated asset URLs. You might want to wait for a quiet traffic period to perform this step if your project relies on caching to handle its normal load.

  8. You're fully upgraded!