A lot of confusion in this field comes from taking a name at face value. origin sounds like it means something. A server that "isn't working" sounds like one problem. Day 26 was two tasks where the useful move was to stop trusting the label and go look at the thing itself.
One Git task, one AWS task. Manage the remotes on a repository, then configure an EC2 instance as a web server with Nginx. The tasks come from the KodeKloud Engineer platform.
Remotes: a nickname for a URL, and nothing else
A remote is not a connection. It is not a sync relationship. It is a name stored in a config file that maps to a URL. That is genuinely all it is.
git remote # names only
