kasun/Vaessl
1
0
Fork 0
Code Issues 8 Pull Requests Actions Packages Projects 3 Releases Wiki Activity

setup-frontend-environment #21

Merged
kasun merged 5 commits from setup-frontend-environment into main 2026-03-24 04:21:47 +01:00
Conversation 0 Commits 5 Files Changed 23
+5 -5
3 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Showing only changes of commit 6d9942d532 - Show all commits
docs/01-Planning/02-Product-and-technical-vision.md
+2 -2
View File
@@ -6,7 +6,7 @@ Vaessl is an AI-powered bridge designed to connect physical reality to digital m
# Technical requirements & stack
## Frontend
- Framework: Next.js (React)
- Framework: Vite (React)
- Styling: Tailwind CSS + SCSS
@@ -52,7 +52,7 @@ The image processing is the heart of Vaessl's "bridge" functionality. It ensures
## Deployment
Vaessl is deployed via Docker Compose for high portability.
- Container 1: Next.js (Web UI)
- Container 1: Vite (Web UI)
- Container 2: Spring Boot
- Container 3: PostgreSQL + pgvector
- Container 4: LiteLLM
docs/01-Planning/03-Project-goals.md
+2 -2
View File
@@ -29,12 +29,12 @@ Vaessl is intended to be a useful tool for the public, specifically those utiliz
# Short-Term Roadmap & Milestones
- Phase 1: Foundation (Current)
* Deploy the core infrastructure (PostgreSQL + pgvector, LiteLLM, Spring Boot Skeleton, Next.Js frontend).
* Deploy the core infrastructure (PostgreSQL + pgvector, LiteLLM, Spring Boot Skeleton, Vite frontend).
* Establish the bridge between the Vaessl backend and a demo Homebox instance.
- Phase 2: The Processing Pipeline
* Implement the image processing workflow: Upload $\rightarrow$ AI analysis $\rightarrow$ staging Table.
* Develop the Next.js interface for data refinement and verification.
* Develop the Vite interface for data refinement and verification.
- Phase 3: Semantic Search & Demo
* Integrate Spring AI for embedding generation.
docs/02-Preparation/01-code-server-adjustments.md
+1 -1
View File
@@ -1,6 +1,6 @@
**Vaessl: code-server adjustments**
Before developing on code-server I configure a Dockerfile to install all packages needed for Spring Boot, Java and Next.js. I install openjdk, npm, nodejs and yarn and set the environment variables for Java. Since the linuxserver code-server image doesn't come with root access for its default user abc out of the box every privileged action will be baked in here:
Before developing on code-server I configure a Dockerfile to install all packages needed for Spring Boot, Java and Vite. I install openjdk, npm, nodejs and yarn and set the environment variables for Java. Since the linuxserver code-server image doesn't come with root access for its default user abc out of the box every privileged action will be baked in here:
```
FROM lscr.io/linuxserver/code-server:latest