beanbeanjuice
beanbeanjuice
Explore posts from servers
HHomarr
Created by beanbeanjuice on 12/18/2024 in #💬・get-help
Dash. Integration Not Working in Beta
Yes, except it works fine regardless if its enabled/disabled for Server #3 which uses cloudflare tunnel
21 replies
HHomarr
Created by beanbeanjuice on 12/18/2024 in #💬・get-help
Dash. Integration Not Working in Beta
It's weird, Server #3 (cloudflare tunnel) works without commenting out the environment variable.
21 replies
HHomarr
Created by beanbeanjuice on 12/18/2024 in #💬・get-help
Tiles Not Saving Properly in Beta
I'm using Firefox Developer and here's my docker compose
beanbeanjuice-dashboard:
container_name: beanbeanjuice-dashboard
image: ghcr.io/homarr-labs/homarr:beta
restart: unless-stopped
volumes:
- /home/beanbeanjuice/projects/homarr:/appdata
networks:
- nginx-network
depends_on:
- beanbeanjuice-dashdot
beanbeanjuice-dashboard:
container_name: beanbeanjuice-dashboard
image: ghcr.io/homarr-labs/homarr:beta
restart: unless-stopped
volumes:
- /home/beanbeanjuice/projects/homarr:/appdata
networks:
- nginx-network
depends_on:
- beanbeanjuice-dashdot
9 replies
HHomarr
Created by beanbeanjuice on 12/18/2024 in #💬・get-help
Tiles Not Saving Properly in Beta
No description
9 replies
HHomarr
Created by beanbeanjuice on 12/18/2024 in #💬・get-help
Tiles Not Saving Properly in Beta
No description
9 replies
HHomarr
Created by beanbeanjuice on 12/18/2024 in #💬・get-help
Dash. Integration Not Working in Beta
Nonetheless, CPU temps aren't super important for me but yeah I'm glad it's working now. If you need me to debug further to get CPU temps working please let me know!
21 replies
HHomarr
Created by beanbeanjuice on 12/18/2024 in #💬・get-help
Dash. Integration Not Working in Beta
How odd...
21 replies
HHomarr
Created by beanbeanjuice on 12/18/2024 in #💬・get-help
Dash. Integration Not Working in Beta
Disabling fixed it!
21 replies
HHomarr
Created by beanbeanjuice on 12/18/2024 in #💬・get-help
Dash. Integration Not Working in Beta
Hey! I have this here as my configuration for Server #1 and Server #2 (everything is the same aside from the container name)
beanbeanjuice-dashdot:
container_name: beanbeanjuice-dashdot
image: mauricenino/dashdot:latest
restart: unless-stopped
privileged: true
volumes:
- /:/mnt/host:ro
environment:
DASHDOT_ENABLE_CPU_TEMPS: 'true'
networks:
- nginx-network
beanbeanjuice-dashdot:
container_name: beanbeanjuice-dashdot
image: mauricenino/dashdot:latest
restart: unless-stopped
privileged: true
volumes:
- /:/mnt/host:ro
environment:
DASHDOT_ENABLE_CPU_TEMPS: 'true'
networks:
- nginx-network
Server #3 has this configuration
services:
dashdot:
container_name: dashdot
image: mauricenino/dashdot:latest
restart: unless-stopped
privileged: true
volumes:
- /:/mnt/host:ro
environment:
DASHDOT_ENABLE_CPU_TEMPS: 'true'
networks:
- cloudflare-network

networks:
cloudflare-network:
name: cloudflare-network
external: true
services:
dashdot:
container_name: dashdot
image: mauricenino/dashdot:latest
restart: unless-stopped
privileged: true
volumes:
- /:/mnt/host:ro
environment:
DASHDOT_ENABLE_CPU_TEMPS: 'true'
networks:
- cloudflare-network

