Quantcast

Local installation of Lively Core from Github: some notes, questions, and errors

classic Classic list List threaded Threaded
20 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Local installation of Lively Core from Github: some notes, questions, and errors

milan zimmermann
Hi:

This weekend I set to install Lively Core from Github on"localhost" ,
using the instructions on Github, with some tinkering in addition.
Short summary is that the resulting install does sort of work, I can
drag out PartsBin, from there drag out parts etc. There are however
quite a few errors when using it (more below).

A brief summary of my installation steps on localhost (Opensuse 12.1
although that is likely not relevant):
--------------------------------------

        - git clone as instructed ~/LivelyKernel
        - npm install
        - make install_partsbin (at the end of this step I have an
combination of .git and .svn client directories) in ~/LivelyKernel)
        - copied ~/LivelyKernel under Apache /srv/www/htdocs
        - configured Apache for WebDAV to /srv/www/htdocs/LivelyKernel
        - pointed to http://127.0.0.1/LivelyKernel/blank.xhtml
        - the world shows and somewhat works, but  not as good as the online
lively-kernel.org :)


I have some questions (realizing most are related to WebDAV/Git) and errors:
-------------------------------------------------------------

If anyone could help or comment that would be great - thanks

        1) From my previous installation of Lively2, I thought WebDAV
requires an actual SVN repository (svnadmin create repo) to work with
Lively2, but this time the lk.conf seem to indicate it can simply
contain the combination of the .git and .svn directories created
above.  Is that how it is supposed to be configured for webDAV /
Lively to work? Also, is the the combination of .git and .svn client
files an issue, and I wonder which parts of the ~/LivelyKernel are
used by Lively for saving and changes...

        2) How does webwerkstatt create the login (later used to authorize to
save worlds), and is there an equivalent way to set it up for the
localhost install?

        3) did someone reading this tried to install core to share notes

Errors:
-----------

        1) Error on dragging out the cloud from PartsBin (similar errors in
other situations):

Error when trying to update
AttributeConnection(PartsItem(Cloud,PartsSpace(PartsBin/Basic/)).loadedMetaInfo
--> <lively.morphic.Box#E5AB3... -
PartsBinBrowser>.setMetaInfoOfSelectedItem) with value
MetaInfo(PartsBin/Basic/Cloud):
TypeError: Object Thu Nov 03 2011 19:13:58 GMT-0400 (EDT) has no method 'format'
TypeError: Object Thu Nov 03 2011 19:13:58 GMT-0400 (EDT) has no method 'format'
    at eval at <anonymous>
