Removing status.nixos.org (only static html/css/js) #137
Conversation
also: - status.nixos.org/prometheus -> prometheus.nixos.org - status.nixos.org/grafana -> grafana.nixos.org
|
I'd prefer keep grafana and prometheus on the same domain, with a path. This is in case more tools get put up or something to that effect. |
|
@grahamc why would be a bad idea having each tool per subdomain? We don't know what the future holds and we don't want to paint our-self again in the corner like we did with nixos.org and status.nixos.org. I don't think it costs us anything. On the other side I'm fine with what ever is decided. I thought I would bring this up. |
|
Would my "4 step" plan create any (significant) downtime? |
|
@grahamc Maybe you didn't know but @edolstra moved DNS servers to Netlify as well and it is a single click to add more. Even sharing the access to this is now possible. But yeah, if you still dont like it, i'll use monitoring.nixos.org domain. Can you be more specific where about prometheus and grafana URL? |
|
Ah, nice. However, I would still prefer a single domain for now. Let's do monitoring.nixos.org/prometheus, monitoring.nixos.org/grafana and the root page can be trivial redirect to status.nixos.org where we can maintain the index. |
|
PR updated to use |
From now we should serve them at the same time, but we will remove this in the next steps. For more please refer to #137
|
Update:
|
|
Merged master since #138 was merged and deployed. Next step is to verify that everything works before pointing status.nixos.org to nixos-status.netlify.app. That would mean that everything is working we just need to do the cleanup. @grahamc Can you verify that Grafana and Prometheus are working correctly under new domain. |
|
I moved further and redirect status.nixos.org domain at netlify. Now all that needs to be done is a clean up. |
|
@edolstra this PR is now ready to be merged and eris redeployed. |
|
I tranfered all the issues/prs to nixos-status repo. I consider this migration done. |
because it is being moved to a separate repository (https://github.com/nixos/nixos-status) to be deployed to Netlify, like we are already doing for https://nixos.org and https://search.nixos.org.
Why
The reason for this change was that we want to add similar design to https://status.nixos.org as we have it on https://nixos.org. For that it would be nice to have similar workflow as we already have for https://github.com/nixos/nixos-homepage and https://github.com/nixos/nixos-search. And who knows maybe that would allow us to improve https://status.nixos.org page even further.
As we did with https://nixos.org the point of moving is not to move it to Netlify, but to make https://status.nixos.org a static website that we can deploy anywhere. The reasons why Netlify was selected was already discussed when we had this discussion regarding moving https://nixos.org.
How
And as it was the problem with https://nixos.org the migration is not as straightforward as we would like. We will have to move this in few steps:
1. Point monitoring.nixos.org to eris's IP (like we currently do for status.nixos.org)
2. Serve https://status.nixos.org/prometheus and https://status.nixos.org/grafana under subdomain alongside existing domain. The proposed subdomain: https://monitoring.nixos.org/prometheus and https://monitoring.nixos.org/grafana. Serve grafana and prometheus under monitoring.nixos.org #138
3. Move status html/js/css to a static page and deploy to Netlify. We need to create proxy for
/grafanaand/prometheuswhich point to subdomain. proxy /grafana and /prometheus nixos-status#34. Change DNS for status.nixos.org to point at Netlify.
5. Remove status html/css/js and remove serving status.nixos.org with erin. This PR, Removing status.nixos.org (only static html/css/js) #137.
6. Move any issues regarding status page to https://github.com/nixos/nixos-status.
Have I missed something?