Migrate CI to GitHub Actions

[stv0g]

Changes

• Replaces deployment to EONERC Kubernetes with deployment to GitHub pages
• Removes building of container images
• Updates references to git.rwth-aachen.de to GitHub
• Updates VILLASnode submodule
• Removes documentation for old api node-type (Remove api node type documentation #139)

[leonardocarreras]

Hi @stv0g! Looks nice, I think there are just few comments that you might want to think about.

[leonardocarreras]

how are we going to deploy it now to fein?

[steffen-vogel-opalrt]

Its only going to be deployed to GitHub pages. We then update the DNS-CNAME record of villas.fein-aachen.org to point to the GitHub servers.

@leonardocarreras @al3xa23 Could you take care of this? I believe Stefan Lankes has the credentials to the Hosteurope customer interface where those settings can be changed.

[leonardocarreras]

@stlankes should we talk to you separately?

[al3xa23]

Nice work, thanks :)

What do we do about the devcontainer when the Dockerfile is not longer available? Just asking because I use the devcontainer for local testing.

[leonardocarreras]

Nice work, thanks :)

What do we do about the devcontainer when the Dockerfile is not longer available? Just asking because I use the devcontainer for local testing.

I understand that it still should work from the file devcontainer.json

Optional would be to decide how/if the help keeps info about how to use it

[al3xa23]

I think we need something like this for devcontainer. We would use the node-js as image where all yarn commands can be run:
{ "name": "VILLASdocumentation", "image": "node:23.11-bookworm", "forwardPorts": [ 3000 ], "portsAttributes": { "3000": { "label": "Development Server", "onAutoForward": "openBrowserOnce" } }, "remoteUser": "node" }

Let me know what you think. If it is okay, I can commit here or make a new PR.

[stv0g]

Hi @al3xa23 @leonardocarreras,

I think having a separate Dockerfile is a bit overkill. It was mostly used to build an image which we can deploy in the EONERC Kubernetes for hosting the webpage.

The approach proposed by Alexandra should work too.