------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
On Sun, Jul 28, 2013 at 10:49 PM, Chris Holmes <chomie@anonymised.com> wrote:
I believe the template for the home page is some static HTML that only
people from OpenGeo can touch, yes?
I think that sounds right? I believe the reason was to be able to put a
map on the front page.
Single points of access aren't ideal, wondering if we should migrate it to
github pages? Then anyone can make pull requests, etc.
Yep, that would be an excellent move (althought I'm not familiar enought
with github pages to say if that would work or not):
people come and go, the project remains, better have something that the
active contributors of the
day can access
On Sun, Jul 28, 2013 at 10:49 PM, Chris Holmes <chomie@anonymised.com
<mailto:chomie@anonymised.com>> wrote:
I believe the template for the home page is some static HTML that
only people from OpenGeo can touch, yes?
I think that sounds right? I believe the reason was to be able to
put a map on the front page.
Single points of access aren't ideal, wondering if we should migrate
it to github pages? Then anyone can make pull requests, etc.
Yep, that would be an excellent move (althought I'm not familiar enought
with github pages to say if that would work or not):
people come and go, the project remains, better have something that
the active contributors of the
day can access
+1.
--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
+1 on github pages. As I understand it it is a fairly straight forward process. Just create an orphaned branch named “gh-pages” and add the static content there. That said if we move the home page there it probably makes more sense to use the github wiki as well. This would be more work.
I’m having trouble finding where the static part of the website is served from… will try to nail down with our sysadmin and report back.
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk