Repository files navigation

• Remix Docs
• Customer Dashboard

First you'll need theVercel CLI:

npm i -g vercel

Before you can run the app in development, you need link this project to a new Vercel project on your account.

It is important that you use a new project. If you try to link this project to an existing project (like a Next.js site) you will have problems.

$ vercel link

Follow the prompts, and when its done you should be able to get started.

You will be running two processes during development when using Vercel as your server.

• Your Vercel server in one
• The Remix development server in another

# in one tab$ vercel dev# in another$ npm run dev

Open uphttp://localhost:3000 and you should be ready to go!

If you'd rather run everything in a single tab, you can look atconcurrently or similar tools to run both processes in one tab.

You will need to add your npmrc with your Remix token to your server's environment:

When you rannpm init remix, we probably created an npmrc in your home directory. Go take a look, it should look something like this:

//npm.remix.run/:_authToken={your-token}@remix-run:registry=https://npm.remix.run

If it looks something like that, then you can run these commands to add your npmrc from the command line:

$ vercel env add NPM_RC development<~/.npmrc$ vercel env add NPM_RC preview<~/.npmrc$ vercel env add NPM_RC production<~/.npmrc

You can also add this environment variable in your vercel project dashboard.

Once that's done you can deploy!

$ npm run build# preview deployment$ vercel# production deployment$ vercel --prod

For some reason the GitHub integration doesn't deploy the public folder. We're working with Vercel to figure this out.

For now,you can set up a GitHub action with this config from our friend @mcansh.