(http://127.0.0.1/LivelyKernel/core/lively/lang/Closure.js?1330401795819:98:29)
    at Array.map (native)
    at Box.commitLogString (eval at <anonymous>
(http://127.0.0.1/LivelyKernel/core/lively/lang/Closure.js?1330401795819:98:29))
    at Box.setMetaInfoOfSelectedItem (eval at <anonymous>
(http://127.0.0.1/LivelyKernel/core/lively/lang/Closure.js?1330401795819:98:29))
    at http://127.0.0.1/LivelyKernel/core/lively/bindings/Core.js?1330401803225:178:19
    at AttributeConnection.update
(http://127.0.0.1/LivelyKernel/core/lively/bindings/Core.js?1330401803225:188:5)
    at PartItem.loadedMetaInfo
(http://127.0.0.1/LivelyKernel/core/lively/bindings/Core.js?1330401803225:246:8)
    at http://127.0.0.1/LivelyKernel/core/lively/bindings/Core.js?1330401803225:179:23
    at AttributeConnection.updater (eval at <anonymous>
(http://127.0.0.1/LivelyKernel/core/lively/lang/Closure.js?1330401795819:98:29))
    at AttributeConnection.update
(http://127.0.0.1/LivelyKernel/core/lively/bindings/Core.js?1330401803225:187:13)


        2) Cannot Save at all / Error on saving blank.xhtml as blank2.xhtml:

        "directory http://127.0.0.1/LivelyKernel does not exist! Create it?"
       
        on OK:

        Problem saving http://127.0.0.1/LivelyKernel/blank2.xhtml:
#<NetRequestStatus{PUT,http://127.0.0.1/LivelyKernel/blank2.xhtml,403}>

Thanks

milan
_______________________________________________
lively-kernel mailing list
[hidden email]
http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Local installation of Lively Core from Github: some notes, questions, and errors

Lincke, Jens
Hi, Milan -

I did a local Lively Setup the following way. I made some notes, they are Mac specific and might miss some steps.
My basic idea was to have two installations: one clean from git with the code and one in the webwerkstatt wiki style for 
playing around with parts and pages. 


How to install lively locally on my Mac: - check out LivelyKernel from github: cd /Library/WebServer/ git clone https://github.com/rksm/LivelyKernel.git - copy https://github.com/rksm/LivelyKernel/blob/master/apache_config/lk_osx.conf into /etc/apache2/other/ - enable your local web server in the Mac system preferences - or if you already have, restart apache: sudo apachectl restart - /Library/WebServer/Documents/LivelyKernel/ This will give you a bare installaltion of Lively without history and without any Tool Parts. How to setup a LivelyWiki - For Lively Wiki functionality as in WebWerkstatt we need apache to serve us an svn repository. So we have to create one: sudo mkdir /Library/WebServer/repositories sudo svnadmin create /Library/WebServer/repositories/LivelyWiki - Allow the webserver to read and write the repositories: sudo chown -R _www:_www /Library/WebServer/repositories/LivelyWiki

- add /etc/apache2/other/livelywiki_osx.conf:

<IfModule !dav_module> LoadModule dav_module libexec/apache2/mod_dav.so </IfModule> <IfModule !dav_svn_module> LoadModule dav_svn_module libexec/apache2/mod_dav_svn.so </IfModule> Redirect /LivelyWiki/core/ /LivelyKernel/core/ # change this to wherever your svn repo is <Location /LivelyWiki> DAV svn SVNPath /Library/WebServer/repositories/LivelyWiki SVNAutoVersioning on ModMimeUsePathInfo on Order Deny,Allow Allow from All SetOutputFilter DEFLATE DavDepthInfinity on </Location>

#EOF

This gives you two repositories:

a) http://localhost/LivelyKernel/ -> WebDAV served plain git 
b) http://localhost/LivelyWiki/ -> SVN DAV Lively wiki with auto commit history

if we copy a blank.xhtml from (a) into (b)i we can start working in (b) because all the .js files are loaded from (a)

I then bootstrapped the parts using a part from WebWerkstatt:

var oldRootPath = Config.rootPath try { Config.rootPath = 'http://lively-kernel.org/repository/webwerkstatt/' this.openPartItem("BootstrapParts", "PartsBin/Tools") } finally { Config.rootPath = oldRootPath }

I tried to figure out a way how I can upload parts / changes made on my localhost machine to webwerkstatt using the proxy,
but I failed because digest authentication can not be proxied with our URL rewriting approach and I will have to use node.js for this.

Best,
Jens 



Am 28.02.2012 um 06:18 schrieb Milan Zimmermann:

Hi:

This weekend I set to install Lively Core from Github on"localhost" ,
using the instructions on Github, with some tinkering in addition.
Short summary is that the resulting install does sort of work, I can
drag out PartsBin, from there drag out parts etc. There are however
quite a few errors when using it (more below).

A brief summary of my installation steps on localhost (Opensuse 12.1
although that is likely not relevant):
--------------------------------------

- git clone as instructed ~/LivelyKernel
- npm install
- make install_partsbin (at the end of this step I have an
combination of .git and .svn client directories) in ~/LivelyKernel)
- copied ~/LivelyKernel under Apache /srv/www/htdocs
- configured Apache for WebDAV to /srv/www/htdocs/LivelyKernel
- pointed to http://127.0.0.1/LivelyKernel/blank.xhtml
- the world shows and somewhat works, but  not as good as the online
lively-kernel.org :)


I have some questions (realizing most are related to WebDAV/Git) and errors:
-------------------------------------------------------------

If anyone could help or comment that would be great - thanks

1) From my previous installation of Lively2, I thought WebDAV
requires an actual SVN repository (svnadmin create repo) to work with
Lively2, but this time the lk.conf seem to indicate it can simply
contain the combination of the .git and .svn directories created
above.  Is that how it is supposed to be configured for webDAV /
Lively to work? Also, is the the combination of .git and .svn client
files an issue, and I wonder which parts of the ~/LivelyKernel are
used by Lively for saving and changes...

2) How does webwerkstatt create the login (later used to authorize to
save worlds), and is there an equivalent way to set it up for the
localhost install?

3) did someone reading this tried to install core to share notes

Errors:
-----------

1) Error on dragging out the cloud from PartsBin (similar errors in
other situations):

Error when trying to update
AttributeConnection(PartsItem(Cloud,PartsSpace(PartsBin/Basic/)).loadedMetaInfo
--> <lively.morphic.Box#E5AB3... -
PartsBinBrowser>.setMetaInfoOfSelectedItem) with value
MetaInfo(PartsBin/Basic/Cloud):
TypeError: Object Thu Nov 03 2011 19:13:58 GMT-0400 (EDT) has no method 'format'
TypeError: Object Thu Nov 03 2011 19:13:58 GMT-0400 (EDT) has no method 'format'
   at eval at <anonymous>
(http://127.0.0.1/LivelyKernel/core/lively/lang/Closure.js?1330401795819:98:29)
   at Array.map (native)
   at Box.commitLogString (eval at <anonymous>
(http://127.0.0.1/LivelyKernel/core/lively/lang/Closure.js?1330401795819:98:29))
   at Box.setMetaInfoOfSelectedItem (eval at <anonymous>
(http://127.0.0.1/LivelyKernel/core/lively/lang/Closure.js?1330401795819:98:29))
   at http://127.0.0.1/LivelyKernel/core/lively/bindings/Core.js?1330401803225:178:19
   at AttributeConnection.update
(http://127.0.0.1/LivelyKernel/core/lively/bindings/Core.js?1330401803225:188:5)
   at PartItem.loadedMetaInfo
(http://127.0.0.1/LivelyKernel/core/lively/bindings/Core.js?1330401803225:246:8)
   at http://127.0.0.1/LivelyKernel/core/lively/bindings/Core.js?1330401803225:179:23
   at AttributeConnection.updater (eval at <anonymous>
(http://127.0.0.1/LivelyKernel/core/lively/lang/Closure.js?1330401795819:98:29))
   at AttributeConnection.update
(http://127.0.0.1/LivelyKernel/core/lively/bindings/Core.js?1330401803225:187:13)


2) Cannot Save at all / Error on saving blank.xhtml as blank2.xhtml:

"directory http://127.0.0.1/LivelyKernel does not exist! Create it?"

on OK:

Problem saving http://127.0.0.1/LivelyKernel/blank2.xhtml:
#<NetRequestStatus{PUT,http://127.0.0.1/LivelyKernel/blank2.xhtml,403}>

Thanks

milan
_______________________________________________
lively-kernel mailing list
[hidden email]
http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel


_______________________________________________
lively-kernel mailing list
[hidden email]
http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Local installation of Lively Core from Github: some notes, questions, and errors

Fabian Bornhofen-2
In reply to this post by milan zimmermann
Hi -

first of all thanks Jens for the instructions.. looks like we should
consolidate the docs once again :).

A few remarks:

On Mon, Feb 27, 2012 at 9:18 PM, Milan Zimmermann
<[hidden email]> wrote:
>        1) From my previous installation of Lively2, I thought WebDAV
> requires an actual SVN repository (svnadmin create repo) to work with
> Lively2, but this time the lk.conf seem to indicate it can simply
> contain the combination of the .git and .svn directories created
> above.  Is that how it is supposed to be configured for webDAV /
> Lively to work? Also, is the the combination of .git and .svn client
> files an issue, and I wonder which parts of the ~/LivelyKernel are
> used by Lively for saving and changes...
There are two approaches for serving files from SVN:
(1) Serving from a repository:
  (+) you can use full version control
  (-) the moment you create a local SVN repo, you have a fork that is
very hard to keep in sync with the upstream repository
(2) Serving from a local copy
  (-) no version control
  (+) syncing is as easy as "svn up" or "svn commit"
With git, you can have both (even though we don't have tools for that
yet): a view on the files that at the same time is a real repository
that can be synced with upstream quite easily (git pull, git push).
In the setup you described, PartsBin is a working copy of a subversion
repo inside your local git repo. In .gitignore, we tell git to
completely ignore that folder. If there are any issues with that
anyway, please let us know.

What parts are used for saving and changes:
Saving is done using HTTP PUT or POST requests (regular WebDAV) in
WebResource. Also, SCB and PartsBin use version information. That is
done using SVN extensions to WebDAV. I am not very familiar with that
part of the code base. (No big fan of SVN and DAV-SVN in particular.
This should be so much more simple.)


>        2) How does webwerkstatt create the login (later used to authorize to
> save worlds), and is there an equivalent way to set it up for the
> localhost install?
Should be regular HTTP digest auth in Apache and I expect Lively to be
completely ignorant about that. Jens?


>        1) Error on dragging out the cloud from PartsBin (similar errors in
> other situations):
>
> Error when trying to update
> AttributeConnection(PartsItem(Cloud,PartsSpace(PartsBin/Basic/)).loadedMetaInfo
> --> <lively.morphic.Box#E5AB3... -
> PartsBinBrowser>.setMetaInfoOfSelectedItem) with value
> MetaInfo(PartsBin/Basic/Cloud):
> TypeError: Object Thu Nov 03 2011 19:13:58 GMT-0400 (EDT) has no method 'format'
> TypeError: Object Thu Nov 03 2011 19:13:58 GMT-0400 (EDT) has no method 'format'
Thanks for the report.

>        2) Cannot Save at all / Error on saving blank.xhtml as blank2.xhtml:
>
>        "directory http://127.0.0.1/LivelyKernel does not exist! Create it?"
>
>        on OK:
>
>        Problem saving http://127.0.0.1/LivelyKernel/blank2.xhtml:
> #<NetRequestStatus{PUT,http://127.0.0.1/LivelyKernel/blank2.xhtml,403}>
Did you check if the Apache process has sufficient rights to create
the folder and files in it?

I hope I'll have some time soon to update the installation guide & fix
some of the problems there.

Best
Fabian
_______________________________________________
lively-kernel mailing list
[hidden email]
http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Local installation of Lively Core from Github: some notes, questions, and errors

milan zimmermann
In reply to this post by Lincke, Jens
Hi Jens:

Thanks for your notes. Part of my confusion is the difference between
LivelyKernel and Webwerkstatt - I have so far only used "the whole
package" on lively-kernel.org so I am not sure where one starts and
ends....

I want to make over my installation based on your comments, but let me
make a summary if I am getting your process right:

a) Just installing the LivelyKernel files from Github under proper
apache directory  (as files - is WebDAV needed for this?) gives us
LivelyKernel functionality, correct? [subquestion that I can answer by
experimenting - what is the LivelyKernel functionality?]

b) To add the functionality of PartsBin, ability to save and version,
I need to also create a "real" svn repository (svnadmin create) under
Apache and attach WebDAV to it. From your notes it seems you created
an empty svn repository, and then, just copied the blank.xhtlm from
a), to b) and then you used the "bootstrap" process to populate the
svn repository with things like PartsBin etc. Is this correct so far?
If correct, at the end of this process, should the functionality be
expected to be equivalent to what I experience by opening a world at
lively-kernel such as
http://lively-kernel.org/repository/webwerkstatt/users/mzimmerm/start.xhtml
?

Sorry for all the questions, I am trying to get a picture of where I
am  heading and what to expect at each step ..

Thanks,

Milan

On Tue, Feb 28, 2012 at 4:21 AM, Jens Lincke
<[hidden email]> wrote:

> Hi, Milan -
>
> I did a local Lively Setup the following way. I made some notes, they are
> Mac specific and might miss some steps.
> My basic idea was to have two installations: one clean from git with the
> code and one in the webwerkstatt wiki style for
> playing around with parts and pages.
>
>
> How to install lively locally on my Mac: - check out LivelyKernel from
> github: cd /Library/WebServer/ git clone
> https://github.com/rksm/LivelyKernel.git - copy
> https://github.com/rksm/LivelyKernel/blob/master/apache_config/lk_osx.conf
> into /etc/apache2/other/ - enable your local web server in the Mac system
> preferences - or if you already have, restart apache: sudo apachectl restart
> - /Library/WebServer/Documents/LivelyKernel/ This will give you a bare
> installaltion of Lively without history and without any Tool Parts. How to
> setup a LivelyWiki - For Lively Wiki functionality as in WebWerkstatt we
> need apache to serve us an svn repository. So we have to create one: sudo
> mkdir /Library/WebServer/repositories sudo svnadmin create
> /Library/WebServer/repositories/LivelyWiki - Allow the webserver to read and
> write the repositories: sudo chown -R _www:_www
> /Library/WebServer/repositories/LivelyWiki
>
> - add /etc/apache2/other/livelywiki_osx.conf:
>
> <IfModule !dav_module> LoadModule dav_module libexec/apache2/mod_dav.so
> </IfModule> <IfModule !dav_svn_module> LoadModule dav_svn_module
> libexec/apache2/mod_dav_svn.so </IfModule> Redirect /LivelyWiki/core/
> /LivelyKernel/core/ # change this to wherever your svn repo is <Location
> /LivelyWiki> DAV svn SVNPath /Library/WebServer/repositories/LivelyWiki
> SVNAutoVersioning on ModMimeUsePathInfo on Order Deny,Allow Allow from All
> SetOutputFilter DEFLATE DavDepthInfinity on </Location>
>
> #EOF
>
> This gives you two repositories:
>
> a) http://localhost/LivelyKernel/ -> WebDAV served plain git
> b) http://localhost/LivelyWiki/ -> SVN DAV Lively wiki with auto commit
> history
>
> if we copy a blank.xhtml from (a) into (b)i we can start working in (b)
> because all the .js files are loaded from (a)
>
> I then bootstrapped the parts using a part from WebWerkstatt:
>
> var oldRootPath = Config.rootPath try { Config.rootPath =
> 'http://lively-kernel.org/repository/webwerkstatt/'
> this.openPartItem("BootstrapParts", "PartsBin/Tools") } finally {
> Config.rootPath = oldRootPath }
>
> I tried to figure out a way how I can upload parts / changes made on my
> localhost machine to webwerkstatt using the proxy,
> but I failed because digest authentication can not be proxied with our URL
> rewriting approach and I will have to use node.js for this.
>
> Best,
> Jens
>
>
>
> Am 28.02.2012 um 06:18 schrieb Milan Zimmermann:
>
> Hi:
>
> This weekend I set to install Lively Core from Github on"localhost" ,
> using the instructions on Github, with some tinkering in addition.
> Short summary is that the resulting install does sort of work, I can
> drag out PartsBin, from there drag out parts etc. There are however
> quite a few errors when using it (more below).
>
> A brief summary of my installation steps on localhost (Opensuse 12.1
> although that is likely not relevant):
> --------------------------------------
>
> - git clone as instructed ~/LivelyKernel
> - npm install
> - make install_partsbin (at the end of this step I have an
> combination of .git and .svn client directories) in ~/LivelyKernel)
> - copied ~/LivelyKernel under Apache /srv/www/htdocs
> - configured Apache for WebDAV to /srv/www/htdocs/LivelyKernel
> - pointed to http://127.0.0.1/LivelyKernel/blank.xhtml
> - the world shows and somewhat works, but  not as good as the online
> lively-kernel.org :)
>
>
> I have some questions (realizing most are related to WebDAV/Git) and errors:
> -------------------------------------------------------------
>
> If anyone could help or comment that would be great - thanks
>
> 1) From my previous installation of Lively2, I thought WebDAV
> requires an actual SVN repository (svnadmin create repo) to work with
> Lively2, but this time the lk.conf seem to indicate it can simply
> contain the combination of the .git and .svn directories created
> above.  Is that how it is supposed to be configured for webDAV /
> Lively to work? Also, is the the combination of .git and .svn client
> files an issue, and I wonder which parts of the ~/LivelyKernel are
> used by Lively for saving and changes...
>
> 2) How does webwerkstatt create the login (later used to authorize to
> save worlds), and is there an equivalent way to set it up for the
> localhost install?
>
> 3) did someone reading this tried to install core to share notes
>
> Errors:
> -----------
>
> 1) Error on dragging out the cloud from PartsBin (similar errors in
> other situations):
>
> Error when trying to update
> AttributeConnection(PartsItem(Cloud,PartsSpace(PartsBin/Basic/)).loadedMetaInfo
> --> <lively.morphic.Box#E5AB3... -
> PartsBinBrowser>.setMetaInfoOfSelectedItem) with value
> MetaInfo(PartsBin/Basic/Cloud):
> TypeError: Object Thu Nov 03 2011 19:13:58 GMT-0400 (EDT) has no method
> 'format'
> TypeError: Object Thu Nov 03 2011 19:13:58 GMT-0400 (EDT) has no method
> 'format'
>    at eval at <anonymous>
> (http://127.0.0.1/LivelyKernel/core/lively/lang/Closure.js?1330401795819:98:29)
>    at Array.map (native)
>    at Box.commitLogString (eval at <anonymous>
> (http://127.0.0.1/LivelyKernel/core/lively/lang/Closure.js?1330401795819:98:29))
>    at Box.setMetaInfoOfSelectedItem (eval at <anonymous>
> (http://127.0.0.1/LivelyKernel/core/lively/lang/Closure.js?1330401795819:98:29))
>    at
> http://127.0.0.1/LivelyKernel/core/lively/bindings/Core.js?1330401803225:178:19
>    at AttributeConnection.update
> (http://127.0.0.1/LivelyKernel/core/lively/bindings/Core.js?1330401803225:188:5)
>    at PartItem.loadedMetaInfo
> (http://127.0.0.1/LivelyKernel/core/lively/bindings/Core.js?1330401803225:246:8)
>    at
> http://127.0.0.1/LivelyKernel/core/lively/bindings/Core.js?1330401803225:179:23
>    at AttributeConnection.updater (eval at <anonymous>
> (http://127.0.0.1/LivelyKernel/core/lively/lang/Closure.js?1330401795819:98:29))
>    at AttributeConnection.update
> (http://127.0.0.1/LivelyKernel/core/lively/bindings/Core.js?1330401803225:187:13)
>
>
> 2) Cannot Save at all / Error on saving blank.xhtml as blank2.xhtml:
>
> "directory http://127.0.0.1/LivelyKernel does not exist! Create it?"
>
> on OK:
>
> Problem saving http://127.0.0.1/LivelyKernel/blank2.xhtml:
> #<NetRequestStatus{PUT,http://127.0.0.1/LivelyKernel/blank2.xhtml,403}>
>
> Thanks
>
> milan
> _______________________________________________
> lively-kernel mailing list
> [hidden email]
> http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel
>
>
_______________________________________________
lively-kernel mailing list
[hidden email]
http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Local installation of Lively Core from Github: some notes, questions, and errors

Lincke, Jens
In reply to this post by Fabian Bornhofen-2

Am 28.02.2012 um 20:41 schrieb Fabian Bornhofen:

       2) How does webwerkstatt create the login (later used to authorize to
save worlds), and is there an equivalent way to set it up for the
localhost install?
Should be regular HTTP digest auth in Apache and I expect Lively to be
completely ignorant about that. Jens?

Lively is ignorant about the kind of authentication per get or put, that is all handled by the various means the 
Apache provides. We used first basic auth and later digest  for these purposes....


       1) Error on dragging out the cloud from PartsBin (similar errors in
other situations):

Error when trying to update
AttributeConnection(PartsItem(Cloud,PartsSpace(PartsBin/Basic/)).loadedMetaInfo
--> <lively.morphic.Box#E5AB3... -
PartsBinBrowser>.setMetaInfoOfSelectedItem) with value
MetaInfo(PartsBin/Basic/Cloud):
TypeError: Object Thu Nov 03 2011 19:13:58 GMT-0400 (EDT) has no method 'format'
TypeError: Object Thu Nov 03 2011 19:13:58 GMT-0400 (EDT) has no method 'format'
Thanks for the report.
The format is in the app.DateFormat, which is not included in core...
This is the reason I pulled in the apps folder in my local lively bootstrap part.


Best,
Jens

_______________________________________________
lively-kernel mailing list
[hidden email]
http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Local installation of Lively Core from Github: some notes, questions, and errors

Robert Krahn-3
In reply to this post by Fabian Bornhofen-2
Hi, Milan --

Thank you very much for trying this out!

Below are a few notes:

Setting up digest authentication is done in the Apache config with something like

AuthType Digest
AuthName "lively"
AuthDigestDomain "/repository/"
AuthUserFile "/path/to/user.htpasswd"
AuthGroupFile /path/to/groups

in the <Location> rule that defines the repository access.


> What parts are used for saving and changes:
> Saving is done using HTTP PUT or POST requests (regular WebDAV) in

We just use PUTs for that.


> WebResource. Also, SCB and PartsBin use version information. That is
> done using SVN extensions to WebDAV. I am not very familiar with that
> part of the code base. (No big fan of SVN and DAV-SVN in particular.
> This should be so much more simple.)

I agree there. WebDAV simulates a HTTP-based file system but that especially the
more advanced features like versioning are well hidden behind complicated interfaces
(actually versioning isn't defined by the WebDAV protocol but by a protocol extension
called DeltaV). The svn apache module never really completely implemented the DeltaV
specification which makes using that stuff even harder. Sooner or later we definitely want
to have much simpler solution, maybe based on a node.js server that gets bootstrapped
and is completely written and changeable from within Lively.


>>        Problem saving http://127.0.0.1/LivelyKernel/blank2.xhtml:

Check the file permissions. The apache user (www-data) needs write permission.

Also, right now the git repo isn't really prepared for being deployed as a full Lively wiki package.
Right now we just focus on the core part of the system. However, we will improve the
support over time and any help there is very much welcome! (Might it be in form
of bug reports or newly implemented features)

Best,
Robert
_______________________________________________
lively-kernel mailing list
[hidden email]
http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Local installation of Lively Core from Github: some notes, questions, and errors

Lincke, Jens
In reply to this post by milan zimmermann
Hi Milan,

I think all your assumptions are correct:

Am 28.02.2012 um 20:57 schrieb Milan Zimmermann:

> Hi Jens:
>
> Thanks for your notes. Part of my confusion is the difference between
> LivelyKernel and Webwerkstatt - I have so far only used "the whole
> package" on lively-kernel.org so I am not sure where one starts and
> ends....
Lively Webwerkstatt is one instance of a Lively Wiki, where the main Lively Kernel 2
development took place. It contains the JavaScript files based core, some additonal modules
distributed in apps, projects, and the user directories. There are also some private pages for example
the "hpi" directory. It then contains the PartsBin. Some of the categories can be considered Core, because
they make up a lot of Lively Kernel functionality such as the PartsBin and the ScriptEditor. But they are
not managed and distributed by the git Lively Kernel project. And there are Lively pages, which contain
mainly content. The core contains only the blank.xhtml page, because one page is needed to start working.

>
> I want to make over my installation based on your comments, but let me
> make a summary if I am getting your process right:
>
> a) Just installing the LivelyKernel files from Github under proper
> apache directory  (as files - is WebDAV needed for this?) gives us
> LivelyKernel functionality, correct? [subquestion that I can answer by
> experimenting - what is the LivelyKernel functionality?]
More or less, it gives you the core of Lively but you don't have the parts based
tools...

>
>
> b) To add the functionality of PartsBin, ability to save and version,
> I need to also create a "real" svn repository (svnadmin create) under
> Apache and attach WebDAV to it. From your notes it seems you created
> an empty svn repository, and then, just copied the blank.xhtlm from
> a), to b) and then you used the "bootstrap" process to populate the
> svn repository with things like PartsBin etc. Is this correct so far?
> If correct, at the end of this process, should the functionality be
> expected to be equivalent to what I experience by opening a world at
> lively-kernel such as
> http://lively-kernel.org/repository/webwerkstatt/users/mzimmerm/start.xhtml
> ?
>
I think so, if something is missing please write here...

Thanks for trying out.

Best,
Jens
_______________________________________________
lively-kernel mailing list
[hidden email]
http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Local installation of Lively Core from Github: some notes, questions, and errors

Robert Krahn-3
a) Just installing the LivelyKernel files from Github under proper
apache directory  (as files - is WebDAV needed for this?) gives us
LivelyKernel functionality, correct? [subquestion that I can answer by
experimenting - what is the LivelyKernel functionality?]

Really good question ;-)

As of now:
- bootstrap process
- class system
- extensions to JS objects
- "Network" abstraction
- module system
- data bindings
- serialization
- test framework
- Lively morphic v2

Currently also an OMeta integration and based on that a JavaScript parser and
interpreter are included.

We will working on shrinking that however. This is one of the main reasons for
creating that "fork". See this wiki entry for our motivation.

_______________________________________________
lively-kernel mailing list
[hidden email]
http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Local installation of Lively Core from Github: some notes, questions, and errors

milan zimmermann
Jens, Fabian, Robert:

Thanks all for your comments - this was really helpful. I will mark
this thread for my next round of installation. Below I just summarize
topics and responses, more or less for myself:

- the save problem is not lively related, just WebDAV likely my
permission problem to check into
- the format error can be fixed by pulling the bootstrap as Jens did
- authentication is done through regular Apache digest config (just
need to set it up right), no interaction with Lively
- PartsBin items can be served either via SVN repo or SVN working copy
as explained (I will likely use working copy for now so I can update
easily and not worry about local versions for now)
- LivelyKernel is served from git repo (=working copy) so this should
be locally versioned as is

I will report here any further successes or questions,

Thanks again

Milan

On Tue, Feb 28, 2012 at 2:27 PM, Robert Krahn
<[hidden email]> wrote:

> a) Just installing the LivelyKernel files from Github under proper
>
> apache directory  (as files - is WebDAV needed for this?) gives us
>
> LivelyKernel functionality, correct? [subquestion that I can answer by
>
> experimenting - what is the LivelyKernel functionality?]
>
>
> Really good question ;-)
>
> As of now:
> - bootstrap process
> - class system
> - extensions to JS objects
> - "Network" abstraction
> - module system
> - data bindings
> - serialization
> - test framework
> - Lively morphic v2
>
> Currently also an OMeta integration and based on that a JavaScript parser
> and
> interpreter are included.
>
> We will working on shrinking that however. This is one of the main reasons
> for
> creating that "fork". See this wiki entry for our motivation.
_______________________________________________
lively-kernel mailing list
[hidden email]
http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Local installation of Lively Core from Github: some notes, questions, and errors

