search

OpenSourceEcon / oselab

Open Source Macroeconomics Lab Webpage built in Flask
9 stars 7 forks source link

Publishing to oselab.org #47

Closed rickecon closed 5 years ago

rickecon commented 5 years ago

@asmockler . Heroku site looks good. What do you need to publish that to oselab.org? The current setup with the new images should be sufficient for me to start advertising the boot camp. I didn't understand the following request of yours.

You will need to add CNAME records for the following:

@ -> fluffy-lobster-7muh4gllrlhqqjtcdho0dqsu.herokudns.com. www -> tropical-carnotaurus-bu1eiejtjamgv6axld6ev4so.herokudns.com.

Let me know once that is done and I will double check that SSL is working.

Let me know what you need from me for the oselab.org domain.

hayleefay commented 5 years ago

@rickecon -- You basically need to tell the domain that you bought that it is going to display the content that is at those URLs that Andy sent. The way to do that is to set up a CNAME record and an A record. Did you buy the domain from google domains? If so, this should be helpful.. Specifically the "How to set custom resource records" section.

@asmockler -- "Fluffy Lobster" is the best automated domain I have ever seen.

rickecon commented 5 years ago

From domains.google.com, I was able to get the CNAME custom resource record www -> tropical-carnotaurus-bu1eiejtjamgv6axld6ev4so.herokudns.com, but I couldn't get the A custom resource record @ -> fluffy-lobster-7muh4gllrlhqqjtcdho0dqsu.herokudns.com. The error said "Invalid data". @asmockler @hayleefay any ideas? screen shot 2019-02-19 at 2 28 23 pm

asmockler commented 5 years ago

Use CNAME for both – so just change A to CNAME in your screenshot

rickecon commented 5 years ago

CNAME also doesn't work for fluffy-lobster-7muh4gllrlhqqjtcdho0dqsu.herokudns.com. The error is "CNAME records for the root domain are not supported". @asmockler screen shot 2019-02-19 at 2 33 44 pm

asmockler commented 5 years ago

Oh yeah, I forgot that google doesn't allow that. Ok, skip the fluffy lobster on (unfortunately) and add a redirect. Above that section, there is a section called "Synthetic records." Do a subdomain forward from @ to www.oselab.org. Choose permanent redirect, forward path, and enable SSL. If it lets you do that, then we should be good to go

asmockler commented 5 years ago

(P.S. https://www.oselab.org is working! Just gotta get the root domain working as well)

rickecon commented 5 years ago

Ugh. "The SSL Certificate for this domain hasn't been created yet. This process may take up to 24 hours to complete." In this screenshot, I am showing the error I got as well as the inputs I gave in the gray panel. Any suggestions @asmockler? screen shot 2019-02-19 at 2 41 58 pm

asmockler commented 5 years ago

Eh, just edit it and disable SSL. I think we can still force it elsewhere and it isn't super necessary for what is there right now.

asmockler commented 5 years ago

It looks like the forwarding rule ends up on SSL after the redirect already, so it is fine to disable it.

rickecon commented 5 years ago

Do I just edit the subdomain forward to disable SSL? Everything else the same?

asmockler commented 5 years ago

Correct

rickecon commented 5 years ago

OK. All looks good. What next?

rickecon commented 5 years ago

Looks like we're good on this issue.