Git pages
The various git remote systems have different approaches to allowing
published pages on their systems.
All these systems use git as a foundation, then add a UI over the top to show the content of remote repositories
codebergOn codeberg, we simply need to make a git branch called
pages and push our web content to it.
The web is made up of tons of computers that ‘host’ web content. The individual machines that make up the web can be as simple as your home computer, your laptop or even your smartphone.
Because of residential power restraints and network connectivity, it is unfortunately not all that simple to set up your own server at home, but it is possible!
More than likely, the websites you visit are hosted in server farms that consume tons of electricity, not only for keeping all the ‘server’ machines on, but also for cooling this infrastructure.

In short, what codeberg (or github, gitlab, bitbucket, etc) does to
serve pages, is that they give us access to a portion of their web
server that is configured (using server software, probably
Apache or nginx) to listen to web requests and
serve web pages based on these requests.
Like a phone call: your computer (the client) makes a request to the host (the server) for various content, using the HTTP protocol.
HTTP = HyperText Transfer protocol
The basics of HTTP are still in place today, but we tend to use HTTPS for any secure transactions. The only difference is that transactions between client and server are encrypted.
By default, web servers will start by serving pages called
index.html, so with codeberg, you need that page, or
nothing will be served.
You can purchase web-serving products, some are very simple and cheap, others are very complex and expensive. It will depend on the amount of computation you want to do.
FTP = File Transfer Protocal
In Git, a branch is a new/separate version of the main repository.

Branches are an excellent way to test an idea, work on a new feature, or show a proposal, while maintaining the advantages of a versioned and backed-up system.
See the practical 8 document for a list of the procedure to create a checkout a branch
In our case, we will use branches in a slightly unconventional manor.
We want our main branch to be a mirror of our
pages branch.
To get codeberg to ‘host’ your code, all you need to do is to create
a pages branch, and make sure it has your
index.html file, plus any other /assets your
project/site relies on.