Skip to content

Commit

Permalink
fix: allow dockerfile to build (#3)
Browse files Browse the repository at this point in the history
  • Loading branch information
ticoombs authored Apr 14, 2024
1 parent 6ddf0cd commit 86c7fc6
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 3 deletions.
4 changes: 2 additions & 2 deletions Dockerfile
Original file line number Diff line number Diff line change
Expand Up @@ -14,11 +14,11 @@ RUN nvm install
RUN nvm use

COPY package*.json ./
RUN npm ci --omit=dev
RUN npm ci --omit=dev --ignore-scripts

COPY . .
ENV NEXT_TELEMETRY_DISABLED=1
RUN npm run build

EXPOSE 3000
CMD ["/root/.nvm/nvm-exec", "npm", "run", "start"]
CMD ["/root/.nvm/nvm-exec", "npm", "run", "start"]
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -53,6 +53,6 @@ LEMMY_BACKEND=https://<your lemmy api> LEMMY_UI_NEXT_PUBLIC_URL=https://<url whe

At this point, you will have lemmy-ui-next listening on 0.0.0.0:3000, and you can point your nginx or any other reverse proxy at it. You can improve performance at least a little by pointing lemmy-ui-next directly at your Lemmy backend process. For examplem if running on the same host, you can use something like `LEMMY_BACKEND=https://localhost:8536`.

*Sample systemd service file will be coming soon. Alternatively, a sample Dockerfile will also be provided. It's on the to-do list 😅.*
*Sample systemd service file will be coming soon. It's on the to-do list 😅. Alternatively, a sample Dockerfile is provided.*


0 comments on commit 86c7fc6

Please sign in to comment.