-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rename to usrse.github.io #37
Comments
@christophernhill owns the domain. Given my failed attempt last time, he and I will need to coordinate. Chris, let me know when you have time. |
Thanks @christophernhill ! And please no rush, I know you guys are busy! |
Got it - I'll take a look. Just resurfacing,.,..,
…On Mon, Jun 3, 2019 at 2:38 PM Vanessasaurus ***@***.***> wrote:
Thanks @christophernhill <https://github.com/christophernhill> ! And
please no rush, I know you guys are busy!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#37>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA27DYAKASYIP4T67QAMOQDPYVQIPANCNFSM4HSBM7SQ>
.
|
Small step - http://usrse.org now gives 404!
I think next step is to change
https://github.com/USRSE/usrseweb/blob/gh-pages/CNAME and see what
happens?
…On Mon, Jun 3, 2019 at 3:19 PM Chris Hill ***@***.***> wrote:
Got it - I'll take a look. Just resurfacing,.,..,
On Mon, Jun 3, 2019 at 2:38 PM Vanessasaurus ***@***.***> wrote:
>
> Thanks @christophernhill ! And please no rush, I know you guys are busy!
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub, or mute the thread.
|
On it! I'll triage this since we have 404. |
Actually I can't - I don't own the repo! @cosden we need to rename the repo itself to usrse.github.io, the CNAME is already set with http://usrse.org. |
And @christophernhill just to confirm - you are using the GitHub alias usrse.github.io (and not the old urseweb one?) |
And you can use dig to get the exact addresses: $ dig grads.github.io
; <<>> DiG 9.11.3-1ubuntu1.7-Ubuntu <<>> grads.github.io
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39424
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;grads.github.io. IN A
;; ANSWER SECTION:
grads.github.io. 3600 IN A 185.199.109.153
grads.github.io. 3600 IN A 185.199.110.153
grads.github.io. 3600 IN A 185.199.111.153
grads.github.io. 3600 IN A 185.199.108.153
;; Query time: 20 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Mon Jun 03 18:48:32 EDT 2019
;; MSG SIZE rcvd: 108 |
Sorry I missed this earlier...where are things? I can try renaming the repo anytime to see what happens. Now that I know that I need an empty commit to trigger github to rebuild the page should be a quick and easy experiment. |
If the DNS stuff is taken care of, we should just need a rename (and if necessary) a rebuild. I don’t think it should technically need one, so maybe rename, give 20 mins, and then push a trivial change to try the rebuild. |
Doing now...standby... |
I think we have success! Something I didn't anticipate (or notice last time) but github wouldn't publish from gh-pages, it would only publish from master. So I created it. I changed the default branch to master (from gh-pages). So with that, I see no reason to keep gh-pages around anymore. |
Awesome! Yes correct, only master works in this case. Master can work (along with docs) on any other repo too :) |
And a quick preview of some of the awesomeness- the blog (another repo) lives happily in the same family: And the same will be true for all github pages deployed from org repos! |
This was a success, solid work. Closing issue! |
Doing so will serve the CNAME across the organization, for a common branding.
This will require also changing the DNS record I believe, @cosden you tried this before (and I think we needed to have the DNS changed too?) I'll assign this to you, since you know who controls the domain. And definitely no rush - it will take me a bump and a leap to get the template and then filled in instance for Stanford ready.
The text was updated successfully, but these errors were encountered: