When I started developing my website I never thought I'd be using a back-end API service, I mean what's the need? Surely a portfolio should be pretty simple and at minimum contain pages such as about, projects and contact?
For a while now, I've been spending a lot of my spare time working on projects and getting to grips with new tech - including Node.js. I created an opportunity for myself to showcase what I've learnt.
I've developed a single API Node.js back-end service to do the following:
- Projects (GitHub)
- Get all repos
- Get repo readme
- Blog (DEV.to)
- Get all posts
- Email (Nodemailer)
- Send contact email (from x2 projects)
- Text (Twilio)
- Send text (just started playing around)
You can find the repo here. I have a config file that's included in gitignore for smtp settings, github token and twilio dets. If helpful I can include the layout of this here at some point? Anyway...
I'm still learning Node.js and next I want to tidy the code base up i.e. add controllers, services and routes. I've used Firebase Cloud Functions for this project and have started to play around with Heruko in another.
I developed a single service to do this purely for costing purposes - FCF costs, so I might move this project to Heruko eventually. Maybe once the code base is all nice and pretty... 🎀
Thank you for reading, any feedback is welcome and info about deploying Node.js too - i.e. recommended platforms.