Thank you Joseph for sharing.
G Pascal
Am 11.08.2017 um 14:01 schrieb Joseph Nuthalapati:
> Since the community's showing interest in Cockpit, I'd like to point out
> a few things.
>
> Cockpit works on a web socket combined with http/https interface. That's
> the major problem with running
Since the community's showing interest in Cockpit, I'd like to point out
a few things.
Cockpit works on a web socket combined with http/https interface. That's
the major problem with running cockpit behind Apache2 as a reverse proxy.
Apache's websocket proxying support has been recently
On 10.08.2017 13:03, Pascal wrote:
I will try that. Just copying another proxy file from apache.
Some webapps only work on direkt Domains without subdir or alias behind it.
But Im sure it will work.
But reality told me it doesn't!
One Mime-type error for the css file: Stylesheet
I will try that. Just copying another proxy file from apache.
Some webapps only work on direkt Domains without subdir or alias behind it.
But Im sure it will work.
Auth is no Problem. Cockpit uses system users like fbx or ldap users can also
be used for access. So SSO works out of the box also
> Would be interesting to know if cockpit can run behind Apache under
> /cockpit. This would avoid having to meddle with the firewall and we
> can potentially do (SSO) authentication using Apache.
Couldn't that be achieved (circumvented) by configuring reverse proxy
setting for cockpit in
On Wednesday 09 August 2017 01:59 PM, heynmoeller wrote:
[...]
> Reload of firewalld seems to be needed to know/recognize cockpit as a
> service!
Ouch. firewalld does not seem to read new files placed in its services
directory automatically. If necessary we can take care of this when we
write
Hello,
cockpit was packaged for Debian on backports, I give it a try on fbx.
This is what I've done.
About Cockpit http://cockpit-project.org/running.html
Install Cockpit from Debian Backports to Freedombox:
https://packages.debian.org/stretch-backports/cockpit
I assume backports is a source
