On 27.03.2016 03:49, brian.dunbar(a)gmail.com wrote:
New to cockpit - a co-worker mentioned it last week and it seems
pretty nifty. I'm curious if it's a good fit for a project of mine.
I want to host Open Bazaar servers (https://openbazaar.org/
_like_ to give my users access a GUI as 'a' user to run a limited set
of functions such as ..
* start / stop a service * look at a log file * run a predefined set
of API calls using CURL * run a predefined script to backup a
Cockpit provides login access to a system. So the user can perform the
various actions that they could if they logged into the system in a
terminal (for example).
So in total you would need to:
1. Make sure that the same user logged if in on the terminal
can perform the same tasks. See below for a twist.
2. Build a Cockpit UI package to expose just those tasks.
Is Cockpit a good fit?
Not without work.
In theory if you do already have a REST API that encapsulates what you
want the user to do, and provides authentication for users, you can
probably do something similar to what the Cockpit Kubernetes container
does, and provide access just to that API:
But it's a bit complicated to make this work and requires lots of bits
to coordinate on what they expect to happen.