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

2
README.md
View File

@ -63,7 +63,7 @@ Interested in self-hosting Typebot on your server? Take a look at the [self-host
Copy `apps/viewer/.env.local.example` to `apps/viewer/.env.local` Copy `apps/viewer/.env.local.example` to `apps/viewer/.env.local`
Copy `packages/db/.env.example` to `packages/db/.env` Copy `packages/prisma/.env.example` to `packages/prisma/.env`
Check out the [Configuration guide](https://docs.typebot.io/self-hosting/configuration) if you want to enable more options Check out the [Configuration guide](https://docs.typebot.io/self-hosting/configuration) if you want to enable more options

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

@ -29,9 +29,9 @@ git clone git@github.com:<username>/typebot.io.git
```sh ```sh
cd typebot.io cd typebot.io
# check out the latest stable version or the one you want to use # 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 # 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/builder/.env.local.example apps/builder/.env.local
cp apps/viewer/.env.local.example apps/viewer/.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: To do so, follow these instructions:
1. Copy `packages/db/.env.example` to `packages/db/.env` and replace `DATABASE_URL` with a development branch 1. Copy `packages/prisma/.env.example` to `packages/prisma/.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` 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. 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 :::note

2
package.json
View File

@ -15,7 +15,7 @@
"build:viewer": "turbo run build --filter=viewer... && turbo run build:env --filter=viewer...", "build:viewer": "turbo run build --filter=viewer... && turbo run build:env --filter=viewer...",
"build:landing-page": "turbo run build --filter=landing-page... && turbo run build:env --filter=landing-page...", "build:landing-page": "turbo run build --filter=landing-page... && turbo run build:env --filter=landing-page...",
"build:apps": "turbo run build --filter=builder... --filter=viewer...", "build:apps": "turbo run build --filter=builder... --filter=viewer...",
"db:migrate": "cd packages/db && pnpm run db:migrate", "db:migrate": "cd packages/prisma && pnpm run db:migrate",
"generate-change-log": "git fetch --all && pnpx gitmoji-changelog" "generate-change-log": "git fetch --all && pnpx gitmoji-changelog"
}, },
"devDependencies": { "devDependencies": {

2
scripts/viewer-entrypoint.sh
View File

@ -2,6 +2,6 @@
ENVSH_ENV=./apps/viewer/.env.production ENVSH_OUTPUT=./apps/viewer/public/__env.js bash env.sh ENVSH_ENV=./apps/viewer/.env.production ENVSH_OUTPUT=./apps/viewer/public/__env.js bash env.sh
./node_modules/.bin/prisma generate --schema=packages/db/postgresql/schema.prisma; ./node_modules/.bin/prisma generate --schema=packages/prisma/postgresql/schema.prisma;
node apps/viewer/server.js; node apps/viewer/server.js;