danvics/openreader
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Make Docker image smaller

Browse source
This commit is contained in:
Richard Roberson 2025-02-26 00:32:30 -07:00
parent 9ae7c39f00
commit 33e48118bc
2 changed files with 5 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
Dockerfile
View file

@ -1,8 +1,8 @@
# Use Node.js slim image # Use Node.js slim image
FROM node:slim FROM node:current-alpine
# Add ffmpeg # Add ffmpeg using Alpine package manager
RUN apt-get update && apt-get install -y ffmpeg RUN apk add --no-cache ffmpeg
# Create app directory # Create app directory
WORKDIR /app WORKDIR /app

4
README.md
View file

@ -42,7 +42,7 @@ https://github.com/user-attachments/assets/262b9a01-c608-4fee-893c-9461dd48c99b
docker run --name openreader-webui \ docker run --name openreader-webui \
-p 3003:3003 \ -p 3003:3003 \
-v openreader_docstore:/app/docstore \ -v openreader_docstore:/app/docstore \
richardr1126/openreader-webui:latest richardr1126/openreader-webui:v0.2.2-alpine
``` ```
(Optionally): Set the TTS `API_BASE` URL and/or `API_KEY` to be default for all devices (Optionally): Set the TTS `API_BASE` URL and/or `API_KEY` to be default for all devices
@ -51,7 +51,7 @@ docker run --name openreader-webui \
-e API_BASE=http://host.docker.internal:8880/v1 \ -e API_BASE=http://host.docker.internal:8880/v1 \
-p 3003:3003 \ -p 3003:3003 \
-v openreader_docstore:/app/docstore \ -v openreader_docstore:/app/docstore \
richardr1126/openreader-webui:latest richardr1126/openreader-webui:v0.2.2-alpine
``` ```
> Requesting audio from the TTS API happens on the Next.js server not the client. So the base URL for the TTS API should be accessible and relative to the Next.js server. If it is in a Docker you may need to use `host.docker.internal` to access the host machine, instead of `localhost`. > Requesting audio from the TTS API happens on the Next.js server not the client. So the base URL for the TTS API should be accessible and relative to the Next.js server. If it is in a Docker you may need to use `host.docker.internal` to access the host machine, instead of `localhost`.