[REQ] sutd-athletics.opensutd.org

[11Keng11]

Project Info

Source URL if any:

Link to repository URL:
https://github.com/11Keng11/sutd-athletics

DNS records needed
CNAME

name: sutd-athletics.opensutd.org
value: sutd-athletics.github.io

Brief description of the project
A short description of what the page is about:
Our athletics fifth row would like to host a website for an event we are going to hold.

Project owners
Tag project owners (@username) : @11Keng11

[tlkh]

DNS has been configured.

Please go to your repo and set the custom domain to sutd-athletics.opensutd.org. If you are using GitHub pages, you may need to republish the page for it to take effect (e.g. edit the README file or do something to get the site to rebuild)

[11Keng11]

So sorry for the inconvenience, but could you change the dns records to this.

DNS records needed
name: sutd-athletics.opensutd.org
value: 11Keng11.github.io/sutd-athletics/

[tlkh]

done

[jamestiotio]

Hi @11Keng11. Just to clarify, the DNS records have been changed to direct to 11Keng11.github.io instead of the subdirectory that you have specified.

A CNAME DNS record is unable to point to a subdirectory because DNS records only map IP addresses to hostnames.

Several options that you could consider to potentially undertake:

1. Deploy your site statically on the specified repository’s GitHub Pages and add a CNAME file with the subdomain URL: sutd-athletics.opensutd.org (follow the instructions here). I personally recommend this since it’s the least of a hassle with your current setup. Do ensure that you have no other deployed GitHub pages in your other repositories with the same CNAME so as to avoid conflicts.
2. Set up a redirect on your 11Keng11.github.io repository to redirect to the specified subdirectory.
3. Move your sutd-athletics repository into your 11Keng11.github.io repository.
4. Set up a separate GitHub organization for sutd-athletics, create a new repository there so that we can point the DNS records to sutd-athletics.github.io and inform us of the new repository to point the DNS records to.
5. Deploy your site on a cloud service such as Netlify and let us know the Netlify subdomain URL that you have deployed your site to.

Cheers!