UNPKG

@saiforceone/dirt-cli

Version:

Official CLI Utility for the D.I.R.T stack

github.com/saiforceone/dirt-cli

saiforceone/dirt-cli

46 lines (35 loc) • 2.09 kB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
``` ______ ___________ _____ _____ _ _____ | _ \_ _| ___ \_ _| / __ \| | |_ _| | | | | | | | |_/ / | | | / \/| | | | | | | | | | | / | | | | | | | | | |/ / _| |_| |\ \ | | | \__/\| |_____| |_ |___/ \___/\_| \_| \_/ \____/\_____/\___/ ``` If you're reading this, it means you chose the __Vercel__ deployment option during the scaffolding process. Awesome! Now, let's make sure we can get everything set up as required. # A few things to consider - This is an __Early__ version of this document so things might just change - This is meant as a starting point - We've broken some rules to serve static assets from Django (only applies to Vercel) - There are two files to pay attention to `vercel.json` and `build_vercel.sh` - -- # Prerequisites Before we get started with the setup for deploying to __Vercel__, we will need to make sure we have a few things in place - An account on Vercel (Don't have one? [Click Here](https://vercel.com/)) - A repo set for your project already set up # Important files - __vercel.json:__ `This file contains the configuration that Vercel will use when deploying your project.` - __build_vercel.sh:__ `This file contains the commands that should be run during the deployment process on Vercel` # Deploying to Vercel This section covers the basics of what you need to know in order to deploy a D.I.R.T Stack web application to Vercel. - Import your project's repo into Vercel [How to import repo to Vercel](https://vercel.com/docs/concepts/deployments/git) - Configure project settings ## Configuration Vercel Project Settings - Set framework preset to `Vite` - Enable the override for `Build Command` and set the value to `npm run build-assets` - Enable the override for `Output Directory` and set the value to `static/dist` - Ensure the checkbox for `Include source files outside of the Root Directory in the Build Step.` is checked - Ensure the NodeJs version is set to `18.x` or the current stable version That should more or less do it. At this point, you should be able to deploy your project.