Re: [kuksa-dev] kuksa.ide

[Robert Höttger <robert.hoettger@xxxxxxxxxxxxxx>]

Dear Soheila,

you are correct.

The current kuksa.ide extensions are tested with docker images, which are used by the Kuksa App-publisher on the kuksa.ide side to be transmitted to the Kuksa cloud that runs Eclipse hawkBit and the Kuksa App Store (among others).

The Appmanager on the in-vehicle side then handles installation / update commands from Eclipse hawkBit.

The process of creating docker images and what they contain is currently very simple - but you should be pretty flexible with docker to create custom images / processes.

Best regards,

Robert

On Feb 27, 2020, at 11:29, SOHEILA DEHGHANZADEH <s.dehghanzadeh@xxxxxxxxxxxxx> wrote:

Dear All,

How does kuksa.ide connects with kuksa.cloud and kuksa.invehicle? My understanding is that the app server is the connection point. That means the app written in kuksa.ide goes to the app server after being built successfully. is my understanding correct?
Does the app written in kuksa.ide goes through ci/cd? Can I attach the deployment code of the app to the app so that I can program how the application is being deployed ?

I appreciate any comments on this.

Best regards
Soheila


_______________________________________________
kuksa-dev mailing list
kuksa-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/kuksa-dev