deployment infrastructure

[jrochkind]

Decided to go heroku

• [x] set up professional dynos
• [x] custom domain

~heroku may be acceptable, we believe 1 to 2 standard-1x dynos will be sufficient, at $25-$50 a month.~

~One standard-1x is likely sufficient under ordinary circumstances, but we recommend 2 because heroku standard-1x dynos run on shared hardware, and performance can vary. With two, if one gets pokey the other one is there to pick up the slack.~

~If we are not going to deploy on heroku, we need to make sure to reserve 8-12 hours (as originally estimated) for working on setup of deployment infrastructure and scripts on fordham hardware.~

[jrochkind]

@tkaczorowski I assume you'll want a custom domain for the app, perhaps search.law.fordham.edu? You'll need to get your local people to set up the DNS to point to heroku.

Instructions from heroku are here: https://devcenter.heroku.com/articles/custom-domains

But I think we might want to switch the dynos to being owned by you, and billed as 'professional' dynos, in case there would be configuration changes as a result of the switch. Would you like to work on that next week?

[jrochkind]

@tkaczorowski I have moved the heroku app over to the 'bento-dev' team you created (personally I would have put 'fordham' in the name, but you can probably change it if you want).

I have set it up to use 2 Professional Standard-1X dynos, so you will start getting billed $50/month, probably starting today, to the billing info you have registered with heroku.

[jrochkind]

@tkaczorowski PS: You should see the "sometimes the response is very slow" problem go away as of now, since we are on Professional instead of Free dynos now.

[jrochkind]

I have also tuned the "max threads" configuration on our new heroku dynos, to try to get the highest request handling throughput capability within the RAM offered by the Standard-1X dynos. Puma max threads is currently set to 12.

[jrochkind]

@tkaczorowski new url for heroku app!

Because it is moving toward not being a 'demo', I have renamed it to take 'demo' out of the heroku app name. Which changes where you will access it to:

http://fordham-law-search.herokuapp.com/

[jrochkind]

@tkaczorowski Here are instructions for DNS.

If you want search.library.law.fordham.edu, you need to tell your DNS admins to set up a DNS CNAME record, from search.library.law.fordham.edu, pointing to search.library.law.fordham.edu.herokudns.com.

If you want another hostname, it would follow that same pattern, but you'd just have to let me know so I can configure on the heroku end.

