Make 2017.foss4g.org availabile via HTTPS

[strk]

Using letsencrypt (letsencrypt.org) would have no cost, and setting up a cronjob would make it also a zero-maintainance task.

[strk]

Do you need any help with this ?

[jive]

Think this is a task for SAC

[RPaulW]

Agreed, as this requires shell access to set up the Let's Encrypt client.

[strk]

Ok, looking at it

[strk]

It turns out 2017.foss4g.org is an alias for a github domain which is an alias for a fastylb.net, finally going to a machine which is not in the availability of SAC (or at least, of myself). So if you need help you should give me access to the host at 151.101.52.133 - can you ?

[RPaulW]

I can't. Do we know who set up the site (local committee, conference committee, or other)?

The "search mailing list" link pointing to ​http://osgeo-org.1803224.n2.nabble.com/OSGeo-Conference-Committee-f2078411.html at ​http://www.osgeo.org/conference gives a "Not Found".

[strk]

Meanwhile I've done europe.foss4g.org, which is on OSGeo machines: ​https://europe.foss4g.org/2017/

[strk]

I've filed a new ticket to fix the broken link from /conference page: #1814

[strk]

Regina do you know who did setup 2017.foss4g.org website ?

[gsteinmon]

Hi,

I am the 2017.foss4g.org owner. We are hoping to have a new version out by next week and put the site code into osgeo gogs.

[strk]

The 2017.osgeo.org name points to github pages, who's in charge of maintaining those pages ? It isn't SAC ...

[neteler]

Replying to strk:

The 2017.osgeo.org

You mean ​http://2017.foss4g.org/

name points to github pages, who's in charge of maintaining those pages ? It isn't SAC ...

The normal post-conference process is to archive the conference with httrack at www.foss4g.org (which is webextra).

This archive job should likely be done and the github pages deleted/made invisible/whatever.

[wildintellect]

If the site is hosted out of github and is static. Then we can just take a clone. However we should be careful to acquire any external js, css, fonts as part of the archiving. So maybe httrack mirror and a clone in our git service will be good way to archive both things.

[robe]

It has an https and supports http as well. I frankly see no issue here.