Conrad Calmez
Hello,

today I sat down and had a look at the installation process of Lively
Kernel on Debian and Mac OS X.
I reworked the installation notes and the Apache configurations for
Linux.  I also added the Apache cofiguration (as well as the
corresponding description) to my GitHub fork for the LivelyKernel
repository.
I just saw that the markdown is not perfect, but it is still readable.
I created a pull request to get my changes in
https://github.com/rksm/LivelyKernel.

@Milan: If you want to have a look at that go to
https://github.com/calmez/LivelyKernel  (esp. INSTALL.md)
(I am really sorry, that I am maybe too late with my help)

If there are any open questions to my changes, I will be happy to answer them.


-- Conrad

On Wed, Feb 29, 2012 at 5:54 AM, Milan Zimmermann
<[hidden email]> wrote:

> Jens, Fabian, Robert:
>
> Thanks all for your comments - this was really helpful. I will mark
> this thread for my next round of installation. Below I just summarize
> topics and responses, more or less for myself:
>
> - the save problem is not lively related, just WebDAV likely my
> permission problem to check into
> - the format error can be fixed by pulling the bootstrap as Jens did
> - authentication is done through regular Apache digest config (just
> need to set it up right), no interaction with Lively
> - PartsBin items can be served either via SVN repo or SVN working copy
> as explained (I will likely use working copy for now so I can update
> easily and not worry about local versions for now)
> - LivelyKernel is served from git repo (=working copy) so this should
> be locally versioned as is
>
> I will report here any further successes or questions,
>
> Thanks again
>
> Milan
>
> On Tue, Feb 28, 2012 at 2:27 PM, Robert Krahn
> <[hidden email]> wrote:
>> a) Just installing the LivelyKernel files from Github under proper
>>
>> apache directory  (as files - is WebDAV needed for this?) gives us
>>
>> LivelyKernel functionality, correct? [subquestion that I can answer by
>>
>> experimenting - what is the LivelyKernel functionality?]
>>
>>
>> Really good question ;-)
>>
>> As of now:
>> - bootstrap process
>> - class system
>> - extensions to JS objects
>> - "Network" abstraction
>> - module system
>> - data bindings
>> - serialization
>> - test framework
>> - Lively morphic v2
>>
>> Currently also an OMeta integration and based on that a JavaScript parser
>> and
>> interpreter are included.
>>
>> We will working on shrinking that however. This is one of the main reasons
>> for
>> creating that "fork". See this wiki entry for our motivation.
> _______________________________________________
> lively-kernel mailing list
> [hidden email]
> http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel
_______________________________________________
lively-kernel mailing list
[hidden email]
http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Local installation of Lively Core from Github: some notes, questions, and errors

