TrueNas support?
Any update on whether peppermint will be on TrueNas?
It previously used to be possible using TrueCharts (https://truecharts.org/charts/incubator/peppermint/) but not any longer.
Alternatively you can install Portainer and then through there add it, however having it as an app would be so much more simple.
Does truenas not have docker support? I can take a look into this
Does truenas not have docker support? I can take a look into this
Truenas does have docker support, also has vms, which if you want, you can spin up an ubuntu server and get docker and get peppermint running. But He might be talking about the one click install plugins maybe?
Edit: He is talking about the app plugins.
Yes, I'm talking about the one click install plugins, thanks Bob for clarifying.
Before the big update "Electric Eel" I believe TrueCharts made a plugin for it, but now it's been deprecated so when searching the catalogue for peppermint it's no longer there, but I am sure it can be, hence the post. It would be nice.
I don't use truenas myself, i'll look into getting it set up myself and get this created
Now that TrueNAS Scale has support for docker. I went ahead and copied and pasted the yaml found in the README. However, visiting <server-ip>:3000 does not load the webpage.
Here's what the logs show.
2025-04-18 14:57:49.042123+00:002025-04-18T14:57:49: PM2 log: Launching in no daemon mode
2025-04-18 14:57:49.086362+00:002025-04-18T14:57:49: PM2 log: App [client:0] starting in -fork mode-
2025-04-18 14:57:49.088743+00:002025-04-18T14:57:49: PM2 log: App [api:1] starting in -fork mode-
2025-04-18 14:57:49.101308+00:002025-04-18T14:57:49: PM2 log: App [client:0] online
2025-04-18 14:57:49.110680+00:002025-04-18T14:57:49: PM2 log: App [api:1] online
2025-04-18 14:57:49.754141+00:00▲ Next.js 13.5.7
2025-04-18 14:57:49.755869+00:00- Local: http://84e41b4f9df8:3000
2025-04-18 14:57:49.755947+00:00- Network: http://[fdd0:0:0:7::3]:3000
2025-04-18 14:57:49.756200+00:00✓ Ready in 374ms
2025-04-18 14:57:49.931080+00:00(node:24) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
2025-04-18 14:57:49.931112+00:00(Use `node --trace-deprecation ...` to show where the warning was created)
2025-04-18 14:57:51.028504+00:00Environment variables loaded from .env
2025-04-18 14:57:51.028555+00:00Prisma schema loaded from src/prisma/schema.prisma
2025-04-18 14:57:51.028584+00:00Datasource "db": PostgreSQL database "peppermint", schema "public" at "peppermint_postgres"
2025-04-18 14:57:51.028593+00:0057 migrations found in prisma/migrations
2025-04-18 14:57:51.028601+00:00No pending migrations to apply.
2025-04-18 14:57:51.028506+00:00npm notice
2025-04-18 14:57:51.028621+00:00npm notice New major version of npm available! 10.9.0 -> 11.3.0
2025-04-18 14:57:51.028629+00:00npm notice Changelog: https://github.com/npm/cli/releases/tag/v11.3.0
2025-04-18 14:57:51.028636+00:00npm notice To update run: npm install -g [email protected]
2025-04-18 14:57:51.028642+00:00npm notice
2025-04-18 14:57:52.807071+00:00Environment variables loaded from .env
2025-04-18 14:57:52.807308+00:00Running seed command `node ./src/prisma/seed.js` ...
2025-04-18 14:57:52.807441+00:00No need to seed, already seeded
2025-04-18 14:57:52.807569+00:00🌱 The seed command has been executed.
2025-04-18 14:57:52.807950+00:00┌─────────────────────────────────────────────────────────┐
2025-04-18 14:57:52.809643+00:00│ Update available 5.6.0 -> 6.6.0 │
2025-04-18 14:57:52.809794+00:00│ │
2025-04-18 14:57:52.810144+00:00│ This is a major update - please follow the guide at │
2025-04-18 14:57:52.810204+00:00│ https://pris.ly/d/major-version-upgrade │
2025-04-18 14:57:52.810213+00:00│ │
2025-04-18 14:57:52.810220+00:00│ Run the following to update │
2025-04-18 14:57:52.810225+00:00│ npm i --save-dev prisma@latest │
2025-04-18 14:57:52.810236+00:00│ npm i @prisma/client@latest │
2025-04-18 14:57:52.810242+00:00└─────────────────────────────────────────────────────────┘
2025-04-18 14:57:52.966019+00:00strict mode: missing type "object" for keyword "required" at "#" (strictTypes)
2025-04-18 14:57:52.966073+00:00strict mode: missing type "object" for keyword "properties" at "#" (strictTypes)
2025-04-18 14:57:52.981535+00:00Server listening on http://127.0.0.1:5003
2025-04-18 14:57:53.310577+00:00Environment variables loaded from .env
2025-04-18 14:57:53.310769+00:00Prisma schema loaded from src/prisma/schema.prisma
2025-04-18 14:57:53.310924+00:00✔ Generated Prisma Client (v5.6.0, engine=binary) to ./node_modules/@prisma/client in 341ms
2025-04-18 14:57:53.311082+00:00Start using Prisma Client in Node.js (See: https://pris.ly/d/client)
2025-04-18 14:57:53.311108+00:00```
2025-04-18 14:57:53.311117+00:00import { PrismaClient } from '@prisma/client'
2025-04-18 14:57:53.311136+00:00const prisma = new PrismaClient()
2025-04-18 14:57:53.311143+00:00```
2025-04-18 14:57:53.311150+00:00or start using Prisma Client at the edge (See: https://pris.ly/d/accelerate)
2025-04-18 14:57:53.311261+00:00```
2025-04-18 14:57:53.311280+00:00import { PrismaClient } from '@prisma/client/edge'
2025-04-18 14:57:53.311297+00:00const prisma = new PrismaClient()
2025-04-18 14:57:53.311303+00:00```
2025-04-18 14:57:53.311311+00:00See other ways of importing Prisma Client: http://pris.ly/d/importing-client
2025-04-18 14:58:02.304631+00:00Error while shutting down PostHog Error [PostHogFetchNetworkError]: Network error while fetching PostHog
2025-04-18 14:58:02.304779+00:00at new PostHogFetchNetworkError (/apps/api/node_modules/posthog-node/lib/index.cjs.js:1127:16)
2025-04-18 14:58:02.305828+00:00at PostHog.<anonymous> (/apps/api/node_modules/posthog-node/lib/index.cjs.js:1521:51)
2025-04-18 14:58:02.305957+00:00at step (/apps/api/node_modules/posthog-node/lib/index.cjs.js:135:27)
2025-04-18 14:58:02.305997+00:00at Object.throw (/apps/api/node_modules/posthog-node/lib/index.cjs.js:84:53)
2025-04-18 14:58:02.306010+00:00at rejected (/apps/api/node_modules/posthog-node/lib/index.cjs.js:71:36)
2025-04-18 14:58:02.306022+00:00at process.processTicksAndRejections (node:internal/process/task_queues:105:5) {
2025-04-18 14:58:02.306041+00:00error: TypeError: fetch failed
2025-04-18 14:58:02.306053+00:00at node:internal/deps/undici/undici:13392:13
2025-04-18 14:58:02.306066+00:00at process.processTicksAndRejections (node:internal/process/task_queues:105:5) {
2025-04-18 14:58:02.306077+00:00[cause]: Error: self-signed certificate
2025-04-18 14:58:02.306089+00:00at TLSSocket.onConnectSecure (node:_tls_wrap:1679:34)
2025-04-18 14:58:02.306108+00:00at TLSSocket.emit (node:events:518:28)
2025-04-18 14:58:02.306121+00:00at TLSSocket._finishInit (node:_tls_wrap:1078:8)
2025-04-18 14:58:02.306133+00:00at ssl.onhandshakedone (node:_tls_wrap:864:12) {
2025-04-18 14:58:02.306145+00:00code: 'DEPTH_ZERO_SELF_SIGNED_CERT'
2025-04-18 14:58:02.306174+00:00}
2025-04-18 14:58:02.306187+00:00},
2025-04-18 14:58:02.306199+00:00[cause]: TypeError: fetch failed
2025-04-18 14:58:02.306210+00:00at node:internal/deps/undici/undici:13392:13
2025-04-18 14:58:02.306222+00:00at process.processTicksAndRejections (node:internal/process/task_queues:105:5) {
2025-04-18 14:58:02.306241+00:00[cause]: Error: self-signed certificate
2025-04-18 14:58:02.306253+00:00at TLSSocket.onConnectSecure (node:_tls_wrap:1679:34)
2025-04-18 14:58:02.306265+00:00at TLSSocket.emit (node:events:518:28)
2025-04-18 14:58:02.306277+00:00at TLSSocket._finishInit (node:_tls_wrap:1078:8)
2025-04-18 14:58:02.306295+00:00at ssl.onhandshakedone (node:_tls_wrap:864:12) {
2025-04-18 14:58:02.306308+00:00code: 'DEPTH_ZERO_SELF_SIGNED_CERT'
2025-04-18 14:58:02.306320+00:00}
2025-04-18 14:58:02.306331+00:00}
2025-04-18 14:58:02.306342+00:00}
2025-04-18 14:58:02.923633+00:00Email fetch completed
2025-04-18 14:58:12.914670+00:00Email fetch completed