Hosting

[patrickbkr]

Open discussion on how to best host the RCB.

Requirements:

• Can be run in a container, but needn't be.
• Requires a persistent Postgres DB.
• Requires a Rakudo and a set of modules among them the Cro stack, Red, LibXML and WebService::GitHub. LibXML requires the libxml dev libs to be installed.
• A TLS reverse proxy is probably a wise choice. (Could be an Nginx or or something else.)
• Currently stores sources and build logs indefinitely. Ticks in at about 32MB per test run. Sooner or later we'll need to implement some form of cleanup. 100GB of disk space will give us ~3000 test runs.
• Needs to be accessible via a stable domain name to be able to use GitHub hooks.
• A nice URL to make the web interface available could be https://cibot.rakudo.org/. Bikeshedding allowed.
• Some kind of orchestrator that auto-restarts the service should it die is wise to have. The minimal solution could be a systemd service file, kubernetes is most certainly overkill. Some raku and rakudo infra currently already is deployed on portainer, so maybe just stick with that.

Ping @rba

[patrickbkr]

I have set up a temporary installation on a temporary server living at https://whoop-rcb.site/.

[patrickbkr]

Given it seems like going live is not so far away, can someone with access to do so point cibot.rakudo.org at 116.203.185.29 / 2a01:4f8:1c1e:e72e:: ? I think it's strategically unwise to do the live start with a domain name that is only temporary. (The server is turned off at the moment, the IPs are correct nonetheless.)

The server is just as temporary, but switching the server doesn't bring back-compat issues with it.

Also if someone has a better idea for a domain name, then now would be a good time to say so.

Who's the right person to ping? @rba @maettu

[lizmat]

@rba said he'll do it tomorrow.

[rba]

@patrickbkr, I have configured DNS as you requested. My you check if this working now?

[patrickbkr]

@rba: Thanks a lot! I think I'll manage to try in the coming days.

[patrickbkr]

@rba The domain works. I have reconfigured the installation to work with the new domain. I think I'll patch the installation to not report results back to Github yet, but run on the live repos otherwise.