blsmedia/bot
2
0
Fork 0
Code Activity

✏️ Fix old packages/db paths in documentation

Browse Source
This commit is contained in:
Baptiste Arnaud
2023-03-20 07:38:47 +01:00
parent b3e5887420
commit 16c261a8a5
5 changed files with 7 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
apps/docs/docs/self-hosting/manual.md
View File

@@ -29,9 +29,9 @@ git clone git@github.com:<username>/typebot.io.git
```sh
cd typebot.io
# check out the latest stable version or the one you want to use
git checkout v2.9.1
git checkout latest
# copy the example env file
cp packages/db/.env.example packages/db/.env
cp packages/prisma/.env.example packages/prisma/.env
cp apps/builder/.env.local.example apps/builder/.env.local
cp apps/viewer/.env.local.example apps/viewer/.env.local
```

4
apps/docs/docs/self-hosting/planetscale.md
View File

@@ -4,8 +4,8 @@ Typebot is also pluggable to a Planetscale database. But it means, you'll need t
To do so, follow these instructions:
1. Copy `packages/db/.env.example` to `packages/db/.env` and replace `DATABASE_URL` with a development branch
2. From the `packages/db` directory, run a the db push command: `pnpm run db:push`
1. Copy `packages/prisma/.env.example` to `packages/prisma/.env` and replace `DATABASE_URL` with a development branch
2. From the `packages/prisma` directory, run a the db push command: `pnpm run db:push`
3. Then, in Planetscale dashboard, or using their CLI, you can create a new deploy request from this development branch to your production branch.
:::note