Do you really need to separate frontend and backend?
Maybe you can cut 1 dyno and deploy backend and frontend from the same repository.
Hmm..
So in the Procfile I could just do:
node fe/server.js && node be/server.js ?
No sorry, I might not have understood correctly the architecture.
Why do you have two servers?
For REST API.. On the client side I need server side rendering for SEO, am I wrong?
I don't know, it seems a very complicated setup for something that should be cheap :-)
Also, why do you want to write it yourself instead of using or customizing an existing CMS?
You can use Wordpress or customize a CMS in your favorite language or even use a "headless" CMS as the API and build the frontend yourself.
Something like getdirectus.com/
This way you have a CMS and you can build many different types of frontends on it
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.
Do you really need to separate frontend and backend?
Maybe you can cut 1 dyno and deploy backend and frontend from the same repository.
Hmm..
So in the Procfile I could just do:
node fe/server.js && node be/server.js ?
No sorry, I might not have understood correctly the architecture.
Why do you have two servers?
For REST API..
On the client side I need server side rendering for SEO, am I wrong?
I don't know, it seems a very complicated setup for something that should be cheap :-)
Also, why do you want to write it yourself instead of using or customizing an existing CMS?
You can use Wordpress or customize a CMS in your favorite language or even use a "headless" CMS as the API and build the frontend yourself.
Something like getdirectus.com/
This way you have a CMS and you can build many different types of frontends on it