Re: Announcement: PicoLisp in a docker container

[David Bloom]

It's not nearly that cool yet.  I must have updated the version without
updating the docs a while back. While updating the docs I noticed that
there's yet a newer version out.

Isn't there already a script somewhere that pings the download page of
picolisp.com for a newer version?  I'd like to stay on top of versioning.
I'm new to maintaining an open source product and strive to one day meet
the responsiveness and helpfulness that many others have been to me in this
forum.

-David

On Aug 22, 2016 5:15 AM, "Jon Kleiser"  wrote:

> Thanks again, David!
>
> When I run this and do “(version)”, I get 16.5.30, while your docs says
> “This is version 16.2”. I guess one gets the current stable release version
> when one does the “docker pull”. Is that right?
>
> /Jon
>
> > On 22. Aug, 2016, at 02:00, David Bloom  wrote:
> >
> > Docs updated.  Sorry it took me so long.  I'll be quicker to respond in
> the future.  Added a --rm to automatically remove the container upon exit

Re: Announcement: PicoLisp in a docker container

[Jon Kleiser]

Thanks again, David!

When I run this and do “(version)”, I get 16.5.30, while your docs says “This 
is version 16.2”. I guess one gets the current stable release version when one 
does the “docker pull”. Is that right?

/Jon

> On 22. Aug, 2016, at 02:00, David Bloom  wrote:
> 
> Docs updated.  Sorry it took me so long.  I'll be quicker to respond in the 
> future.  Added a --rm to automatically remove the container upon exit.  That 
> way you don't have to manually remove any cruft left over in docker ps -a.  
> Optionally you can decide not to use the --rm switch and be able to inspect 
> the container after exit.
> 
> https://hub.docker.com/r/progit/docker-tinycore-picolisp/
> 
> Enjoy!
> 
> On Mon, Aug 15, 2016 at 9:31 AM, Jon Kleiser  wrote:
> Thanks a lot, David!
> 
> /Jon
> 
> > On 15. Aug, 2016, at 13:57, David Bloom  wrote:
> >
> > Pardon the delay Jon,  I've been under extreme amounts of stress but not
> > for much longer.  I'll update the docs to reflect getting a Tinycore prompt
> > rather than just a REPL.
> >
> > On Aug 15, 2016 6:08 AM, "Jon Kleiser"  wrote:
> >
> >> I just want to report that my use of “docker run -v” was not correct. This
> >> works much better:
> >>
> >> docker run -v /Users/jkleiser/script:/opt/script -it
> >> progit/docker-tinycore-picolisp
> >>
> >> I can then do things like (dir "/opt/script") or (in "/opt/script/foo.sh"
> >> (echo)) from inside PicoLisp.
> >>
> >> /Jon
> >>
> >>> On 12. Aug, 2016, at 16:40, Jon Kleiser  wrote:
> >>>
> >>> Hi David,
> >>>
> >>> I have now tried your container as described at
> >> https://hub.docker.com/r/progit/docker-tinycore-picolisp/, and I got
> >> PicoLisp version 16.5.30 running. Does your container allow me to get
> >> access to the Tinycore Linux command line?
> >>>
> >>> I need to load a PicoLisp file I have on my Mac. I have tried starting
> >> your container like this:
> >>> docker run -v /Users/jkleiser/script -it progit/docker-tinycore-picolisp
> >>> but when I from inside PicoLisp do (dir "/Users/jkleiser/script”), I
> >> just get NIL, so for some reason sharing the OS X file system with your
> >> container doesn’t work at the moment. Maybe the container has to be set up
> >> for the new ‘osxfs’ shared file system solution? I don’t know.
> >>>
> >>> If I could get at the Tinycore Linux CLI, then I could maybe get my
> >> PicoLisp file by use of wget or curl (if I put the file on the net first)
> 
>