digital twin hub consolidate (June end)

[despiegk]

digital twin code has multiple parts now, this needs to be consolidated.

• filemanager backend

• chat backend (maybe same)

• twin frontend https://github.com/threefoldtech/digitaltwin/issues/269

• rest interface for twin back

• we need good organized code

• document what is where and how to use

• deploy using github actions and flist https://github.com/threefoldtech/digitaltwin/issues/270

[jdelrue]

Digitaltwin - publishingtools location:
https://github.com/threefoldtech/digitaltwin
Temporary spawner:
https://github.com/threefoldtech/digitaltwin_spawner

@despiegk @Hamdy How do we see publishingtools integrate with digitaltwin? To what extend do we need to merge these projects?

[jdelrue]

@JensMeire will make both startup so every DT has its own publishingtools

[ken-de-moor]

Implementing publishingserver is in progress. Meeting yesterday about how to tackle it and we've started work on it.

[Hamdy]

publishtools supports now vuejs apps as well including (digitaltwin) frontend
I mvoed the frontend repo to https://github.com/threefoldtech/www_digitaltwin so may be it's a good idea to continue development from there @ken-de-moor ?

[sasha-astiadi]

need reestimation

[sasha-astiadi]

@JensMeire please reestimate

[sasha-astiadi]

ken is on holiday, @JensMeire take over this story

[sasha-astiadi]

any spec changes please write here @JensMeire

[JensMeire]

Currently in a working , stable state. Making changes for CI/CD for staging and production.

[jdelrue]

Backend is now npm package and is added to publisher. https://www.npmjs.com/package/@threefoldjimber/digitaltwin-backend

Finishing up our deployment for demo platform, after that ticket can be closed

[JensMeire]

Publishtools does not work on docker build only at runtime, figuring out with @Hamdy

[Hamdy]

everything is working now thanks @JensMeire
we have one Docker that can run the whole thing

• publisher node server now is getting wikis from (publishtools develop)
• digitaltwin-lib it's a dependency that is added to package.json of our publisher
• digitaltwin frontend is now a normal website thta should be in sites.json by default
• redis server is running on the docker as well
• publihstools and nodeservers are running in tmux

[JensMeire]

Deployed on staging, to be tested

[sasha-astiadi]

@xmonader ready to move forward with deploy using github actions and flist prepare digitaltwin docker image + flist digitaltwin#270 #1065

[Hamdy]

Staging: http://Digitaltwin-test.jimbertesting.be
we still missing 2 things

• adjust to the new configuration style for publishtools (finished but not yet ported to staging)
• more docs