EODHD Academy
‹ Start From Zero Lesson 20 of 21
Contents Lesson 20 of 21

3 min read · foundations

Deploy something tiny, and what course 1 expects

Course 1 defines success as "deployed at a URL you own". Here you do it once, on something trivial, so the word means something before it matters.

What deploying is

Your code runs on your machine because your machine is on. Deploying puts it on a machine that is always on, at an address anyone can open.

That is the whole idea. The rest is a hosting provider's setup, and modern ones do it from a git repository in a few clicks.

Do it with one page

Not an application. One page that says your name and today's date.

  • Put it in a git repository and push it to GitHub.
  • Connect that repository to a host with a free tier.
  • Open the URL it gives you, on your phone.

Seeing something you wrote answer at a public address is the moment the abstraction becomes concrete, and it is worth having before you have anything to lose.

Two things you have now proved

Your git works end to end — local commits reaching a remote. Course 1 assumes this from lesson 1.

You know what "public" means, having just made something public. That connects directly to unit 3: everything the browser receives, the visitor can read. You have now been on both sides of that sentence.

What course 1 assumes you have

A checklist, so nothing there is a surprise:

  • Editor, Node, git installed and checked.
  • Comfortable with pwd, ls, cd, and reading an error.
  • git init/add/commit/log/diff, and a repository pushed to GitHub.
  • You can read a function, an object, an array, an if and a loop — and say what one does.
  • You have made a real API request, checked a status code, and parsed JSON.
  • You know the difference between client and server, and why a key in client code is public.
  • You can narrow a failure to the smallest case that still breaks, rather than changing things until it works.
  • You can make a branch, merge it, and undo a committed change with git revert.
  • An assistant installed, and you have accepted one change after reading its diff.
  • Something of yours deployed at a URL.

If any line is not true, that lesson is worth another twenty minutes now rather than in the middle of course 1.

What comes next

Course 1 builds a real watchlist: your instruments, your notes, live prices, deployed. It moves faster than this course because the assistant does the typing — and you will be reading everything it writes.

Try it now

Deploy the page, then open it on a device that is not your computer. Then go through the checklist honestly and fix anything that is not true. Starting course 1 with all ten lines solid is the difference between a course that teaches you and one that fights you.