Add: git.dpaste.org public instance #68
Loading…
Reference in a new issue
No description provided.
Delete branch "refs/pull/68/head"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
🕺
@Darren this instance is down for at least ~5 days now. Are you sure it should currently be advertised to the public? It's better to be listed when there's enough resources to actively maintain it and keep it online.
Hello, the NVMe I used for this server failed. I'm currently waiting for parts to arrived so I can get it back up and running. I have a backup but not a spare NVMe.
The hardware failed in a horrible way after an unrelated upgrade (technician's fault), currently I'm just trying to get everything off the datacenter that I used.
I think it should not be advertised to the public for the time being, but the good news is the instance will go back online (with all the data intact) once I get the new parts setup & running.
@0ko
It's good to know that you're aware and going to fix this. It would be nice if there was some notice on git.dpaste.org or dpaste.org about this issue instead of complete lack of response from the server. I think it will be easier to wait for the issue to be resolved than removing and re-adding the link, but feel free to open a PR if you wan.t
I've set up git.dpaste.org on a temporary VPS and made a public announcement about the cause of the downtime.
https://git.dpaste.org/dpaste/git-issues/issues/1#issue-344
I've made an announcement regarding downtime on my discord server, which I know now is not enough.
In the future [after the migration to new hardware is completed], I'll setup Atlassian's statuspage so people can easily see & stay informed when a downtime / maintenance happened.
I agree with your 3rd point
For a status page, take a look at uptime-kuma. It is open source and used by Codeberg. It doesn't seem to offer a hosted option, but you can host it on a separate hardware.
I think a mix of both would probably work well, since I already have the license for Atlassian eco system; and I could use uptime-kuma to send the graph / data.
That way statuspage is always up