In order to solve the security problems https://github.com/pavelk2/social-feed/issues/44, we need to have a back-end which does the actual interactions with social networks, while the front-end only pulls the data from this back-end.
The back-end will stay in a different repository. In order to make it very easy for people with absent/low back-end development skills to deploy such a back-end we create a Heroku deploy button, using which people can deploy in a single click the code on a free instance on Heroku. To keep the similarity with the front-end we implement the back-end in Node.js (using Express.js framework). All the social-network credentials should be defined as environmental variables. The domain name from which the requests are sent from the front-end should also be defined as an environmental variable and fixed in CORS.
In order to solve the security problems https://github.com/pavelk2/social-feed/issues/44, we need to have a back-end which does the actual interactions with social networks, while the front-end only pulls the data from this back-end.
The back-end will stay in a different repository. In order to make it very easy for people with absent/low back-end development skills to deploy such a back-end we create a Heroku deploy button, using which people can deploy in a single click the code on a free instance on Heroku. To keep the similarity with the front-end we implement the back-end in Node.js (using Express.js framework). All the social-network credentials should be defined as environmental variables. The domain name from which the requests are sent from the front-end should also be defined as an environmental variable and fixed in CORS.