What you’ve mastered
As a Data Wizard you can:
- explain why data in memory disappears
- version code with Git and back it up on GitHub
- store messages in SQLite
- deploy a server (Render) and a frontend (Vercel/Netlify) – you already know this from Master
Show me: the checklist
Go through your project and check off:
| Task | Done? |
|---|---|
| Repository on GitHub, latest code pushed | ☐ |
.gitignore contains node_modules, .env, web.db | ☐ |
The server uses SQLite for /api/vzkazy | ☐ |
| Messages remain after a server restart | ☐ |
| The frontend calls the correct API URL (localhost or production) | ☐ |
Deploying with a database
- Push
my-serverto GitHub. - On Render, create a Web Service from the repository (
npm install,node server.js). - Note: the first
web.dbwill be created empty on the server at startup – that’s fine. - Deploy the frontend as before; in
fetch, use the Render URL instead oflocalhost:3900.
💡
Diploma: finished the whole level? In the Certificates section you can print your Data Wizard diploma – a well-earned reward for all your work.
Your turn 💪
- Go through the table above and fill in what’s missing.
- Write 3 sentences in the repository’s README (on GitHub): what the project is about, how to run it (
npm install,node server.js), and what port it runs on. - Send the link to your live frontend to a parent or friend – your website with a permanent guestbook.
✅
Check: All of Level 4 is done. You’re a Data Wizard – your code is under control in Git and your data lives in a database. 🎉
What to take away from this lesson
- Data Wizard = Git + GitHub + SQLite + deployment.
- In production, think about a permanent disk or a hosted DB.
- The journey continues: Level 5 – Inventor will teach your website to talk to APIs and AI.
© 2026 Ing. Martin Polak / AlgoRhino · Content usage terms