milan zimmermann
On Wed, Feb 29, 2012 at 6:19 PM, Conrad Calmez
<[hidden email]> wrote:

> Hello,
>
> today I sat down and had a look at the installation process of Lively
> Kernel on Debian and Mac OS X.
> I reworked the installation notes and the Apache configurations for
> Linux.  I also added the Apache cofiguration (as well as the
> corresponding description) to my GitHub fork for the LivelyKernel
> repository.
> I just saw that the markdown is not perfect, but it is still readable.
> I created a pull request to get my changes in
> https://github.com/rksm/LivelyKernel.
>
> @Milan: If you want to have a look at that go to
> https://github.com/calmez/LivelyKernel  (esp. INSTALL.md)
> (I am really sorry, that I am maybe too late with my help)

Hi Conrad:

This is great, thanks, I will not have time to get back to it fully
until weekend anyway, any notes and experience help. I started to
script the whole installation process in a shell script which is
slowing me down, repeatability is good but it is slow to achieve and
the process hurts...

To all:

I have a general question: If I decide to keep PartsBin in an actual
SVN repo for versioning: Let's say I first bootstrap PartsBin using
the script that uses

   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?]

thanks
milan

>
> If there are any open questions to my changes, I will be happy to answer them.
>
>
> -- Conrad
>
> On Wed, Feb 29, 2012 at 5:54 AM, Milan Zimmermann
> <[hidden email]> wrote:
>> Jens, Fabian, Robert:
>>
>> Thanks all for your comments - this was really helpful. I will mark
>> this thread for my next round of installation. Below I just summarize
>> topics and responses, more or less for myself:
>>
>> - the save problem is not lively related, just WebDAV likely my
>> permission problem to check into
>> - the format error can be fixed by pulling the bootstrap as Jens did
>> - authentication is done through regular Apache digest config (just
>> need to set it up right), no interaction with Lively
>> - PartsBin items can be served either via SVN repo or SVN working copy
>> as explained (I will likely use working copy for now so I can update
>> easily and not worry about local versions for now)
>> - LivelyKernel is served from git repo (=working copy) so this should
>> be locally versioned as is
>>
>> I will report here any further successes or questions,
>>
>> Thanks again
>>
>> Milan
>>
>> On Tue, Feb 28, 2012 at 2:27 PM, Robert Krahn
>> <[hidden email]> wrote:
>>> a) Just installing the LivelyKernel files from Github under proper
>>>
>>> apache directory  (as files - is WebDAV needed for this?) gives us
>>>
>>> LivelyKernel functionality, correct? [subquestion that I can answer by
>>>
>>> experimenting - what is the LivelyKernel functionality?]
>>>
>>>
>>> Really good question ;-)
>>>
>>> As of now:
>>> - bootstrap process
>>> - class system
>>> - extensions to JS objects
>>> - "Network" abstraction
>>> - module system
>>> - data bindings
>>> - serialization
>>> - test framework
>>> - Lively morphic v2
>>>
>>> Currently also an OMeta integration and based on that a JavaScript parser
>>> and
>>> interpreter are included.
>>>
>>> We will working on shrinking that however. This is one of the main reasons
>>> for
>>> creating that "fork". See this wiki entry for our motivation.
>> _______________________________________________
>> lively-kernel mailing list
>> [hidden email]
>> http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel
_______________________________________________
lively-kernel mailing list
[hidden email]
http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Local installation of Lively Core from Github: some notes, questions, and errors