networks:
cloudflare-network:
name: cloudflare-network
external: true
It seems as though CPU temps is already enabled, i'll try disabling and seeing if that makes a difference
21 replies
HHomarr
Created by beanbeanjuice on 12/18/2024 in #💬・get-help
Dash. Integration Not Working in Beta
fixed this issue by doing this;
location / {
proxy_pass http://beanbeanjuice-dashboard:7575/;
#include proxy_params;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "Upgrade";
proxy_set_header Host $host;
}
location / {
proxy_pass http://beanbeanjuice-dashboard:7575/;
#include proxy_params;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "Upgrade";
proxy_set_header Host $host;
}
However, the issues above still persist
21 replies
HHomarr
Created by beanbeanjuice on 12/18/2024 in #💬・get-help
Dash. Integration Not Working in Beta
No description
21 replies
HHomarr
Created by beanbeanjuice on 12/18/2024 in #💬・get-help
Dash. Integration Not Working in Beta
Using this YML produces the same result
beanbeanjuice-dashboard:
container_name: beanbeanjuice-dashboard
image: ghcr.io/homarr-labs/homarr:beta
restart: unless-stopped
volumes:
- /home/beanbeanjuice/projects/homarr:/appdata
networks:
- nginx-network
# - default
depends_on:
- beanbeanjuice-dashdot
beanbeanjuice-dashboard:
container_name: beanbeanjuice-dashboard
image: ghcr.io/homarr-labs/homarr:beta
restart: unless-stopped
volumes:
- /home/beanbeanjuice/projects/homarr:/appdata
networks:
- nginx-network
# - default
depends_on:
- beanbeanjuice-dashdot
21 replies
HHomarr
Created by beanbeanjuice on 12/18/2024 in #💬・get-help
Dash. Integration Not Working in Beta
beanbeanjuice-dashboard:
container_name: beanbeanjuice-dashboard
image: ghcr.io/homarr-labs/homarr:beta
restart: unless-stopped
volumes:
- /home/beanbeanjuice/projects/homarr:/appdata
networks:
- nginx-network
- default
depends_on:
- beanbeanjuice-dashdot
beanbeanjuice-dashboard:
container_name: beanbeanjuice-dashboard
image: ghcr.io/homarr-labs/homarr:beta
restart: unless-stopped
volumes:
- /home/beanbeanjuice/projects/homarr:/appdata
networks:
- nginx-network
- default
depends_on:
- beanbeanjuice-dashdot
21 replies
HHomarr
Created by beanbeanjuice on 12/18/2024 in #💬・get-help
Dash. Integration Not Working in Beta
No description
21 replies
HHomarr
Created by beanbeanjuice on 12/18/2024 in #💬・get-help
Dash. Integration Not Working in Beta
No description
21 replies
PPrisma
Created by beanbeanjuice on 12/10/2024 in #help-and-questions
Previously Working Dockerfile No Longer Works
Actually this is half of what I did to get it to work!
13 replies
PPrisma
Created by beanbeanjuice on 12/10/2024 in #help-and-questions
Previously Working Dockerfile No Longer Works
Correct
13 replies
PPrisma
Created by beanbeanjuice on 12/10/2024 in #help-and-questions
Previously Working Dockerfile No Longer Works
Posted this in the wrong chat previously... sorry! But I managed to "fix" it. I'm not sure if this is a bad way, but I'm sure someone will correct me if I am wrong. These are my latest files/settings which fixed it.
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 openssl
WORKDIR /app

# Install dependencies based on the preferred package manager
COPY package.json yarn.lock* package-lock.json* pnpm-lock.yaml* .npmrc* ./
RUN npm ci

# Rebuild the source code only when needed
FROM base AS builder
WORKDIR /app
COPY --from=deps /app/node_modules ./node_modules
RUN apk add --no-cache openssl
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 npm run build

# 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
RUN apk add --no-cache openssl

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 openssl
WORKDIR /app

# Install dependencies based on the preferred package manager
COPY package.json yarn.lock* package-lock.json* pnpm-lock.yaml* .npmrc* ./
RUN npm ci

# Rebuild the source code only when needed
FROM base AS builder
WORKDIR /app
COPY --from=deps /app/node_modules ./node_modules
RUN apk add --no-cache openssl
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 npm run build

