concerted-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gaurav Shukla <>
Subject Re: Website for Concerted
Date Sun, 18 Oct 2015 20:21:59 GMT
Dynamic website was required for two features -

1. Full text search powered by Elastic search
          I went with elastic search because the whole documentation can be
indexed in it and also it supports query DSL. Moreover we could use it to
index all the content related to this project and provide searching across
various sources be it mailing archives, wiki's , documentation , etc

2. To set up a demo app which can be used to along with documentation to
give hands on experience to anyone reading the documentation (For eg see google
api explorer

@Jake I agree with your concerns regarding hosting externally. If there's
some other way you can suggest to implement both these features staying
inside the ASF infra. then we don't need to host anything elsewhere.

On Mon, Oct 19, 2015 at 1:27 AM, Jake Farrell <> wrote:

> -1 to hosting externally, this makes it impossible for ASF infra to help
> when issues arise and also if someone decides to leave the project there
> are no access controls in place that the ASF has control over. Infra does
> support running a per project vm or possible we could do this using a
> docker container which could contain the site and meet the projects needs
> (though I lack to see why a dynamic site is really needed here)
> -Jake
> On Sun, Oct 18, 2015 at 3:33 PM, Gaurav Shukla <>
> wrote:
> > Keeping in mind Julian's message (Permalink
> > <
> >
> > >).Since
> > apache allows support for static websites only I think an api based
> backend
> > with angular js front end would be good for website.
> >
> > Api written in python would need to be hosted somewhere else while the
> > website  front end (written in Angularjs) can be hosted via svnpubsub.
> >
> > I suppose 'powered by concerted' means using concerted as datastore for
> > website. A possible use case can be the '*Try it yourself*' section.
> >
> > Any suggestions from the more experienced people out here are most
> welcome
> > because I am just a newbie so I don't know what extra limitations might
> be
> > there.
> >

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message