So I'm new to Nginx and that's what I think is causing my problem. I have tried changing the origin value in my app.use(cors(corsOptions)) but in the browser console, it says the same error. This makes me believe it's a…
my publisher.ts file: import nats from 'node-nats-streaming'; const stan = nats.connect('ticketing', 'abc', { url: 'http://localhost:4222', }); stan.on('connect', () => { console.log('Publisher connected to NATS'); }); }); my port forwarding command: kubectl port-forward {nats-deployment pod name} 4222:4222 my publish command in…
I am quite desperate right now and I am looking for any kind of help. I am trying to setup cache mechanism in my project using GraphQL and Redis. This is how I configure GraphQLModule: GraphQLModule.forRoot({ cache: new BaseRedisCache({ client:…
I have taken about 2days to research on this and i have come across several answers but it doesn't still solve my problem. I have this api app which i built with nodejs and express js, when I listen to…
const redis = require("redis"); let client = redis.createClient({ host: process.env.host, port: process.env.port, password:process.env.password }); (async () => { client.on('error', (err) => console.log('Redis Client Error', err)); await client.connect(); console.log("connected to redis") })(); I have added redis-heroku addon to my project, Now…
I'm creating a React app with docker in WSL2 and create-react-app and everything seems to be working fine except the app is not updating with changes in the code. I mean, when I make a change in the code, the…
I had watched a series of tutorials online and had followed lot of steps. I had to change my IP address to my machine IP, but yet network error. even, I had to change it to 127.0.0.1. Am just so…
const redis = require('redis'); const client = redis.createClient({ host: 'redis-19606.redislabs.com', port: 19606, password: 'password' }); client.on('ready', () => { console.log('redis is connected'); }); client.on('error', (err) => { console.log('redis is disconnected: ', err); }); (async () => { try { await…
Can you suggest me a way of separating learning/trying out vs production in the same computer? I am in such a place that I know a lot of JS and production ready skills whilst sometimes require probing or trying out…
I have a node.js application that run as a application server. It is deployed on an Ubuntu 20.04 machine running on AWS, uses nginx as a reverse proxy and PM2 as a service starter. Everything seems perfectly configured. What looks…