Re: in the spirit of RosettaCode...

[Erik Gustafson]

Hi list,

I think heroku would probably be best as it's similar to how others in the
todo-backend have done it. It would also be good to demonstrate how to
deploy a picolisp app to heroku.


I made a handful of attempts at getting PL deployed to Heroku this past
week. Humbly, I admit defeat for the moment.

The Heroku documentation makes it seem straightforward:

https://devcenter.heroku.com/articles/git

https://devcenter.heroku.com/articles/container-registry-and-runtime

I was hoping I could simply plug the docker-tinycore-picolisp image into
Heroku with slight variations of the above articles. It must be possible!
My attempts, however, were greeted with a storm of different error messages
each time. Someone with a bit more knowledge of Docker and these types of
systems might be able to make it work.

I suppose the "right" way to deploy PL to Heroku would be to create a
custom buildpack:

https://devcenter.heroku.com/articles/buildpack-api

https://sendgrid.com/blog/create-first-heroku-buildpack/

That lies beyond my interest (at the time of writing this mail, at least).
I'll keep it in mind for when I'm feeling adventurous again :P

Erik

Re: in the spirit of RosettaCode...

[Joe Bogner]

Thanks Erik! I've updated app-persist

To run it, I was also thinking heroku or hyper.sh is interesting (minimal
expense). For either one, I was thinking of creating a docker container.

I have a minimal, non-picolisp, example at:
https://github.com/joebo/docker-tinycore-jhs

There is also https://github.com/iprog4u/docker-tinycore-picolisp, although
I might modify that to pull latest picolisp and compile

Lastly, a free amazon micro instance could suffice

I have a shell on digitalocean that I use, but I don't particularly want to
maintain the app going forward


I think heroku would probably be best as it's similar to how others in the
todo-backend have done it. It would also be good to demonstrate how to
deploy a picolisp app to heroku. I just don't have time at the moment to
try it out. Thanks for the help!

Joe


On Fri, Mar 17, 2017 at 7:46 PM, Erik Gustafson 
wrote:

> Hi Joe,
>
> Thanks for your work on this!
>
>
> Minor note - app-persist.l starts with
>
># non-persistent version ...
>
> To get your implementation listed, we need it running live somewhere. Do
> you have a favorite method for that? I'm happy to look into using Heroku
> this weekend.
>
> It was a fun exercise. I would like to write a wiki article about it and
> possibly even create a video to show my workflow
>
>
> I would especially love to see this video if you make it!
>
> Cheers,
> Erik
>
>

Re: in the spirit of RosettaCode...

[Erik Gustafson]

Hi Joe,

Thanks for your work on this!


Minor note - app-persist.l starts with

   # non-persistent version ...

To get your implementation listed, we need it running live somewhere. Do
you have a favorite method for that? I'm happy to look into using Heroku
this weekend.

It was a fun exercise. I would like to write a wiki article about it and
possibly even create a video to show my workflow


I would especially love to see this video if you make it!

Cheers,
Erik

Re: in the spirit of RosettaCode...

[Joe Bogner]

I've completed this. I haven't yet contributed it to the todobackend.com
site. If someone wants to do that I'd be grateful

https://github.com/joebo/todo-backend-pil/

There are two versions - in-memory (non-persistent)  and persistent using
the picolisp db. All tests are passing.

It was a fun exercise. I would like to write a wiki article about it and
possibly even create a video to show my workflow


On Wed, Mar 1, 2017 at 9:36 PM, Joe Bogner <joebog...@gmail.com> wrote:

> Hi Dave, I am hoping to find some time over the next few days to work on
> this and will send a note when I have some progress. It looks like an
> interesting challenge and similar to the todo work I already did. Thanks
> for sharing.
>
> Thanks,
> Joe
>
> On Wed, Mar 1, 2017 at 11:13 AM, Loyall, David <david.loy...@nebraska.gov>
> wrote:
>
>> >>>> In the spirit of RosettaCode, may I present
>> http://www.todobackend.com/ ?
>> >>>
>> >>> Seems I should give it a try :)
>> >>>
>> >>> I don't understand the full extent of the task yet, but could it be
>> >>> something
>> >>
>> >> To be correct, I don't understand it at all!
>> >>
>> >> Is the only "spec" a bunch of JavaScript sources? I don't feel like
>> >> wanting to analyze that, sorry!
>> >
>> > Another clue could be to look at the server end:
>> >
>> > For instance one in Python
>> >
>> > https://github.com/KixPanganiban/todo-falcon/blob/master/todo.py
>> >
>> >
>> > AFAIK the whole thing is like a "hello world" for persistence on the
>> server and a very light GUI on the client.
>>
>> Visit http://www.todobackend.com/client/index.html?https://todo-
>> backend-clojure.herokuapp.com/todos for example.
>>
>> This is a javascript client.  It speaks to some backend.  Which backend
>> is actually configurable.  The main site lists dozens.
>>
>> So the goal is to make a picolisp backend which is compatible with this
>> client.
>>
>> For language learners, once they know a few of these backends... they
>> will be able to learn about new languages by reading the source code of
>> other backends.
>>
>> For daily grind developers, they can compare frameworks, I guess. :)
>>
>> I guess "backend" here means a RESTful API.  (I'm probably misusing the
>> term.)
>>
>> You don't have a read the javascript "spec", you can run this:
>> http://www.todobackend.com/specs/index.html
>>
>> What it does is connect to any backend and attempt to perform actions
>> that are expected to be implemented.  (I wonder if anyone has used "machine
>> learning" to implement a compliant backend...)
>>
>> Cheers,
>> --Dave
>>
>
>

Re: in the spirit of RosettaCode...

[Joe Bogner]

Hi Dave, I am hoping to find some time over the next few days to work on
this and will send a note when I have some progress. It looks like an
interesting challenge and similar to the todo work I already did. Thanks
for sharing.

Thanks,
Joe

On Wed, Mar 1, 2017 at 11:13 AM, Loyall, David <david.loy...@nebraska.gov>
wrote:

> >>>> In the spirit of RosettaCode, may I present
> http://www.todobackend.com/ ?
> >>>
> >>> Seems I should give it a try :)
> >>>
> >>> I don't understand the full extent of the task yet, but could it be
> >>> something
> >>
> >> To be correct, I don't understand it at all!
> >>
> >> Is the only "spec" a bunch of JavaScript sources? I don't feel like
> >> wanting to analyze that, sorry!
> >
> > Another clue could be to look at the server end:
> >
> > For instance one in Python
> >
> > https://github.com/KixPanganiban/todo-falcon/blob/master/todo.py
> >
> >
> > AFAIK the whole thing is like a "hello world" for persistence on the
> server and a very light GUI on the client.
>
> Visit http://www.todobackend.com/client/index.html?https://
> todo-backend-clojure.herokuapp.com/todos for example.
>
> This is a javascript client.  It speaks to some backend.  Which backend is
> actually configurable.  The main site lists dozens.
>
> So the goal is to make a picolisp backend which is compatible with this
> client.
>
> For language learners, once they know a few of these backends... they will
> be able to learn about new languages by reading the source code of other
> backends.
>
> For daily grind developers, they can compare frameworks, I guess. :)
>
> I guess "backend" here means a RESTful API.  (I'm probably misusing the
> term.)
>
> You don't have a read the javascript "spec", you can run this:
> http://www.todobackend.com/specs/index.html
>
> What it does is connect to any backend and attempt to perform actions that
> are expected to be implemented.  (I wonder if anyone has used "machine
> learning" to implement a compliant backend...)
>
> Cheers,
> --Dave
>

RE: in the spirit of RosettaCode...

[Loyall, David]

>>>> In the spirit of RosettaCode, may I present http://www.todobackend.com/ ?
>>>
>>> Seems I should give it a try :)
>>>
>>> I don't understand the full extent of the task yet, but could it be 
>>> something
>> 
>> To be correct, I don't understand it at all!
>> 
>> Is the only "spec" a bunch of JavaScript sources? I don't feel like 
>> wanting to analyze that, sorry!
>
> Another clue could be to look at the server end:
> 
> For instance one in Python
> 
> https://github.com/KixPanganiban/todo-falcon/blob/master/todo.py
> 
> 
> AFAIK the whole thing is like a "hello world" for persistence on the server 
> and a very light GUI on the client.

