Closed PierreBesson closed 7 years ago
There is already a docker image for this. look at the readme
Thanks & Regards, Deepu
On Sun, Sep 25, 2016 at 5:16 PM, Pierre Besson notifications@github.com wrote:
The idea is that people can run the JHipster studio with a "binary" (maybe published on NPM, or with docker). Then doing something like ‘jdl-studio entity.jh‘ will start a small server that serve the JDL-Studio front-end and synchronize it with the jdl file.
This could also be a way for a user to visualize all the app entities, once @cbornet https://github.com/cbornet's JSON reversing is done.
To me it seems a better solution than creating an editor specific plugin.
Maybe @flaviencathala https://github.com/flaviencathala can work on this, I think you will need a break from the angular migration from time to time. If nobody sees any objection to do this ?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/jhipster/jdl-studio/issues/23, or mute the thread https://github.com/notifications/unsubscribe-auth/ABDlFwiGmMN_c2EdDZV-i-Gt35Z53S3cks5qtl8UgaJpZM4KF4hJ .
This is not my idea, I want to have the JDL studio synchronize with a local file on my computer. Is this already possible now ?
What do you mean by synchronisation? Currently its possible to spawn a local instance using the docker image which serves the site on nginx.
Thanks & regards, Deepu
On 25 Sep 2016 18:31, "Pierre Besson" notifications@github.com wrote:
This is not my idea, I want to have the JDL studio synchronize with a local file on my computer. Is this already possible now ?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/jhipster/jdl-studio/issues/23#issuecomment-249420656, or mute the thread https://github.com/notifications/unsubscribe-auth/ABDlF5A2rPeJldza3hzxZTEzqGcibtiyks5qtnCjgaJpZM4KF4hJ .
I mean synchronize a .jdl file in the filesystem with what you see in the JDL studio UI.
Currently you need to import the file using the UI feature. But why do you want it to be synchronized? Sorry but im still a bit confused by the use case you mentioned. May be i didn't understand it well.
Thanks & regards, Deepu
On 25 Sep 2016 19:55, "Pierre Besson" notifications@github.com wrote:
I mean synchronize a .jdl file in the filesystem with what you see in the JDL studio UI.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/jhipster/jdl-studio/issues/23#issuecomment-249424594, or mute the thread https://github.com/notifications/unsubscribe-auth/ABDlF9MuPiXwVdGWxPztOiyTee2BrDagks5qtoRKgaJpZM4KF4hJ .
Never mind, maybe I'm not clear. The idea was that you wouldn't have to deal with importing and exporting manually to a file, it would just synchronize by itself with a file on your computer. I will talk about it directly with @jdubois next time I see him to see if this is worth doing it.
If you know what you are doing then you can very well go ahead. I have no issues with that.
Thanks & regards, Deepu
On 25 Sep 2016 20:39, "Pierre Besson" notifications@github.com wrote:
Never mind, maybe I'm not clear. The idea was that you wouldn't have to deal with importing and exporting manually to a file, it would just synchronize by itself with a file on your computer. I will talk about it directly with @jdubois https://github.com/jdubois next time I see him to see if this is worth doing it.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/jhipster/jdl-studio/issues/23#issuecomment-249426962, or mute the thread https://github.com/notifications/unsubscribe-auth/ABDlF6t14ZGuWOllLKXqEBKm7Ea8AEnwks5qto6ZgaJpZM4KF4hJ .
The idea is that people can run the JHipster studio with a "binary" (maybe published on NPM, or with docker). Then doing something like ‘jdl-studio entity.jh‘ will start a small server that serve the JDL-Studio front-end and synchronize it with the jdl file.
This could also be a way for a user to visualize all the app entities, once @cbornet's JSON reversing is done.
To me it seems a better solution than creating an editor specific plugin.
Maybe @flaviencathala can work on this, I think you will need a break from the angular migration from time to time. If nobody sees any objection to do this ?