Make the site go live

Issue #7 resolved
Fredrik repo owner created an issue

The site should have gone live on aug 25th, so it is already too late.

Depends on:

  • Issue #6, and all the pull requests
  • Login-details for one.com (the rumor has it that @tuggertron already has those?)
  • Cron-job/pinging-utility checking in on the site at least once an hour so the Heroku Dyno doesn't go to sleep.
  • A Heroku Dyno running from Europe (the current one is in the US).

What should be done:

  1. Set up new Heroku Dyno in Europe -> http://stormy-headland-2241.herokuapp.com/
  2. Set up custom subdomain at Heroku and one.com (bal.blekingska.se for example?)
  3. Make blekingska.se/bal and blekingska.se/bal/ respond with HTTP 302, redirecting the user to bal.blekingska.se.

Comments (2)

  1. Fredrik reporter

    The site is now live: http://bal.blekingska.se/

    The cron-job is running on sartre.kd35a.se:

    */30 * * * * tmp=$(mktemp); wget --timeout 1 --output-document=/dev/null -e html_extension=Off http://stormy-headland-2241.herokuapp.com/ 2>$tmp || cat $tmp; rm $tmp
    

    Would probably be nice with another cron-job somewhere else aswell, and maybe some random time-offset for each run.

  2. Log in to comment