Skip to content
Snippets Groups Projects
Commit c0625c5c authored by timothycarambat's avatar timothycarambat
Browse files

update baremetal doc

parent 331d3741
No related branches found
No related tags found
No related merge requests found
...@@ -30,6 +30,13 @@ Here you can find the scripts and known working process to run AnythingLLM outsi ...@@ -30,6 +30,13 @@ Here you can find the scripts and known working process to run AnythingLLM outsi
STORAGE_DIR="/your/absolute/path/to/server/.env" STORAGE_DIR="/your/absolute/path/to/server/.env"
``` ```
5. Edit the `frontend/.env` file for the `VITE_BASE_API` to now be set to `/api`. This is documented in the .env for which one you should use.
```
# VITE_API_BASE='http://localhost:3001/api' # Use this URL when developing locally
# VITE_API_BASE="https://$CODESPACE_NAME-3001.$GITHUB_CODESPACES_PORT_FORWARDING_DOMAIN/api" # for Github Codespaces
VITE_API_BASE='/api' # Use this URL deploying on non-localhost address OR in docker.
```
## To start the application ## To start the application
AnythingLLM is comprised of three main sections. The `frontend`, `server`, and `collector`. When running in production you will be running `server` and `collector` on two different processes, with a build step for compilation of the frontend. AnythingLLM is comprised of three main sections. The `frontend`, `server`, and `collector`. When running in production you will be running `server` and `collector` on two different processes, with a build step for compilation of the frontend.
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment