he surely is... ;)
This commit is contained in:
parent
93fcadefa9
commit
90d59778a6
4 changed files with 30 additions and 0 deletions
0
lib/frontends/__init__.py
Normal file
0
lib/frontends/__init__.py
Normal file
12
lib/frontends/frontends.py
Normal file
12
lib/frontends/frontends.py
Normal file
|
|
@ -0,0 +1,12 @@
|
|||
'''
|
||||
Just the frontends.py stub... ;)
|
||||
|
||||
If linspector is being started without a frontend "enabled" it just is doing stuff like: polling, alerting, logging etc.
|
||||
|
||||
Frontends a absolutely no requirement for running Linspector.
|
||||
'''
|
||||
|
||||
|
||||
class Frontends():
|
||||
def __init__(self, **kwargs):
|
||||
return
|
||||
6
lib/frontends/https.py
Normal file
6
lib/frontends/https.py
Normal file
|
|
@ -0,0 +1,6 @@
|
|||
'''
|
||||
A HTTPS frontend to the current Linspector instance.
|
||||
|
||||
A Webserver listening for requests to give information about the internal state of linspector.
|
||||
(maybe providing a JSON API to the instance too...)
|
||||
'''
|
||||
12
lib/frontends/lish.py
Normal file
12
lib/frontends/lish.py
Normal file
|
|
@ -0,0 +1,12 @@
|
|||
'''
|
||||
The Linspector Interactive Shell...
|
||||
|
||||
This will become an interface to Linspector at "start" time. Think about MidnightCommander... and then run
|
||||
Linspector in a screen session and not as daemon, why not? BTW.: Daemonization is at this point of development
|
||||
cancelled, because it makes no sense to daemonize everything. Linspector is a user software which will run in any
|
||||
screen session perfectly.
|
||||
'''
|
||||
|
||||
class LishFrontend(Frontends):
|
||||
def __init__(self, **kwargs):
|
||||
return
|
||||
Loading…
Add table
Add a link
Reference in a new issue