Lincke, Jens
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.

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.

Meanwhile you can always copy your changes files for parts and pages and commit them 
with the svn tools.

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
[hidden email]
http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Local installation of Lively Core from Github: some notes, questions, and errors

milan zimmermann
On Thu, Mar 1, 2012 at 11:01 AM, Jens Lincke
<[hidden email]> 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
[hidden email]
http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Local installation of Lively Core from Github: some notes, questions, and errors

milan zimmermann
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
<[hidden email]> wrote:

> On Thu, Mar 1, 2012 at 11:01 AM, Jens Lincke
> <[hidden email]> 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
[hidden email]
http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel

lively-core-from-github-local-install-one-server.sh (23K) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Local installation of Lively Core from Github: some notes, questions, and errors

Lawson English-2
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
[hidden email] wrote:
On Thu, Mar 1, 2012 at 11:01 AM, Jens Lincke
[hidden email] 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
[hidden email]
http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel


_______________________________________________
lively-kernel mailing list
[hidden email]
http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: 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 <[hidden email]> 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
> <[hidden email]> wrote:
>
> On Thu, Mar 1, 2012 at 11:01 AM, Jens Lincke
> <[hidden email]> 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
> [hidden email]
> http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel
>
>
>
> _______________________________________________
> lively-kernel mailing list
> [hidden email]
> http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel
>
_______________________________________________
lively-kernel mailing list
[hidden email]
http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Local installation of Lively Core from Github: some notes, questions, and errors