Visit 
http://www.todobackend.com/client/index.html?https://todo-backend-clojure.herokuapp.com/todos
 for example.

This is a javascript client.  It speaks to some backend.  Which backend is 
actually configurable.  The main site lists dozens.

So the goal is to make a picolisp backend which is compatible with this client.

For language learners, once they know a few of these backends... they will be 
able to learn about new languages by reading the source code of other backends.

For daily grind developers, they can compare frameworks, I guess. :)

I guess "backend" here means a RESTful API.  (I'm probably misusing the term.)

You don't have a read the javascript "spec", you can run this: 
http://www.todobackend.com/specs/index.html 

What it does is connect to any backend and attempt to perform actions that are 
expected to be implemented.  (I wonder if anyone has used "machine learning" to 
implement a compliant backend...)

Cheers,
--Dave
PԔ � )mX�����zV�u�.n7�

Re: in the spirit of RosettaCode...

[Jakob Eriksson]

Another clue could be to look at the server end:

For instance one in Python

https://github.com/KixPanganiban/todo-falcon/blob/master/todo.py


AFAIK the whole thing is like a "hello world" for persistence on the
server and a very light GUI on the client.



On 2017-03-01 08:46, Alexander Burger wrote:
> On Tue, Feb 28, 2017 at 05:21:52PM +0100, Alexander Burger wrote:
>>> In the spirit of RosettaCode, may I present http://www.todobackend.com/ ?
>>
>> Seems I should give it a try :)
>>
>> I don't understand the full extent of the task yet, but could it be something
> 
> To be correct, I don't understand it at all!
> 
> Is the only "spec" a bunch of JavaScript sources? I don't feel like wanting to
> analyze that, sorry!
> 
> ♪♫ Alex
> 
-- 
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Re: in the spirit of RosettaCode...

[Alexander Burger]

On Tue, Feb 28, 2017 at 05:21:52PM +0100, Alexander Burger wrote:
> > In the spirit of RosettaCode, may I present http://www.todobackend.com/ ?
> 
> Seems I should give it a try :)
> 
> I don't understand the full extent of the task yet, but could it be something

To be correct, I don't understand it at all!

Is the only "spec" a bunch of JavaScript sources? I don't feel like wanting to
analyze that, sorry!

♪♫ Alex
-- 
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Re: in the spirit of RosettaCode...

[Alexander Burger]

On Tue, Feb 28, 2017 at 05:21:52PM +0100, Alexander Burger wrote:
> Hi Loyall,

Oops! I mean "Hi Dave!" :)
-- 
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Re: in the spirit of RosettaCode...

[Joe Bogner]

Hi David, Alex

Not exactly the same thing (both front-end and back-end)... I created a
todo example last year: https://github.com/joebo/pil-mithril-todo. This is
not a pure pil way since it uses a javascript framework - so it could be a
PicoLisp / Mithril.js combo. It would be nice to see a pure pil way. If
someone else wants to take it on, they might be able to use what I have as
a starting point (feel free!)

To see my example: I restarted the example at http://csilo.com:8088/
username: admin , password: admin ... It takes a few seconds to log in due
the bcrypt hashing

Thanks,
Joe

On Tue, Feb 28, 2017 at 11:21 AM, Alexander Burger <a...@software-lab.de>
wrote:

> Hi Loyall,
>
> > In the spirit of RosettaCode, may I present http://www.todobackend.com/
> ?
>
> Seems I should give it a try :)
>
> I don't understand the full extent of the task yet, but could it be
> something
> similar to http://picolisp.com/wiki/?mindbgui with some modifications and
> extensions?
>
> ♪♫ Alex
> --
> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
>

Re: in the spirit of RosettaCode...

[Alexander Burger]

Hi Loyall,

> In the spirit of RosettaCode, may I present http://www.todobackend.com/ ?

Seems I should give it a try :)

I don't understand the full extent of the task yet, but could it be something
similar to http://picolisp.com/wiki/?mindbgui with some modifications and
extensions?

♪♫ Alex
-- 
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

in the spirit of RosettaCode...

[Loyall, David]

In the spirit of RosettaCode, may I present http://www.todobackend.com/ ?

Perhaps one of you skilled picolisp folks could submit a new implementation to 
their growing list.

Cheers,
--Dave
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe