tudorconstantin / knests Goto Github PK

is it compatible in windows? I am having issues while building docker.

They point to resources that have either been moved or don't exist

...should they?

I also tried using the Logger class, those also don't show up in the terminal window when running the docker command, is this expected?

When spinning up, I get the following dependency error:

Building server
Step 1/7 : FROM node:16.13.0-alpine3.11 AS builder
 ---> ef75ab605b08
Step 2/7 : RUN apk add --no-cache python make g++
 ---> Using cache
 ---> 6711b49f3e1a
Step 3/7 : RUN addgroup -S nodegroup && adduser -S -G node nodegroup
 ---> Using cache
 ---> 68d87abaa70a
Step 4/7 : USER node
 ---> Using cache
 ---> 7d2b77d55a34
Step 5/7 : WORKDIR /home/node
 ---> Using cache
 ---> a4716a856254
Step 6/7 : COPY --chown=node:nodegroup package.json /home/node/
 ---> Using cache
 ---> d1d555ffd3c3
Step 7/7 : RUN npm install
 ---> Running in b580bfef63fe
npm notice 
npm notice New minor version of npm available! 8.1.0 -> 8.3.2
npm notice Changelog: <https://github.com/npm/cli/releases/tag/v8.3.2>
npm notice Run `npm install -g [email protected]` to update!
npm notice 
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: @nestjs/[email protected]
npm ERR! node_modules/@nestjs/common
npm ERR!   @nestjs/common@"8.2.3" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @nestjs/common@"^6.0.0" from @nestjsplus/[email protected]
npm ERR! node_modules/@nestjsplus/config
npm ERR!   @nestjsplus/config@"1.0.14" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /home/node/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/node/.npm/_logs/2022-01-27T08_24_00_716Z-debug.log
ERROR: Service 'server' failed to build: The command '/bin/sh -c npm install' returned a non-zero code: 1

I'm looking into hosting this project now, wondering if it's best to use ECS or UKS? I noticed you mentioned kubernetes in the roadmap, wondering why you made that choice?

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Error type: undefined. Note: this is a nested preset so please contact the preset author if you are unable to fix it yourself.

WebSocket connection to 'ws://localhost:8080/graphql' failed: Error during WebSocket handshake: Unexpected response code: 400

get this pretty often and haven't been able to figure out why yet. checked and auth header is getting set correctly once on the dashboard

Hey,

Just looking over your code and I'm wondering how you're serving the next.js app. I don't see a next.js module under server directory, so I'm wondering if you're even using SSR.

I'm guessing you're serving it SSR through ZEIT and you're using nest.js as an API server or graphql in this case. If this is true, it would mean your next.js server has to request data from the API server each time a request is made? Is this right?

Thanks

Hey! This is a cool project, I haven't used this stack before and wanted to try it out.

started off by trying to extend passport to also have facebook login, followed this tutorial, and every time I try to hit /facebook i get a 404. not sure what's going on. RoutesExplorer shows the route being mapped, so I'm not sure what's going on.

also, do i always have to run rm -rf client/dist && docker-compose -f docker-compose.yml -f docker-compose.dev.yml up --build -V --force-recreate to start the project, or is there a shorter command? (first time using docker as well 😄)

Error: Missing "driver" option. In the latest version of "@nestjs/graphql" package (v10) a new required configuration property called "driver" has been introduced.

Hey, you should add your npm/yarm lock files to the repo

Hi, this looks like a really nice project, however I can't get it running.

I got the following error message.

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Datasource	Name	Replacement PR?
npm	@material-ui/core
npm	@material-ui/icons
npm	@material-ui/styles
npm	@types/jwt-decode
npm	@types/knex
npm	subscriptions-transport-ws

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