Lawson English-2
On 3/8/12 11:38 PM, Milan Zimmermann wrote:
> 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)
>

Actually, I was thinking in more simplistic terms of simply a one-click
localhost install of the current version of LK. Versioning and so on
wasn't what I was concerned with. Having to set up apache, etc., in
order to simply play with LK seems to be a rather larger hurdle to
expect people to overcome just to play with a private sandbox.


L
_______________________________________________
lively-kernel mailing list
[hidden email]
http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Local installation of Lively Core from Github: some notes, questions, and errors

Fabian Bornhofen-2
On Fri, Mar 9, 2012 at 4:21 AM, Lawson English <[hidden email]> wrote:
> Actually, I was thinking in more simplistic terms of simply a one-click
> localhost install of the current version of LK. Versioning and so on wasn't
> what I was concerned with. Having to set up apache, etc., in order to simply
> play with LK seems to be a rather larger hurdle to expect people to overcome
> just to play with a private sandbox.

I completely agree.
At this point, we would need a WebDAV HTTP server in Squeak in order
to make Lively run from a one-click Squeak image. If you know such a
server, please let us know.

Technically, WebDAV is only a design decision. We might want to
decouple our tools from DAV and think of a simpler protocol for Lively
installations that do not need DAV SVN versioning.

WebDAV is pretty awesome the moment it works, but getting there can be painful.

