#1802: Dev Setup for 2017.foss4g.org Jekyll Site
---------------------------+-------------------
Reporter: gsteinmon | Owner: sac@…
Type: task | Status: new
Priority: normal | Milestone:
Component: Systems Admin | Keywords:
---------------------------+-------------------
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?
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/1802>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#1802: Dev Setup for 2017.foss4g.org Jekyll Site
---------------------------+--------------------
Reporter: gsteinmon | Owner: sac@…
Type: task | Status: new
Priority: normal | Milestone:
Component: Systems Admin | Resolution:
Keywords: |
---------------------------+--------------------
Comment (by 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 ?
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/1802#comment:1>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#1802: Dev Setup for 2017.foss4g.org Jekyll Site
---------------------------+--------------------
Reporter: gsteinmon | Owner: sac@…
Type: task | Status: new
Priority: normal | Milestone:
Component: Systems Admin | Resolution:
Keywords: |
---------------------------+--------------------
Comment (by 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.
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/1802#comment:2>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#1802: Dev Setup for 2017.foss4g.org Jekyll Site
---------------------------+--------------------
Reporter: gsteinmon | Owner: sac@…
Type: task | Status: new
Priority: normal | Milestone:
Component: Systems Admin | Resolution:
Keywords: |
---------------------------+--------------------
Comment (by 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
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/1802#comment:3>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#1802: Dev Setup for 2017.foss4g.org Jekyll Site
---------------------------+--------------------
Reporter: gsteinmon | Owner: sac@…
Type: task | Status: new
Priority: normal | Milestone:
Component: Systems Admin | Resolution:
Keywords: |
---------------------------+--------------------
Comment (by strk):
Guido please drop here a link to the Gogs repository containing the code
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/1802#comment:4>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#1802: Dev Setup for 2017.foss4g.org Jekyll Site
---------------------------+--------------------
Reporter: gsteinmon | Owner: sac@…
Type: task | Status: new
Priority: normal | Milestone:
Component: Systems Admin | Resolution:
Keywords: |
---------------------------+--------------------
Comment (by gsteinmon):
Replying to [comment:4 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.
--
Ticket URL: <http://trac.osgeo.org/osgeo/ticket/1802#comment:5>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#1802: Dev Setup for 2017.foss4g.org Jekyll Site
---------------------------+--------------------
Reporter: gsteinmon | Owner: sac@…
Type: task | Status: new
Priority: normal | Milestone:
Component: Systems Admin | Resolution:
Keywords: |
---------------------------+--------------------
Comment (by 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.
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/1802#comment:6>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#1802: Dev Setup for 2017.foss4g.org Jekyll Site
---------------------------+--------------------
Reporter: gsteinmon | Owner: sac@…
Type: task | Status: new
Priority: normal | Milestone:
Component: Systems Admin | Resolution:
Keywords: |
---------------------------+--------------------
Comment (by 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 [comment:6 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.
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/1802#comment:7>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#1802: Dev Setup for 2017.foss4g.org Jekyll Site
---------------------------+--------------------
Reporter: gsteinmon | Owner: sac@…
Type: task | Status: new
Priority: normal | Milestone:
Component: Systems Admin | Resolution:
Keywords: |
---------------------------+--------------------
Comment (by 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.
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/1802#comment:8>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#1802: Dev Setup for 2017.foss4g.org Jekyll Site
---------------------------+--------------------
Reporter: gsteinmon | Owner: sac@…
Type: task | Status: new
Priority: normal | Milestone:
Component: Systems Admin | Resolution:
Keywords: |
---------------------------+--------------------
Comment (by 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
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/1802#comment:9>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#1802: Dev Setup for 2017.foss4g.org Jekyll Site
---------------------------+--------------------
Reporter: gsteinmon | Owner: sac@…
Type: task | Status: new
Priority: normal | Milestone:
Component: Systems Admin | Resolution:
Keywords: |
---------------------------+--------------------
Comment (by 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?
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/1802#comment:10>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#1802: Dev Setup for 2017.foss4g.org Jekyll Site
---------------------------+--------------------
Reporter: gsteinmon | Owner: sac@…
Type: task | Status: new
Priority: normal | Milestone:
Component: Systems Admin | Resolution:
Keywords: |
---------------------------+--------------------
Comment (by 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 ?
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/1802#comment:11>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#1802: Dev Setup for 2017.foss4g.org Jekyll Site
---------------------------+--------------------
Reporter: gsteinmon | Owner: sac@…
Type: task | Status: new
Priority: normal | Milestone:
Component: Systems Admin | Resolution:
Keywords: |
---------------------------+--------------------
Comment (by EliL):
Replying to [comment:10 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.
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/1802#comment:12>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#1802: Dev Setup for 2017.foss4g.org Jekyll Site
---------------------------+--------------------
Reporter: gsteinmon | Owner: sac@…
Type: task | Status: new
Priority: normal | Milestone:
Component: Systems Admin | Resolution:
Keywords: |
---------------------------+--------------------
Comment (by 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?
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/1802#comment:13>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#1802: Dev Setup for 2017.foss4g.org Jekyll Site
---------------------------+--------------------
Reporter: gsteinmon | Owner: sac@…
Type: task | Status: new
Priority: normal | Milestone:
Component: Systems Admin | Resolution:
Keywords: |
---------------------------+--------------------
Comment (by 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.
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/1802#comment:14>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#1802: Dev Setup for 2017.foss4g.org Jekyll Site
---------------------------+--------------------
Reporter: gsteinmon | Owner: sac@…
Type: task | Status: new
Priority: normal | Milestone:
Component: Systems Admin | Resolution:
Keywords: |
---------------------------+--------------------
Comment (by 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)
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/1802#comment:15>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#1802: Dev Setup for 2017.foss4g.org Jekyll Site
---------------------------+--------------------
Reporter: gsteinmon | Owner: sac@…
Type: task | Status: new
Priority: normal | Milestone:
Component: Systems Admin | Resolution:
Keywords: |
---------------------------+--------------------
Comment (by 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.
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/1802#comment:16>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#1802: Dev Setup for 2017.foss4g.org Jekyll Site
---------------------------+----------------------
Reporter: gsteinmon | Owner: sac@…
Type: task | Status: closed
Priority: normal | Milestone:
Component: Systems Admin | Resolution: wontfix
Keywords: |
---------------------------+----------------------
Changes (by gsteinmon):
* status: new => closed
* resolution: => wontfix
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/1802#comment:17>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.