Comment on page
Deploy Frontity using Vercel
In their own words : Vercel is a cloud platform for static sites and Serverless Functions that fits perfectly with your workflow. It enables developers to host Jamstack sites and web services that deploy instantly, scale automatically, and requires no supervision, all with no configuration.
We strongly recommend this service as it is serverless, cheap, includes CDN, and really easy to set up.
It also supports the cache technique stale-while-revalidate (which they call Serverless Pre-Rendering). This is a powerful way to improve your site speed.
> npx vercel login
Deploying to Vercel is really easy and all the required configuration for Frontity projects is automatically set for you via a
vercel.json file.So, to deploy your Frontity site under a Vercel domain you have to:
- 1.
- 3.
{
"version": 2,
"builds": [
{
"src": "package.json",
"use": "@frontity/now"
}
]
}
@frontity/now is a Frontity builder created especifically for Vercel. It encapsulates all the actions that need to be triggered on Vercel servers when deploying a Frontity project> npx vercel
You should get something like this
Vercel CLI 19.2.0
? Set up and deploy “~/PROJECTS/2020/FRONTITY/DEMOS/my-frontity-project”? [Y/n] y
? Which scope do you want to deploy to? myVercelScope
? Link to existing project? [y/N] n
? What’s your project’s name? my-frontity-project
? In which directory is your code located? ./
🔗 Linked to vercel-username/head-tags (created .vercel)
🔍 Inspect: https://vercel.com/vercel-username/my-frontity-project/lofg8n03c [2s]
✅ Production: https://my-frontity-project.vercel.app [copied to clipboard] [1m]
Vercel will assign you a domain (something like your-project-name.vercel.app) that that will allow you to check your site online.
From the above deployment example we got the following URL's:
- Live URL:
https://my-frontity-project.vercel.app→ Our temporary URL assigned automatically by Vercel, We can check (and share) our site online from this URL - Inspect:
https://vercel.com/vercel-username/my-frontity-project/settings→ Here we can check the status of our site and check the logs among other things - Project Settings:
https://vercel.com/vercel-username/my-frontity-project/settings→ Here we can change domain and build settings among other things
To deploy your site in Vercel under a custom domain you have to:
By visiting the project settings URL provided in our previous deployment (
https://vercel.com/vercel-username/my-frontity-project/settings in our example above) we can set a custom domain.
Add it, and you will be provided with a set of nameservers that you can use in your domain provider's configuration to point your custom domain to the Vercel nameservers.
vercel nameservers
A subdomain can be used to separate your WordPress and Frontity deployments. They can be created within the Vercel dashboard under the domains section.
To setup a subdomain for your WordPress source, simply select your desired domain from the list and add a new DNS Record with type A and the IP address of your WordPress server.
You need to set Vercel nameservers as custom DNS of your custom domain from your domain provider site.
If you don't know how to do this, contact your domain provider (GoDaddy, CloudFlare, etc)
Finally, deploy Frontity using this command (from the root of your project):
> npx vercel --prod
You should get something like this
⬢ my-frontity-project npx vercel --prod
🔍 Inspect: https://vercel.com/vercel-username/my-frontity-project/9ue4zsq9n [2s]
✅ Production: https://mycustomtomain.com [copied to clipboard] [4s]
This will create a deployment and assign it to your real site URL.
Vercel now forces all apps to be served over HTTPS. You therefore need to ensure that your WordPress site has a SSL certificate and that you connect to your WordPress API endpoint using HTTPS rather than HTTP.
{
"name": "@frontity/wp-source",
"state": {
"source": {
"url": "https://your-wordpress-blog-url/",
}
}
},
...
The effect of using a HTTP only connection on a Frontity project deployed on Vercel will result in navigation links not working and getting stuck in the
data.isFetching state (although apparently working on the local dev machine). The reason is that Frontity won't be able to fetch the content from the WordPress backend over HTTP on a pure HTTPS site.Last modified 2yr ago