Best,
Fabian
_______________________________________________
lively-kernel mailing list
[hidden email]
http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Local installation of Lively Core from Github: some notes, questions, and errors

Lawson English-2
I dont' know anything about Aida OR WebDAV but I found this link:

http://www.aidaweb.si/webdav%20support


Promising?


L.



On 3/9/12 7:18 PM, Fabian Bornhofen wrote:

> On Fri, Mar 9, 2012 at 4:21 AM, Lawson English<[hidden email]>  wrote:
>> Actually, I was thinking in more simplistic terms of simply a one-click
>> localhost install of the current version of LK. Versioning and so on wasn't
>> what I was concerned with. Having to set up apache, etc., in order to simply
>> play with LK seems to be a rather larger hurdle to expect people to overcome
>> just to play with a private sandbox.
> I completely agree.
> At this point, we would need a WebDAV HTTP server in Squeak in order
> to make Lively run from a one-click Squeak image. If you know such a
> server, please let us know.
>
> Technically, WebDAV is only a design decision. We might want to
> decouple our tools from DAV and think of a simpler protocol for Lively
> installations that do not need DAV SVN versioning.
>
> WebDAV is pretty awesome the moment it works, but getting there can be painful.
>
> Best,
> Fabian
>

_______________________________________________
lively-kernel mailing list
[hidden email]
http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Local installation of Lively Core from Github: some notes, questions, and errors