# 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
RUN apk add --no-cache openssl

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"]
generator client {
provider = "prisma-client-js"
binaryTargets = ["native", "linux-musl", "linux-musl-openssl-3.0.x"]
}
generator client {
provider = "prisma-client-js"
binaryTargets = ["native", "linux-musl", "linux-musl-openssl-3.0.x"]
}
13 replies
PPrisma
Created by beanbeanjuice on 12/10/2024 in #help-and-questions
Previously Working Dockerfile No Longer Works
Again, the only thing that changed is I built a working image via GitHub actions AND locally 3 days ago. Building the new image TODAY it causes that error.
13 replies
PPrisma
Created by beanbeanjuice on 12/10/2024 in #help-and-questions
Previously Working Dockerfile No Longer Works
{
"name": "REDACTED",
"version": "0.0.0",
"private": true,
"type": "module",
"scripts": {
"seed": "node prisma/seed.js",
"dev": "next dev",
"build": "next build",
"postbuild": "next-sitemap --config next-sitemap.config.cjs",
"start": "next start",
"lint": "next lint"
},
"prisma": {
"seed": "node prisma/seed.js"
},
"dependencies": {
"@apollo/client": "^3.11.10",
"@apollo/server": "^4.11.2",
"@as-integrations/next": "^3.2.0",
"@emotion/react": "^11.13.5",
"@emotion/styled": "^11.13.5",
"@graphql-tools/merge": "^9.0.10",
"@mui/icons-material": "^6.1.9",
"@mui/material": "^6.1.9",
"@prisma/client": "^6.0.0",
"axios": "^1.7.7",
"bcrypt": "^5.1.1",
"dateformat": "^5.0.3",
"framer-motion": "^11.11.17",
"graphql": "^16.9.0",
"graphql-tag": "^2.12.6",
"jsonwebtoken": "^9.0.2",
"minio": "^8.0.2",
"next": "15.0.3",
"next-auth": "^4.24.10",
"next-sitemap": "^4.2.3",
"react": "18.3.1",
"react-burger-menu": "^3.1.0",
"react-dom": "18.3.1",
"react-loading-indicators": "^1.0.0",
"sass": "^1.81.0"
},
"devDependencies": {
"@types/dateformat": "^5.0.2",
"@types/graphql": "^14.2.3",
"@types/jsonwebtoken": "^9.0.7",
"@types/minio": "^7.1.0",
"@types/node": "^20.17.9",
"@types/react": "^18.3.12",
"@types/react-burger-menu": "^2.8.7",
"@types/react-dom": "^18",
"prisma": "^6.0.0",
"typescript": "^5.7.2"
}
}
{
"name": "REDACTED",
"version": "0.0.0",
"private": true,
"type": "module",
"scripts": {
"seed": "node prisma/seed.js",
"dev": "next dev",
"build": "next build",
"postbuild": "next-sitemap --config next-sitemap.config.cjs",
"start": "next start",
"lint": "next lint"
},
"prisma": {
"seed": "node prisma/seed.js"
},
"dependencies": {
"@apollo/client": "^3.11.10",
"@apollo/server": "^4.11.2",
"@as-integrations/next": "^3.2.0",
"@emotion/react": "^11.13.5",
"@emotion/styled": "^11.13.5",
"@graphql-tools/merge": "^9.0.10",
"@mui/icons-material": "^6.1.9",
"@mui/material": "^6.1.9",
"@prisma/client": "^6.0.0",
"axios": "^1.7.7",
"bcrypt": "^5.1.1",
"dateformat": "^5.0.3",
"framer-motion": "^11.11.17",
"graphql": "^16.9.0",
"graphql-tag": "^2.12.6",
"jsonwebtoken": "^9.0.2",
"minio": "^8.0.2",
"next": "15.0.3",
"next-auth": "^4.24.10",
"next-sitemap": "^4.2.3",
"react": "18.3.1",
"react-burger-menu": "^3.1.0",
"react-dom": "18.3.1",
"react-loading-indicators": "^1.0.0",
"sass": "^1.81.0"
},
"devDependencies": {
"@types/dateformat": "^5.0.2",
"@types/graphql": "^14.2.3",
"@types/jsonwebtoken": "^9.0.7",
"@types/minio": "^7.1.0",
"@types/node": "^20.17.9",
"@types/react": "^18.3.12",
"@types/react-burger-menu": "^2.8.7",
"@types/react-dom": "^18",
"prisma": "^6.0.0",
"typescript": "^5.7.2"
}
}
This is my package.json
13 replies