Different take on a GitHub Project – DynDNS/Redirects

Hi CoolGithubProjects!

im not sure if this is the right home and sure someone will tell me if it isnt. so, I use GH a lot for work and a bit personally – and I have been sitting on a domain I bought a few months back trying to think of a project to use it. naturally, this idea had to have something to do with GitHub.

so i made this thing: https://src.ms/start

basically dev's can get short names on a few domains (src.ms, 3nx.dev, mygit.uk, etc) and can either:

• point them at an IP that changes (dyndns, updates go through cloudflare, usually live in a few seconds)
• or just redirect them somewhere (301/302, the service handles it so you don’t mess with certs)

the whole point for me was that i wanted something i could drive from a script or CI without fighting a web UI. so the API is deliberately dumb and curl-friendly – one endpoint does create/update, you just PUT a json blob with a bearer token. keys are scoped read-only or read/write. nothing fancy.

login is github oauth only (no password forms, or security leaks/hacks). analytics for the redirect campaigns are server-side only, no client trackers, just the usual country/asn/time stuff.

it’s still in beta and gated behind a waitlist. if anyone wants to poke at it and tell me what’s broken or missing, i’ll give permanent free pro-level accounts to people who actually use it and give feedback. I added a bug log into the GUI for ease of reporting. https://src.ms/betatest

anyway… yeah. that’s it. happy to answer questions or take “this is stupid, do it this way instead” comments. or tell me to go …. off! All good! 😉

Cheers,

Iscanic

Github : https://src.ms/iscanic