More info (which you shouldn't need) is available here: https://devcenter.heroku.com/articles/custom-domains

Once the hostname is in place, i can set up https/SSL, so let me know!

[tkaczorowski]

Great! Thanks!

Tom

From: Jonathan Rochkind [mailto:notifications@github.com] Sent: Thursday, December 15, 2016 3:11 PM To: Fordham-lawlib-bento/fordham-law-search < fordham-law-search@noreply.github.com> Cc: tkaczorowski tkaczorowski@law.fordham.edu; Mention < mention@noreply.github.com> Subject: Re: [Fordham-lawlib-bento/fordham-law-search] deployment infrastructure (#24)

@tkaczorowski https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_tkaczorowski&d=DgMFaQ&c=aqMfXOEvEJQh2iQMCb7Wy8l0sPnURkcqADc2guUW8IM&r=ufwSdmS5IZPSMZUMObqD9D-VUZ9gAg0GtO2ab7PNYjU&m=F06pzFJSuUzI-Vq3JekgrxDzILEQiUyByKjxskTRULQ&s=lX9RiGvld1Ce9feYxwSMyn-GoEK8IFoKM4Z8Hyt92Uo&e= new url for heroku app!

Because it is moving toward not being a 'demo', I have renamed it to take 'demo' out of the heroku app name. Which changes where you will access it to:

http://fordham-law-search.herokuapp.com/ https://urldefense.proofpoint.com/v2/url?u=http-3A__fordham-2Dlaw-2Dsearch.herokuapp.com_&d=DgMFaQ&c=aqMfXOEvEJQh2iQMCb7Wy8l0sPnURkcqADc2guUW8IM&r=ufwSdmS5IZPSMZUMObqD9D-VUZ9gAg0GtO2ab7PNYjU&m=F06pzFJSuUzI-Vq3JekgrxDzILEQiUyByKjxskTRULQ&s=Pamzxc_PjuaELbC7ue4daxUdj-J1jReYp4fAe-JxEnw&e=

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_Fordham-2Dlawlib-2Dbento_fordham-2Dlaw-2Dsearch_issues_24-23issuecomment-2D267431056&d=DgMFaQ&c=aqMfXOEvEJQh2iQMCb7Wy8l0sPnURkcqADc2guUW8IM&r=ufwSdmS5IZPSMZUMObqD9D-VUZ9gAg0GtO2ab7PNYjU&m=F06pzFJSuUzI-Vq3JekgrxDzILEQiUyByKjxskTRULQ&s=7i0E6wtaeUnJcZ__td0EQE0l43etOL5na1dBzFBABTE&e=, or mute the thread https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AOW-2DfujLuiylkJh0lmy8EDqAKbrKmiR6ks5rIZ7egaJpZM4K0OeC&d=DgMFaQ&c=aqMfXOEvEJQh2iQMCb7Wy8l0sPnURkcqADc2guUW8IM&r=ufwSdmS5IZPSMZUMObqD9D-VUZ9gAg0GtO2ab7PNYjU&m=F06pzFJSuUzI-Vq3JekgrxDzILEQiUyByKjxskTRULQ&s=8P3hqhiQkzPFo8Sc7ITQJuzQr0LCppNz56V4cnwKhLE&e= .[image: Image removed by sender.]

[tkaczorowski]

CNAME should have been done by University IT. Please test and notify me of result. Thanks.

[jrochkind]

Tom, what DNS name did you settle upon?

I thought it was search.library.law.fordham.edu, but I'm still not finding that registered in DNS. My browser can't find it, and it is not showing up using DNS lookup tools.

Did you decide on a different hostname?

[tkaczorowski]

Hi Jonathan,

Sorry for the confusion. Our staff didn’t like having another node in the url.

The hostname is librarysearch.lawnet.fordham.edu and points to librarysearch.lawnet.fordham.edu.herokudns.com https://urldefense.proofpoint.com/v2/url?u=http-3A__librarysearch.lawnet.fordham.edu.herokudns.com&d=DgMFaQ&c=aqMfXOEvEJQh2iQMCb7Wy8l0sPnURkcqADc2guUW8IM&r=ufwSdmS5IZPSMZUMObqD9D-VUZ9gAg0GtO2ab7PNYjU&m=55fFtPh4NY3W6Ud1i5d3WPToFyXWCC_o9UnlzUjh7qw&s=EgM27r96ETM7zrCrE7KpMVoVC1K4PsYWCJ32PXCs7Ck&e=

Let me know if there are further problems.

Tom

From: Jonathan Rochkind [mailto:notifications@github.com] Sent: Tuesday, January 31, 2017 6:06 PM To: Fordham-lawlib-bento/fordham-law-search < fordham-law-search@noreply.github.com> Cc: tkaczorowski tkaczorowski@law.fordham.edu; Mention < mention@noreply.github.com> Subject: Re: [Fordham-lawlib-bento/fordham-law-search] deployment infrastructure (#24)

Tom, what DNS name did you settle upon?

I thought it was search.library.law.fordham.edu, but I'm still not finding that registered in DNS. My browser can't find it, and it is not showing up using DNS lookup tools.

Did you decide on a different hostname?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_Fordham-2Dlawlib-2Dbento_fordham-2Dlaw-2Dsearch_issues_24-23issuecomment-2D276522583&d=DwMFaQ&c=aqMfXOEvEJQh2iQMCb7Wy8l0sPnURkcqADc2guUW8IM&r=ufwSdmS5IZPSMZUMObqD9D-VUZ9gAg0GtO2ab7PNYjU&m=XIm3sJTgpc1OaYeGLYAdlynxoJs_CUpzTUMNJQtsct8&s=_OsLZOoyKGVELuGq1WD3EJxf_tG5sJXoCsjqgK4UkPY&e=, or mute the thread https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AOW-2DfqJD-2DRmjE-2DAGAzWyhw9BS1oFh1GNks5rX75HgaJpZM4K0OeC&d=DwMFaQ&c=aqMfXOEvEJQh2iQMCb7Wy8l0sPnURkcqADc2guUW8IM&r=ufwSdmS5IZPSMZUMObqD9D-VUZ9gAg0GtO2ab7PNYjU&m=XIm3sJTgpc1OaYeGLYAdlynxoJs_CUpzTUMNJQtsct8&s=Dz1DUFw4YytQ-vMAwkBMQVmC57Vb5dXdW-ESUmJhHfM&e= .[image: Image removed by sender.]

[jrochkind]

Great, the custom domain is working, and also now has ssl/https:

https://librarysearch.lawnet.fordham.edu/

Please note that embed URLs can and should be updated as well: <script src="//librarysearch.lawnet.fordham.edu/search-embed.js" async></script> The // at the beginning of the URL does work now, and is recommended, so the embed will work without browser content warnings on both http and https host pages.

The SSL cert was obtained from letsencrypt.com, using the letsencrypt-rails-heroku gem.

There is a heroku scheduled task I created that periodically renews the cert with letsencrypt, per instructions in the letsencrypt-rails-heroku gem README.

These things are mentioned in the README for future reference.

[jrochkind]

To be clear, the app will work at either http OR https, both work.

https://librarysearch.lawnet.fordham.edu/ http://librarysearch.lawnet.fordham.edu/

[tkaczorowski]

Hi Jonathan,

The urls and embed are not working for me. “Site can’t be reached” and empty embed.

Do I need to inform Fordham University IT re: DNS?

Thanks,

Tom

From: Jonathan Rochkind [mailto:notifications@github.com] Sent: Wednesday, February 01, 2017 2:58 PM To: Fordham-lawlib-bento/fordham-law-search < fordham-law-search@noreply.github.com> Cc: tkaczorowski tkaczorowski@law.fordham.edu; Mention < mention@noreply.github.com> Subject: Re: [Fordham-lawlib-bento/fordham-law-search] deployment infrastructure (#24)

To be clear, the app will work at either http OR https, both work.

https://librarysearch.lawnet.fordham.edu/ http://librarysearch.lawnet.fordham.edu/

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_Fordham-2Dlawlib-2Dbento_fordham-2Dlaw-2Dsearch_issues_24-23issuecomment-2D276764442&d=DwMFaQ&c=aqMfXOEvEJQh2iQMCb7Wy8l0sPnURkcqADc2guUW8IM&r=ufwSdmS5IZPSMZUMObqD9D-VUZ9gAg0GtO2ab7PNYjU&m=oHBkX7KVKP_mxh4MPK0Y9rHF4vzVg6C3AmxgDviiMqc&s=eEVM4LeOSZBVS9edfbynU12cMTYGhWQ0p2Wj_x24ANk&e=, or mute the thread https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AOW-2DfuiLdpd0oduylBj-5FwCV5hQf36c0oks5rYOPdgaJpZM4K0OeC&d=DwMFaQ&c=aqMfXOEvEJQh2iQMCb7Wy8l0sPnURkcqADc2guUW8IM&r=ufwSdmS5IZPSMZUMObqD9D-VUZ9gAg0GtO2ab7PNYjU&m=oHBkX7KVKP_mxh4MPK0Y9rHF4vzVg6C3AmxgDviiMqc&s=Ukppkt0302bdJT2Iwm0GrQO5wQ2x8KMeCkDvnYhCBq4&e= .[image: Image removed by sender.]

[jrochkind]

Tom, are you saying that going to http://librarysearch.lawnet.fordham.edu/ does not work for you?

That's very odd, it works for me.

It sounds like a DNS caching problem, but that's surprising to me if you are on campus, since you should be using campus DNS, and the campus DNS is the one that had to be changed to make this work for me too!

If you have a mobile device, can you try accessing http://librarysearch.lawnet.fordham.edu/ from your mobile device not on wifi but using cellular data? That way you'll be using a different network and different DNS -- it should work.

You could also try changing your workstation DNS to 8.8.8.8 (google's free dns), which should make both direct access and embeds work.

The CNAME record they created seems to be set up fine as far as I'm concerned -- it works for me. So I think it is a local DNS problem of some kind you should talk to your local IT about, but it's not a problem creating the CNAME record, that seems to created properly.

Ah, I'm remembering that at JHU they sometimes had different 'internal' and 'external' DNS, and when we asked them to create a record, they would sometimes create it in one but not the other. If Fordham is similar, perhaps they created the CNAME in 'external' DNS but not 'internal'?

[tkaczorowski]

Looks like the problem was the DNS I was using – I don’t know if it was University or the Law School DNS. Probably the latter.

I changed my config to use 8.8.8.8 and I get to the search and see the embed in IE. It doesn’t work yet in Chrome which seems to be caching even though I see the change in view source.

Tom

From: Jonathan Rochkind [mailto:notifications@github.com] Sent: Wednesday, February 01, 2017 3:59 PM To: Fordham-lawlib-bento/fordham-law-search < fordham-law-search@noreply.github.com> Cc: tkaczorowski tkaczorowski@law.fordham.edu; Mention < mention@noreply.github.com> Subject: Re: [Fordham-lawlib-bento/fordham-law-search] deployment infrastructure (#24)

Tom, are you saying that going to http://librarysearch.lawnet.fordham.edu/ does not work for you?

That's very odd, it works for me.

It sounds like a DNS caching problem, but that's surprising to me if you are on campus, since you should be using campus DNS, and the campus DNS is the one that had to be changed to make this work for me too!

If you have a mobile device, can you try accessing http://librarysearch.lawnet.fordham.edu/ from your mobile device not on wifi but using cellular data? That way you'll be using a different network and different DNS -- it should work.

You could also try changing your workstation DNS to 8.8.8.8 (google's free dns), which should make both direct access and embeds work.

The CNAME record they created seems to be set up fine as far as I'm concerned -- it works for me. So I think it is a local DNS problem of some kind you should talk to your local IT about, but it's not a problem creating the CNAME record, that seems to created properly.

Ah, I'm remembering that at JHU they sometimes had different 'internal' and 'external' DNS, and when we asked them to create a record, they would sometimes create it in one but not the other. If Fordham is similar, perhaps they created the CNAME in 'external' DNS but not 'internal'?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_Fordham-2Dlawlib-2Dbento_fordham-2Dlaw-2Dsearch_issues_24-23issuecomment-2D276780400&d=DwMFaQ&c=aqMfXOEvEJQh2iQMCb7Wy8l0sPnURkcqADc2guUW8IM&r=ufwSdmS5IZPSMZUMObqD9D-VUZ9gAg0GtO2ab7PNYjU&m=JXp1eW62fq4fQ8wQvNowCV38LF7kTQVKBiwpe1EzM2w&s=VyFX5QokGWqUZwD48f13zj4O2L7TmboYM4JR_twAb-M&e=, or mute the thread https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AOW-2Dfl3NQNWcP-5FZzVGZpOdkNAB889GSqks5rYPIhgaJpZM4K0OeC&d=DwMFaQ&c=aqMfXOEvEJQh2iQMCb7Wy8l0sPnURkcqADc2guUW8IM&r=ufwSdmS5IZPSMZUMObqD9D-VUZ9gAg0GtO2ab7PNYjU&m=JXp1eW62fq4fQ8wQvNowCV38LF7kTQVKBiwpe1EzM2w&s=A6g5DL0fd1bUFu0oM0UeHFOS1xwPQD2Q-MgSDmlhoTI&e= .[image: Image removed by sender.]

[jrochkind]

Whatever DNS you were using may be caching longer than it ought to.

Windows also sometimes caches, and Chrome may have it's own cache. To be sure you aren't using any DNS caches, reboot.