Putting an API Online
Put your API at a link you can share: a free MongoDB Atlas cluster for the data, Render's free web service for the code, deployed from GitHub with its secrets set on the host, checked live, and updated with every push. Then plan your final capstone.
Updated
A Database Online
- A Free MongoDB Atlas Cluster (Journeyman): An API online can't reach the MongoDB on your laptop, so this lesson makes a free MongoDB Atlas cluster with a database user and network access, keeps its connection string secret in .env, and checks that Node connects to it.
Your API Online
- Put Your API Online with Render (Journeyman): Render's free web service runs your API from its GitHub repository at a link anyone can open, once the API takes its port from PORT, starts without a .env file and answers /health; then every push deploys again, and a rollback undoes a bad one.
Exercise: Trail Conditions Online
- Exercise: Trail Conditions Online (Journeyman): Get Willow Creek Parks' finished trails API ready for a host (settings read from the environment, a /health route, a start script with no .env file, and the secret kept out of Git), then put it online with a free Atlas cluster and Render, and hand in a repository whose README links the live API.
Where to Go Next
- Where to Go Next (Journeyman): A look back at what you can now build with Node.js, the two projects that put it all together (the Neighborhood Book Swap API and an API of your own, online with a simple front end), and how to choose your next step among a front end, TypeScript, NestJS, Docker and more MongoDB.