Cockpit - the next iteration šŸ„

Releases
1

Itā€™s time for a new iteration of Cockpit. And Iā€™m more than happy to announce that a new major release is imminent.

Changes

CORE

  • redesigned admin ui
  • move from UIkit to a custom made frontend design system based on custom elements
  • replacing RiotJS with Vue
  • GraphQL support
  • PHP >= 8
  • admin ui for permissions & locales
  • built-in playground for REST & GraphQL API
  • enhanced field types

PRO

With the new version, there will be also an introduction of a pro version (commercial license) which will include the following addons:

  • CloudStorage: Save your assets on S3 (more providers are in the pipeline)
  • Layouts: manage component based lauyouts
  • Lokalize: manage i18n internationalization language strings
  • Pages: a page-centric approach to content creation and editing
  • Sync: Push or pull resources between different Cockpit instances
  • Webhooks: send HTTP requests on specific events

The pro version is meant to support the development and work on Cockpit and put its future on a healthy footing.

Youā€™re invited to test the new version. Get the code now:

Cheers,
Artur

7 Likes
2

Holy shit, itā€™s amazing!!!
wow

3

wow

4

Good day,

first of all nice that it goes on that pleased me very much. Basically once the question is a backward compatibility with old versions planned so that you can update. Or is to be seen as a completely new independent version, which will have nothing to do with the old version?

1 Like
5

Is there any effort to integrate type hints and clean objects?

I would love to see a proper DI container integrated. ^^

6

Completely new from scratch, different js ( old riot.js , new vue )

7

So our existing projectsā€¦ cant we ā€œupgradeā€ to the newer release, or back up and restore data kind of thingā€¦ or is it dead end ? :frowning:

8

Exactly the question I ask myself, basically it does not mean to me that if everything was extremely revised that it is no longer possible to upgrade. If the data structure was retained.

I had tested it myself once briefly in a short test the upgrade did not run. But maybe it is still planned that can probably only answer @artur.

9

The first big problem is Lack of proper documentation. now thisā€¦ :confused:

2 Likes
10

@fschuermeyer Data structure and field types changed and it is not planned to provide an auto migration option from the old version to the new one. Of course you can get paid migration support if needed.

@Cryptospy Cockpit was and still is an Open Source project. If you see that something is lacking, eg documentation, then feel invited to contribute to the project.

One of the reasons for the new pro version is to hire additional resources in the future to keep the docs updated and thrive Cockpits development.

Donations just didnā€™t work in the past to be able to commit and focus 100% on Cockpit (docs, guides etc).

Cheers
Artur

2 Likes
11

Wow! canā€™t wait to see a new design of Cockpit.

Just my opinion, TailwindCSS + Vite would be really cool.

1 Like
12

Will there be a performance boost in the GUI with many fields? (see Slow GUI load times)

13

I plan to use pro version that has so attractive addons! :+1:
Is there any details of pro license and price now?

15
1 Like
16

Same sparse documentation :frowning:

2 Likes
17

Hey! Nice job. I have a small problem. Canā€™t seem to find a way to create a new item in a collection trough the API. Canā€™t find the endpoint for saving data. Can you point me in the right direction please?

18

Mutation API will be available soon.

Greets
Artur

19

When using a Tags field: If you create an entry with a specific tag then delete that tag from the model it still shows in the json object for the entry. But if you go in an edit the entry, that deleted tag is not visible in the tag list and the only way to remove it from the json object is to update the tag field, which requires you to add or remove tags from the actual tag field.

Consider: Showing tags in the field that are not in the model with a different background color to indicate they are old/deleted/invalid. That way we can hit the (X) to remove and actually trigger that update, if we desire that content to be removed.

20

@pixelkarma Will look into that :+1:

21

Hello !
Thanks for the awsome job you made during all this years !
With the new version I have some questions :

  • Can i buy just one addon ?
  • Or Can i use a pro addons with some modifications for fit to my projects for free ?

I realy love your product but some time itā€™s just for small projects with low budget, and i didnā€™t need all the pro features.

1 Like