Yes, we do not have PR workflow for SVN like we have for Git... Anyway, I applied your patches with some fixes (r1746248) and you have it now the content live at our staging site:
http://marmotta.staging.apache.org/configuration.html http://marmotta.staging.apache.org/installation.html Thanks! On Tue, May 31, 2016 at 12:45 AM, Rob Atkinson <[email protected]> wrote: > I guess the list didnt allow attachements,, > > not sure if there is a better way of dealing with this with svn- i guess > it would be a matter of checking in to a review branch? > > Rob > > On Tue, 31 May 2016 at 01:45 Sergio Fernández <[email protected]> wrote: > >> Sorry, I guess the attachment got lost... >> >> ASF CMS uses SVN, that's why you can't find it in out git. >> >> On Mon, May 30, 2016 at 2:50 PM, Rob Atkinson <[email protected]> >> wrote: >> >> > Hi Sergio - >> > >> > here are edits to both installation and configuration to make sure >> things >> > go in the right order - if I have fully understood the behaviour. >> > >> > (I couldnt find a git version of these docs to create a pull request - >> so >> > just attached them) >> > >> > Rob >> > >> > On Mon, 30 May 2016 at 17:56 Sergio Fernández <[email protected]> >> wrote: >> > >> >> Exactly, Marmotta automatically self-configures on the first HTTP >> request. >> >> >> >> Please, if you consider that detail not suffiently explain, you can >> >> provide >> >> a patch to >> >> >> >> >> http://svn.apache.org/repos/asf/marmotta/site/trunk/content/markdown/configuration.md >> >> with a clearer explanation. >> >> >> >> On Sat, May 28, 2016 at 12:56 AM, Rob Atkinson <[email protected] >> > >> >> wrote: >> >> >> >> > So its the first HTTP request sets a config parameter? This probably >> >> ought >> >> > to be made clear - it took a long time to unravel this after I >> installed >> >> > marmotta from a remote source and tested it before I tried >> configuring >> >> it. >> >> > I have seen environments where the local machine didnt recognise the >> >> > external name used - and it would be impossible to access from the >> local >> >> > machine n that case I think. I should raise an issue - but is this a >> >> > documentation issue or a behaviour issue? >> >> > >> >> > Thanks for the clarifications. >> >> > >> >> > Rob >> >> > >> >> > >> >> > On Fri, 27 May 2016 at 17:57 Sergio Fernández <[email protected]> >> >> wrote: >> >> > >> >> > > On Fri, May 27, 2016 at 9:52 AM, Rob Atkinson < >> [email protected] >> >> > >> >> > > wrote: >> >> > > > >> >> > > > I have read that page many times and I still dont really >> understand >> >> > > > exactly what you mean by "Note that the host name and port you >> are >> >> > using >> >> > > > for the first access to your installation is *important* since >> >> decides >> >> > on >> >> > > > how Linked Data resources will be handled later" >> >> > > > >> >> > > > what constitutes an "access"?- first time you access in a >> browser, >> >> > first >> >> > > > time you edit configs and restart, first time you post something >> to >> >> an >> >> > > > endpoint? >> >> > > > >> >> > > >> >> > > First time Marmotta is reached (browser, api access or whatever) >> after >> >> > > installing. >> >> > > >> >> > > >> >> > > >> >> > > -- >> >> > > Sergio Fernández >> >> > > Partner Technology Manager >> >> > > Redlink GmbH >> >> > > m: +43 6602747925 >> >> > > e: [email protected] >> >> > > w: http://redlink.co >> >> > > >> >> > >> >> >> >> >> >> >> >> -- >> >> Sergio Fernández >> >> Partner Technology Manager >> >> Redlink GmbH >> >> m: +43 6602747925 >> >> e: [email protected] >> >> w: http://redlink.co >> >> >> > >> >> >> -- >> Sergio Fernández >> Partner Technology Manager >> Redlink GmbH >> m: +43 6602747925 >> e: [email protected] >> w: http://redlink.co >> > -- Sergio Fernández Partner Technology Manager Redlink GmbH m: +43 6602747925 e: [email protected] w: http://redlink.co
