Ticket #1267 (new task)

Opened 7 years ago

Last modified 4 years ago

decide on small webserver for the laptop

Reported by: sj Owned by: cscott
Priority: normal Milestone: 9.1.0-cancelled
Component: distro Version:
Keywords: Cc: lauren, mchua, mako
Action Needed: never set Verified: no
Deployments affected: Blocked By:
Blocking:

Description

There should be a small webserver on the laptop, so that children can publish web small services, and have webpages that interact with a local databsae [e.g., sqlite]. This would run as a background process by default. There have been a few suggestions of what to run; we should pick one and test it out.

Change History

Changed 7 years ago by krstic

  • owner changed from marco to krstic
  • status changed from new to assigned
  • milestone changed from Untriaged to BTest-3

Changed 7 years ago by krstic

  • component changed from web browser to infrastructure

Changed 7 years ago by sj

  • verified unset

update: this will be needed for a few things:

  • a good interactive atlas running in the browser,
  • a script that autogenerates an html view of what's in /home/olpc/Library

I'd like to decide on what minimal webbrowser we want to include and test one in T3.

Changed 7 years ago by sj

  • cc lauren added

adding lauren to cc:

Changed 7 years ago by cjb

If you'd like a first candidate, I think I'd recommend web.py.

Changed 7 years ago by lauren

If this ends up making it in to T3, we can close #2923 and #2924.

Changed 7 years ago by mchua

  • cc mchua added

Changed 7 years ago by jg

  • milestone changed from Trial-3 to V1.1

Changed 7 years ago by sj

on further discussion, cherry.py seems a more plausible candidate.

Changed 7 years ago by krstic

I'll try to take a look at this soon.

Changed 7 years ago by mako

  • cc mako added

webpy does not include a webserver. By default, it uses the simple webserver built into the Python standard library. It's got it's issue but it's alright. There has been talk on the web.py list of moving to using the cherrypy server which is apparently more flexible and faster.

It's not clear to me what our criteria are for deciding this except that it be small. I suppose will there will need to be a justification for anything other the one that is installed and that we are not using yet.

Changed 7 years ago by mako

Just as a quick follow up, there are several projects (e.g., MikMik, Josh Gay's annotation work, and the content library) that could use this if it were installed today and if it had WSGI support which I'm assuming it would.

Changed 6 years ago by cscott

  • owner changed from krstic to cscott
  • status changed from assigned to new
  • next_action set to never set
  • component changed from infrastructure to distro
  • milestone changed from Future Release to 9.1.0

Let's put this back on the roadmap for 9.1.0, along with revisiting the library story in general. (I'd like to integrate libraries more with an offline web cache, for instance.)

Changed 4 years ago by cjl

How about migrating this ticket to bugs.sugarlabs.org?

Note: See TracTickets for help on using tickets.