A space to discuss and keep up software development and manage your software career
An inclusive community for gaming enthusiasts
News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more.
From composing and gigging to gear, hot music takes, and everything in between.
Discussing AI software development, and showing off what we're building.
A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here
Movie and TV enthusiasm, criticism and everything in-between.
Memes and software development shitposting
Web design, graphic design and everything in-between
A community of golfers and golfing enthusiasts
Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike
For engineers building software at scale. We discuss architecture, cloud-native, and SRE—the hard-won lessons you can't just Google
Discussing the core forem open source software project — features, bugs, performance, self-hosting.
A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis.
A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other.
A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more.
So I would need to run npm start for both express and the client? Is the proxy you added just for local development? How would I deploy this test code of yours to production
You would need to run npm start for both locally. It works in production as well, I'll add a section on deployment tonight.
Thanks. I would guess you would want to compile the code in the client folder so yeah, would love to read about that process
I've added a short section, I hope that everything is clear
Yes this makes sense. Your creating a Node Heroku setup and it will run that. Thanks
For running locally from your ./client folder, you can modify your package.json script to start both at the same time:
"scripts": { "start": "node ../index.js | react-scripts start", ... }
And when you C to terminate batch job, it will terminate both front and back localhosts.
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
So I would need to run npm start for both express and the client? Is the proxy you added just for local development? How would I deploy this test code of yours to production
You would need to run npm start for both locally. It works in production as well, I'll add a section on deployment tonight.
Thanks. I would guess you would want to compile the code in the client folder so yeah, would love to read about that process
I've added a short section, I hope that everything is clear
Yes this makes sense. Your creating a Node Heroku setup and it will run that. Thanks
For running locally from your ./client folder, you can modify your package.json script to start both at the same time:
And when you C to terminate batch job, it will terminate both front and back localhosts.