Fabian Bornhofen-2
Indeed, thanks!

Best,
Fabian

On Fri, Mar 9, 2012 at 6:29 PM, Lawson English <[hidden email]> wrote:

> I dont' know anything about Aida OR WebDAV but I found this link:
>
> http://www.aidaweb.si/webdav%20support
>
>
> Promising?
>
>
> L.
>
>
>
>
> On 3/9/12 7:18 PM, Fabian Bornhofen wrote:
>>
>> On Fri, Mar 9, 2012 at 4:21 AM, Lawson English<[hidden email]>  wrote:
>>>
>>> Actually, I was thinking in more simplistic terms of simply a one-click
>>> localhost install of the current version of LK. Versioning and so on
>>> wasn't
>>> what I was concerned with. Having to set up apache, etc., in order to
>>> simply
>>> play with LK seems to be a rather larger hurdle to expect people to
>>> overcome
>>> just to play with a private sandbox.
>>
>> I completely agree.
>> At this point, we would need a WebDAV HTTP server in Squeak in order
>> to make Lively run from a one-click Squeak image. If you know such a
>> server, please let us know.
>>
>> Technically, WebDAV is only a design decision. We might want to
>> decouple our tools from DAV and think of a simpler protocol for Lively
>> installations that do not need DAV SVN versioning.
>>
>> WebDAV is pretty awesome the moment it works, but getting there can be
>> painful.
>>
>> Best,
>> Fabian
>>
>
_______________________________________________
lively-kernel mailing list
[hidden email]
http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel
Loading...