Dev Setup for 2017.foss4g.org Jekyll Site

[gsteinmon]

Hi

We are working on developing a full conference site using Jekyll (​https://jekyllrb.com/). Can you please provide us a place where we can upload our code and test our site for the development process.

Should we tie this to a git repo on the gogs site?

[strk]

Putting the code on Gogs sounds like a great idea to me. As for the space, I dunno what a good place to set that up would be. Maybe "webextra" ?

Alex, Martin ?

[martin]

Webextra is one of the more recent setups, at least it's running Debian7, therefore it looks like one of the preferred places to me.

[strk]

Martin, can you map dev.2017.foss4g.org to webextra ? Then we'll need to configure the web server and finally a git hook to publish data there

[strk]

Guido please drop here a link to the Gogs repository containing the code

[gsteinmon]

Replying to strk:

Guido please drop here a link to the Gogs repository containing the code

I don't have code yet, but here is a link to the jekyl repo which has a lot of code for testing: ​https://github.com/jekyll/jekyll

sorry for my delay on responding to this.

[strk]

I'd ask you to provide, in the same tree with the sources, instructions about how to generate/update the static files from the source files. And maybe also a Makefile to automate the process.

[gsteinmon]

Hey strk,

My apologies for lagging on my reply.

I have posted the current site up to gogs.

This runs very slowly.

So, this original site is static. Our new design uses Jeykll and is currently being generated when we push to github. I take it Gogs cannot do this, is that accurate?

Replying to strk:

I'd ask you to provide, in the same tree with the sources, instructions about how to generate/update the static files from the source files. And maybe also a Makefile to automate the process.

[strk]

Does "runs very slowly" refer to the current foss4g website or the Gogs service ?

Gogs, by itself, does not have provision for hosting websites, but does support specifying an url to hit or a command to run upon pushing to a repository. Both mechanisms could be used to automatically generate and publish updates for the website, but some work is needed to put things togheter. Are you up to play with that ? I'm happy to help.

[strk]

For the record, some Jekyll deploy methods are documented here: ​https://jekyllrb.com/docs/deployment-methods/

And, I guess the current website is here: ​https://git.osgeo.org/gogs/FOSS4G-Boston-2017/foss4g2017-web

If you are happy with your current github setup this ticket can be closed

[gsteinmon]

I am fine and happy to leave the site up on github, but I have been asked to bring things into the osgeo stack. The gogs repo is correct, but don't you need to have th Git post-update hook setup? Do I have the power to do this?

[strk]

You don't have power to automatically install a git post-update hook, as that would give you the ability to run arbitrary unix commands as the user running the service. But you should have the power to setup *web* hooks upon pushes (for example).

Can you setup the receiving side for a web hook ?

[EliL]

Replying to gsteinmon:

I am fine and happy to leave the site up on github, but I have been asked to bring things into the osgeo stack. The gogs repo is correct, but don't you need to have th Git post-update hook setup? Do I have the power to do this?

You can confirm on the Conference list, but I think the Conference Committee's perspective is to use whatever works best for the LOC. At the end or after, the LOC will be expected to provide some html archive that can often be created with wget or HTTrack.

SAC may have other technical requirements and that is a separate matter.

[gsteinmon]

oh, I think there was also a request that the site be served as https, I figured this was something that needed to happen through gogs?

[EliL]

https instead of http could probably be achieved multiple ways with either setup.

If your goal is https I'm not sure that gogs is the first logical step. They are separate issues about different things but you can probably discuss to sort them out and then pursue either or both of them.

But those aren't Conference Committee issues so I'll step aside.

[strk]

If you want OSGeo to serve via web (http and https) the development version we need to map dev.2017.foss4g.org to webextra (but it looks like we're short on sysadmin volunteers to do that)

[gsteinmon]

ok, I guess we will continue to use github. Once the event is over we will use the github repo to stand up a version of the site that will stay static and is hosted by osgeo.