@1boiledpotato It’s just the server getting overloaded, only thing to do is wait for it to come back up.
@1boiledpotato It’s just the server getting overloaded, only thing to do is wait for it to come back up.
@GregorTacTac If you use containers you can map something like 8080 on the host to 80 in the container. Generally it’s recommended to have a reverse proxy listening on 80 and 443 with all your individual applications on localhost only high ports.
@Tippon That is a big part of the point behind containers, you don’t have any long term state inside them. Migration is just a case of copying the configuration over along with the contents of any persistent volumes.
It’s worth looking into Podman instead of Docker, the daemon-less architecture makes it more lightweight and secure as it’s easier to have rootless containers. Management can also be easer as being a Red Hat project it integrates well into Systemd.
With your existing server on Xubuntu you may as well stick with Ubuntu Server or Debian for the familiarity.
@AVincentInSpace The template system is a big part of that since it makes active collaboration much easier, as long as the template authors are talking to each other then the rest of the community will automatically get new orders whenever they need to reload the page.
For example that battle was originally planned along the other diagonal, before being flipped in a deal with the osu! logo. Same thing happened later on with the Rocket League logo being moved from where the blue portal is.