beanbeanjuice Posts - Answer Overflow

beanbeanjuice

Explore posts from servers

PPrisma HHomarr

Posts Comments

HHomarr

•Created by beanbeanjuice on 12/18/2024 in #💬・get-help

Tiles Not Saving Properly in Beta

I've attached a video demonstrating, but essentially when I save tiles, and reload, it messes it up a bit.

9 replies

HHomarr

•Created by beanbeanjuice on 12/18/2024 in #💬・get-help

Dash. Integration Not Working in Beta

21 replies

PPrisma

•Created by beanbeanjuice on 12/10/2024 in #help-and-questions

Previously Working Dockerfile No Longer Works

FROM node:lts-alpine AS base

# Install dependencies only when needed
FROM base AS deps
# Check https://github.com/nodejs/docker-node/tree/b4117f9333da4138b03a546ec926ef50a31506c3#nodealpine to understand why libc6-compat might be needed.
RUN apk add --no-cache libc6-compat
WORKDIR /app

# Install dependencies based on the preferred package manager
COPY package.json yarn.lock* package-lock.json* pnpm-lock.yaml* .npmrc* ./
RUN \
  if [ -f yarn.lock ]; then yarn --frozen-lockfile; \
  elif [ -f package-lock.json ]; then npm ci; \
  elif [ -f pnpm-lock.yaml ]; then corepack enable pnpm && pnpm i --frozen-lockfile; \
  else echo "Lockfile not found." && exit 1; \
  fi


# Rebuild the source code only when needed
FROM base AS builder
WORKDIR /app
COPY --from=deps /app/node_modules ./node_modules
COPY . .

# Next.js collects completely anonymous telemetry data about general usage.
# Learn more here: https://nextjs.org/telemetry
# Uncomment the following line in case you want to disable telemetry during the build.
# ENV NEXT_TELEMETRY_DISABLED=1

RUN npx prisma generate

RUN \
  if [ -f yarn.lock ]; then yarn run build; \
  elif [ -f package-lock.json ]; then npm run build; \
  elif [ -f pnpm-lock.yaml ]; then corepack enable pnpm && pnpm run build; \
  else echo "Lockfile not found." && exit 1; \
  fi

# Production image, copy all the files and run next
FROM base AS runner
WORKDIR /app

ENV NODE_ENV=production
# Uncomment the following line in case you want to disable telemetry during runtime.
# ENV NEXT_TELEMETRY_DISABLED=1

RUN addgroup --system --gid 1001 nodejs
RUN adduser --system --uid 1001 nextjs

COPY --from=builder /app/public ./public

# Automatically leverage output traces to reduce image size
# https://nextjs.org/docs/advanced-features/output-file-tracing
COPY --from=builder --chown=nextjs:nodejs /app/.next/standalone ./
COPY --from=builder --chown=nextjs:nodejs /app/.next/static ./.next/static
COPY --chown=nextjs:nodejs prisma ./prisma/

USER nextjs

EXPOSE 3000

ENV PORT=3000

# server.js is created by next build from the standalone output
# https://nextjs.org/docs/pages/api-reference/next-config-js/output
ENV HOSTNAME="0.0.0.0"
CMD ["sh", "-c", "npx prisma migrate deploy && npm run seed && node server.js"]

FROM node:lts-alpine AS base

# Install dependencies only when needed
FROM base AS deps
# Check https://github.com/nodejs/docker-node/tree/b4117f9333da4138b03a546ec926ef50a31506c3#nodealpine to understand why libc6-compat might be needed.
RUN apk add --no-cache libc6-compat
WORKDIR /app

# Install dependencies based on the preferred package manager
COPY package.json yarn.lock* package-lock.json* pnpm-lock.yaml* .npmrc* ./
RUN \
  if [ -f yarn.lock ]; then yarn --frozen-lockfile; \
  elif [ -f package-lock.json ]; then npm ci; \
  elif [ -f pnpm-lock.yaml ]; then corepack enable pnpm && pnpm i --frozen-lockfile; \
  else echo "Lockfile not found." && exit 1; \
  fi


# Rebuild the source code only when needed
FROM base AS builder
WORKDIR /app
COPY --from=deps /app/node_modules ./node_modules
COPY . .

# Next.js collects completely anonymous telemetry data about general usage.
# Learn more here: https://nextjs.org/telemetry
# Uncomment the following line in case you want to disable telemetry during the build.
# ENV NEXT_TELEMETRY_DISABLED=1

RUN npx prisma generate

RUN \
  if [ -f yarn.lock ]; then yarn run build; \
  elif [ -f package-lock.json ]; then npm run build; \
  elif [ -f pnpm-lock.yaml ]; then corepack enable pnpm && pnpm run build; \
  else echo "Lockfile not found." && exit 1; \
  fi

# Production image, copy all the files and run next
FROM base AS runner
WORKDIR /app

ENV NODE_ENV=production
# Uncomment the following line in case you want to disable telemetry during runtime.
# ENV NEXT_TELEMETRY_DISABLED=1

RUN addgroup --system --gid 1001 nodejs
RUN adduser --system --uid 1001 nextjs

COPY --from=builder /app/public ./public

# Automatically leverage output traces to reduce image size
# https://nextjs.org/docs/advanced-features/output-file-tracing
COPY --from=builder --chown=nextjs:nodejs /app/.next/standalone ./
COPY --from=builder --chown=nextjs:nodejs /app/.next/static ./.next/static
COPY --chown=nextjs:nodejs prisma ./prisma/

USER nextjs

EXPOSE 3000

ENV PORT=3000

# server.js is created by next build from the standalone output
# https://nextjs.org/docs/pages/api-reference/next-config-js/output
ENV HOSTNAME="0.0.0.0"
CMD ["sh", "-c", "npx prisma migrate deploy && npm run seed && node server.js"]

The above dockerfile worked and created working images flawlessly a few days ago. Today, I rebuilt the image on the same repository, on the same branch, on the same commit, and I'm getting this error:

2024-12-10 01:11:54 npm warn exec The following package was not found and will be installed: [email protected]
2024-12-10 01:11:59 prisma:warn Prisma failed to detect the libssl/openssl version to use, and may not work as expected. Defaulting to "openssl-1.1.x".
2024-12-10 01:11:59 Please manually install OpenSSL and try installing Prisma again.
2024-12-10 01:11:59 prisma:warn Prisma failed to detect the libssl/openssl version to use, and may not work as expected. Defaulting to "openssl-1.1.x".
2024-12-10 01:11:59 Please manually install OpenSSL and try installing Prisma again.
2024-12-10 01:11:59 Prisma schema loaded from prisma/schema.prisma
2024-12-10 01:11:59 Datasource "db": PostgreSQL database "REDACTED", schema "public" at "REDACTED"
2024-12-10 01:11:59 
2024-12-10 01:11:59 Error: Could not parse schema engine response: SyntaxError: Unexpected token 'E', "Error load"... is not valid JSON
2024-12-10 01:11:59 npm notice
2024-12-10 01:11:59 npm notice New patch version of npm available! 10.9.0 -> 10.9.2
2024-12-10 01:11:59 npm notice Changelog: https://github.com/npm/cli/releases/tag/v10.9.2
2024-12-10 01:11:59 npm notice To update run: npm install -g [email protected]
2024-12-10 01:11:59 npm notice

2024-12-10 01:11:54 npm warn exec The following package was not found and will be installed: [email protected]
2024-12-10 01:11:59 prisma:warn Prisma failed to detect the libssl/openssl version to use, and may not work as expected. Defaulting to "openssl-1.1.x".
2024-12-10 01:11:59 Please manually install OpenSSL and try installing Prisma again.
2024-12-10 01:11:59 prisma:warn Prisma failed to detect the libssl/openssl version to use, and may not work as expected. Defaulting to "openssl-1.1.x".
2024-12-10 01:11:59 Please manually install OpenSSL and try installing Prisma again.
2024-12-10 01:11:59 Prisma schema loaded from prisma/schema.prisma
2024-12-10 01:11:59 Datasource "db": PostgreSQL database "REDACTED", schema "public" at "REDACTED"
2024-12-10 01:11:59 
2024-12-10 01:11:59 Error: Could not parse schema engine response: SyntaxError: Unexpected token 'E', "Error load"... is not valid JSON
2024-12-10 01:11:59 npm notice
2024-12-10 01:11:59 npm notice New patch version of npm available! 10.9.0 -> 10.9.2
2024-12-10 01:11:59 npm notice Changelog: https://github.com/npm/cli/releases/tag/v10.9.2
2024-12-10 01:11:59 npm notice To update run: npm install -g [email protected]
2024-12-10 01:11:59 npm notice

13 replies

HHomarr

•Created by beanbeanjuice on 11/10/2024 in #💬・get-help

Why is it recommended to use basic auth (either through Apache2 or NGINX)?

Doesn't homarr come with a login screen already? What is the purpose of the basic auth? I know it says to keep API keys safe, but if no one knows my homarr login, they can't view my API keys right?

7 replies

HHomarr

•Created by beanbeanjuice on 9/18/2024 in #💬・get-help

Media Server/Download Speed Integrations Not Working

I'm using Portainer and stuff to run Homarr, everything is working as normal. My integrations, like the media server/download speed do not work despite plex working perfectly normal. Is there anything I can do? OS: Ubuntu 24.04 Homarr: 15.4 Config: docker-compose

version: '3'
#---------------------------------------------------------------------#
#     Homarr - A simple, yet powerful dashboard for your server.      #
#---------------------------------------------------------------------#
services:
  homarr:
    container_name: homarr
    image: ghcr.io/ajnart/homarr:latest
    restart: unless-stopped
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock # Optional, only if you want docker integration
      - /home/beanbeanjuice/projects/homarr/configs:/app/data/configs
      - /home/beanbeanjuice/projects/homarr/icons:/app/public/icons
      - /home/beanbeanjuice/projects/homarr/data:/data
    ports:
      - '7575:7575'

version: '3'
#---------------------------------------------------------------------#
#     Homarr - A simple, yet powerful dashboard for your server.      #
#---------------------------------------------------------------------#
services:
  homarr:
    container_name: homarr
    image: ghcr.io/ajnart/homarr:latest
    restart: unless-stopped
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock # Optional, only if you want docker integration
      - /home/beanbeanjuice/projects/homarr/configs:/app/data/configs
      - /home/beanbeanjuice/projects/homarr/icons:/app/public/icons
      - /home/beanbeanjuice/projects/homarr/data:/data
    ports:
      - '7575:7575'

Log file is attached.

9 replies

Gaming

Programming