[lively-kernel] Local installation of Lively Core from Github: some notes, questions, and errors

[Milan Zimmermann]

hmm interesting .. do you mean to use the squeak http server + seaside
for this .. lively wiki currently uses dav and dav-svn for versioning
.. i am not sure if or how seaside (or rather the underlying http
server)  would provide versioning but worth looking into.... (quick
google did not help me much)

milan

On Thu, Mar 8, 2012 at 9:27 PM, Lawson English <lenglish5 at cox.net> wrote:
> Is there yet no one-click install that leverages seaside for this?
>
>
> L.
>
>
> On 3/8/12 7:08 PM, Milan Zimmermann wrote:
>
> Hi:
>
> Finally I managed to put together a script that installs a localhost
> based LivelyKernel and LivelyWiki (one flavour of Linux only) - based
> on various previous installs such as Fabian's Lively2 install, the
> LivelyKernel git, this mailing list help etc (thanks!).
>
> The installer loads all required OS packages (apache, git, nodejs,
> git, svn and dependencies), gets LivelyKernel from the git repo,
> installs all nodejs packages, creates the Apache LK configurations
> including dav-svn and authentication modules, adjusts permissions,
> creates the SVN repo for  LivelyWiki etc etc and starts Apache when
> done. It does give me a working repeatable installation :) It does
> everything automatically, except the last bit of bootstraping
> PartsBin, I could not figure out how to automate that part.
>
> If it may be of any use to anyone it is attached - but I think the
> most important point it makes, is that Apache installation is the same
> pain as 15 years ago (increased with DAV, and dav-svn  of course), and
> partly for that reason it is hard for a new person not ready to spend
> significant time to go through creating a personal, at the same time
> somewhat world shareable (authentication) LivelyKernel and LivelyWiki.
>  At least for the personal install it will be great to replace the
> need for Apache + dav svn with something simpler (as I think Fabian
> and maybe others are working on. I will check that next :) )
>
> Thanks for all help along the way here
>
> Milan
>
> On Thu, Mar 1, 2012 at 11:29 AM, Milan Zimmermann
> <milan.zimmermann at gmail.com> wrote:
>
> On Thu, Mar 1, 2012 at 11:01 AM, Jens Lincke
> <jens.lincke at hpi.uni-potsdam.de> wrote:
>
> Hi, Milan
>
> you can always run the bootstrap again, it will just override everything.
> If you published your locally changed parts under new names or your own
> category, this should be no problem.
>
> Great, thanks, that is the piece of knowledge I was looking for at this
> point.
>
> We work on some mechanism that lets your upload your changes back to
> webwerkstatt
> and that in the end will give you diffing and merging of parts.
>
> Perfect :)
>
> Meanwhile you can always copy your changes files for parts and pages and
> commit them
> with the svn tools.
>
> Thanks Jens!
>
> Milan
>
> Best,
> Jens
>
> Am 01.03.2012 um 16:47 schrieb Milan Zimmermann:
>
>
>
>   Config.rootPath = 'http://lively-kernel.org/repository/webwerkstatt/'
>   $world.openPartItem("BootstrapParts", "PartsBin/Tools")
>
> Then, let's say I work for a while. save some things locally, etc,
> then decide to get PartsBin *updates* from
> http://lively-kernel.org/repository/webwerkstatt/ again.
>
> Is there a way to do that that anyone here uses? [I think it was
> answered as negative, but wanted to check, thanks.  (At the same time
> it can  likely be done by merging from  a read-only mirror master or
> similar but surely must be a pain). Apart from that, is there perhaps
> a plan to base the wiki versioning on Git rather then SVN?]
>
>
>
>
> _______________________________________________
> lively-kernel mailing list
> lively-kernel at hpi.uni-potsdam.de
> http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel
>
>
>
> _______________________________________________
> lively-kernel mailing list
> lively-kernel at hpi.uni-potsdam.de
> http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel
>