• Update dependency @types/jest to v27.5.2
• Update dependency @types/passport-jwt to v3.0.13
• Update dependency @types/react to v17.0.80
• Update dependency @types/supertest to v2.0.16
• Update dependency class-validator to v0.14.1
• Update dependency js-cookie to v3.0.5
• Update dependency node-sass to v7.0.3
• Update dependency nodemon to v2.0.22
• Update docker Docker tag to v20.10.24
• Update nest monorepo (@nestjs/common, @nestjs/passport, @nestjs/platform-express, @nestjs/testing)
• Update Apollo GraphQL packages (@apollo/client, @apollo/gateway, apollo-server-express)
• Update Node.js to v14.21.3
• Update Node.js to v16.20.2 (node, @types/node)
• Update babel monorepo to v7.24.7 (@babel/plugin-transform-modules-commonjs, @babel/preset-typescript)
• Update dependency bcrypt to v5.1.1 (bcrypt, @types/bcrypt)
• Update dependency chart.js to v3.9.1
• Update dependency eslint to v8.57.0
• Update dependency eslint-config-next to v12.3.4
• Update dependency eslint-plugin-import to v2.29.1
• Update dependency eslint-plugin-jsdoc to v39.9.1
• Update dependency graphql to v15.9.0
• Update dependency moment to v2.30.1
• Update dependency pg to v8.12.0
• Update dependency prettier to v2.8.8
• Update dependency react-chartjs-2 to v4.3.1
• Update dependency reflect-metadata to v0.2.2
• Update dependency ts-loader to v9.5.1
• Update dependency ts-node to v10.9.2
• Update dependency tsconfig-paths to v3.15.0
• Update dependency typescript to v4.9.5
• Update graphql-tools monorepo (@graphql-tools/schema, graphql-tools)
• Update playwright monorepo to v1.44.1 (playwright, playwright-chromium)
• Update postgres Docker tag to v14.12
• Update typescript-eslint monorepo to v5.62.0 (@typescript-eslint/eslint-plugin, @typescript-eslint/parser)
• Update Node.js to v20 (node, @types/node)
• Update actions/checkout action to v4
• Update dependency @nestjs/cli to v10
• Update dependency @nestjs/config to v3
• Update dependency @nestjs/graphql to v12
• Update dependency @nestjs/jwt to v10
• Update dependency @types/uuid to v10
• Update dependency chart.js to v4
• Update dependency eslint to v9
• Update dependency eslint-config-next to v14
• Update dependency eslint-plugin-jsdoc to v48
• Update dependency http-proxy-middleware to v3
• Update dependency jest-playwright-preset to v4
• Update dependency jwt-decode to v4
• Update dependency node-sass to v9
• Update dependency nodemon to v3
• Update dependency nyc to v17
• Update dependency passport-jwt to v4.0.1 (passport-jwt, @types/passport-jwt)
• Update dependency prettier to v3
• Update dependency react-chartjs-2 to v5
• Update dependency rimraf to v5
• Update dependency supertest to v6.3.4 (supertest, @types/supertest)
• Update dependency supertest to v7
• Update dependency ts-morph to v22
• Update dependency tsconfig-paths to v4
• Update dependency typescript to v5
• Update docker Docker tag to v26
• Update graphql-tools monorepo (major) (@graphql-tools/schema, graphql-tools)
• Update jest monorepo to v29 (major) (@types/jest, jest, ts-jest)
• Update nest monorepo to v10 (major) (@nestjs/common, @nestjs/passport, @nestjs/platform-express, @nestjs/schematics, @nestjs/testing)
• Update postgres Docker tag to v16
• Update typescript-eslint monorepo to v7 (major) (@typescript-eslint/eslint-plugin, @typescript-eslint/parser)
• 🔐 Create all rate-limited PRs at once 🔐

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• Update dependency express to v4.19.2 [SECURITY]
• Update dependency passport to v0.6.0 [SECURITY]
• Update dependency @nestjs/core to v9 [SECURITY]
• Update dependency knex to v2 [SECURITY]
• Update dependency next to v13 [SECURITY]
• Replace dependency @material-ui/core with @mui/material 5.0.0
• Replace dependency @material-ui/icons with @mui/icons-material 5.0.0
• Replace dependency @material-ui/styles with @mui/styles 5.0.0
• Update dependency @nestjs/cli to v8.2.8
• Update dependency @apollo/gateway to v2
• Update dependency graphql to v16.9.0
• Update react monorepo to v18 (major) (@types/react, react, react-dom)
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

I'm looking into hosting this project now, wondering if it's best to use ECS or UKS? I noticed you mentioned kubernetes in the roadmap, wondering why you made that choice?

proxy request /graphql from localhost:8080 to http://server:8081/graphql (ECONNREFUSED)

haven't found a way around this yet

Would hasten the development here a good bit! I'm looking into it now, wonder if you thought about this before

Hey,

Great package! I'm still going through it and disclaimer, I've only been messing around with Docker for a couple of months, but is there any way that you know if to add npm packages without rebuilding the image? Not within your package, but in general?

It's a real drag having to rebuild the image every time you add a new image in dev.

Thanks