Building Cockpit together

(Giacomo Sanchietti) #21

My bad: we do not have a document describing the road map. You can find some info in the forum, we also talked a bit together at FOSDE, and finally some marginal notes ares on my private workstation :smiley:

We are focusing now on 3 main tasks:

(David) #22

Thanks for the explanation! :grinning:
Would it be a good idea to move this information to the Project feature of GitHub?
I also noticed that the issue-tab is disabled in the cockpit repository, is that intentional?

(Edoardo Spadoni) #23

The issue tab is disabled because all issues are centralized here:

(Giacomo Sanchietti) #24

Once we used the project board inside the cockpit repo to track the first alpha.
The problem is keeping it up to date, honestly I don’t have the time to do it :frowning:

Still, there is a NS board here:

(David) #25

Okay, I understand that these things need fostering…
However this makes it difficult for new guys like my to find their way into the codebase and get an overview. Also a issue-list of not-too-hard bugs or easy features would be very helpful in order to find my way into the code. This is where a project board combined with a separate issue list would be very helpful!

(Davide Principi) #26

Now there’s an Ejabberd Cockpit application on development:

According to Cockpit guidelines, we must rework our code to remove the “content-security-policy” directive from “manifest.json” files:“content-security-policy”&type=Code

To make the Ejabberd Cockpit UI work without the blamed CSP “unsafe-inline” directive the JS code was separated from the HTML partials code.

  • <script> tag contents goes to app.js or other static JS file
  • style= HTML attributes cannot be used

We could fix the “nethserver-cockpit-empty” kickstart repo accordingly, starting from here for example:

What do you think?

(Giacomo Sanchietti) #27

This seems a reasonable limitation to have better security, but does it work with VueJS? I have no idea, maybe @edoardo_spadoni can help us here.

If it works and doesn’t break existing things, go with with CSP enabled.

(Giacomo Sanchietti) #28

You could start with some simple applications which need porting like fail2ban, UPS or nextcloud.

Take a look to and for some inspiration! :wink:

(Axel Urbanski) #29

some bad question…

  • Whats about securety with cockpit?

  • witch web browser ist save for using cockpit ?

  • did cockpit uses java ?

thx axel

(Giacomo Sanchietti) #30

You can find many info online.

No, thanks god! :smiley:

(Federico Ballarini) #31

We can load pages without taking a coffee break :smile:

(Giacomo Sanchietti) #32

As request by @dasois, @davidep has created a Cockpit board:

We will try to keep it updated!

(Rob Bosch) #33

but… but… I like coffee :coffee:

(David) #34

Sick! Thank you! :smile:

(Alessio Fattorini) #35

Wonderful news! I love that

(David) #36

My personal top priority issue would be integration tests, so maybe we can include that into the project board?

(Giacomo Sanchietti) #37