search

pepkit / peppy

Project metadata manager for PEPs in Python
https://pep.databio.org/peppy
BSD 2-Clause "Simplified" License
36 stars 12 forks source link

reporting results or status to web #6

Closed nsheff closed 5 years ago

nsheff commented 8 years ago

long-term idea:

we could think about connecting to either a mysql server or to google spreadsheets using gspread, for updating run status, etc.

afrendeiro commented 8 years ago

Regardless of the user-facing implementation, we should have functions (in models) that report on the state of each job. Once we have that, building an app to monitor them is easy.

Ideas for that: Flask or Shiny. I'd obviously favor a Python based option, mostly for the interface with the existing platform.

We could have this as a command in looper like described in #4. Something like: $ looper serve Output: Looper running on localhost, port 4000: http://0.0.0.0:4000/ Now we have a server constantly updating the status of our jobs.

nsheff commented 8 years ago

great idea.

this does require looper to depend on pypiper output though.

afrendeiro commented 7 years ago

Just to update this issue (for which I've open the monitor branch):

There is a functioning implementation with Flask, which for now simply runs the summarize command and displays the summary sheet in a web interface.

Anyone willing to contribute is welcome, but for now it is something low-priority I guess.

nsheff commented 6 years ago

This issue became part of looper with the split. It is now part of a looper issue:

https://github.com/pepkit/looper/issues/30

nsheff commented 5 years ago

this has basically been implemented now in caravel