feature(new_mirror): Added a community mirror: zig.savalione.com

[SavaLione]

This adds a new community mirror hosted at zig.savalione.com.

The mirror is powered by a custom Go implementation and an Nginx configuration.
I plan to release the implementation and a guide on how to host a Zig mirror in the future.

I have tested several files and everything appears to be working correctly.
If you encounter any issues, please contact me at savelii.pototskii@gmail.com, and I will address them as quickly as possible.

Thanks for all your work on Zig!

[mlugg]

@SavaLione sorry for the delay in getting to this. The CI indicates you are frequently failing with 504 Gateway Timeout; see https://github.com/ziglang/www.ziglang.org/actions/runs/19148918602?pr=533.

[SavaLione]

Hi @mlugg , it's ok
Apologies for my late reply as well

The 504 timeouts are happening because the server is located in a region with restricted external connectivity (similar to the GFW), though local connections within the region work perfectly.

After the recent push, I noticed that the new mirror still can't pass all mirror checks.
I can do the following:

1. Within a couple of days, I can move the mirror to another server in the region that has fewer connectivity issues with the outside world.
   The new server will also comply with Document IPv4/IPv6 requirements for community mirrors.
   I am happy to do this as long as there are no concerns about these connectivity issues and it aligns with Zig Community standards.
2. Alternatively, the PR can be closed.

Let me know what you think
Thanks!

[mlugg]

After the recent push, I noticed that the new mirror still can't pass all mirror checks.

You can ignore that failure---I'm currently trying to fix some problems with that CI check, sorry! Your mirror might be fine. I'll hopefully rebase this PR again later today on a working version of the "Check Mirrors" action so we can see what the actual status is.

[mlugg]

@SavaLione it looks like zig.savalione.com doesn't have any working DNS records. The CI failure reports error: UnknownHostName, and local tests with curl and dig confirm that (curl says "Could not resolve host", and dig cannot find any A or AAAA records for that domain).

In terms of whether connectivity issues to some parts of the world are okay: it would depend on how common they are.

I'm going to close this PR for now, but feel free to open another one if you can get the DNS issue fixed. Thank you for trying to improve the Zig ecosystem!