Run CI checks in Dokploy build
This commit is contained in:
parent
3d31dc1b55
commit
62544a1b97
4 changed files with 4 additions and 44 deletions
|
|
@ -66,9 +66,9 @@ Simply open [Lovable](https://lovable.dev/projects/5ee9d1e7-af25-47e9-ab4c-bdbca
|
|||
|
||||
### Forgejo and Dokploy
|
||||
|
||||
Pushes and pull requests targeting `main` are verified by the Forgejo Actions workflow in `.forgejo/workflows/ci.yml`. The production container is built from `Dockerfile` and serves the Vite output with NGINX, including React Router fallback handling.
|
||||
The production container is built from `Dockerfile` and serves the Vite output with NGINX, including React Router fallback handling. During the image build, `npm ci` installs the locked dependencies and `npm run ci` runs lint plus the production Vite build.
|
||||
|
||||
Dokploy is connected to the `Websites/interactives` Forgejo repository with autodeploy enabled. A successful push to `main` triggers a fresh Dockerfile build and replaces the running service only after the image has built successfully.
|
||||
Dokploy is connected to the `Websites/interactives` Forgejo repository with autodeploy enabled. A push to `main` triggers the Dockerfile CI checks and replaces the running service only after every build step succeeds.
|
||||
|
||||
## Can I connect a custom domain to my Lovable project?
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue