-
Notifications
You must be signed in to change notification settings - Fork 5
Release0.3.0 #130
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release0.3.0 #130
Conversation
pymongo upgrade is needed for security
both code files are currently not used and are therefore removed from the code base
Package upgrades
make execution forms user friendly for the execution create form it is now possible to add form fields in a more flexible way on demand rather then knowing in advance how much steps, parameters and ports should be added it can be configured to add a JSON Editor for showing the progress in the execution create and run form for execution runs a better workflow is provided: all that belongs to the run of an execution is now stored in one run object that can also be viewed in a json editor if configured.
refactor(dashboard execution pages): execution form user friendly
chore: remove unused code barfi and models
|
Hello @sabinem, I'm building and testing the ODTP GUI on my Windows machine. I'm going to list here my suggestions and bugs I'm catching:
A
How feasible is adding a button to create a new folder when setting the working directory?
The sidebar with the working area and other information is on the right, which feels a bit strange. Did you test the feeling of placing this to the right? Also, this sidebar disappears when the screen width is minimized.
In the tabs menu,
Change
Amazing way of adding steps to the workflow. Great work @sabinem!! Regarding the parameters from files, is there any way to change the icon or the color once you pick the parameters? Parameters overwriting: Change Ports. Change
Missing
Add the possibility to add secret fields. This is fine if the users needs it. However, make them "star" coded? Like I'm currently running the whole corsica pipeline. But Amazing work Sabine! |
|
@caviri I want to discuss with you on
I would like to postpone this, unless you help me solve the problem I have with this:
But the secrets are taken from file. And the GUI starts the CLI command. Otherwise I would have to call the WorkflowManager directly, but it a long running process and should rather run in the background, therefore I went with starting the CLI command. To be able to overwrite secrets, the CLI command would have to be changed, so that is not only takes files but also variables. I would suggest to leave it as it is for now, since it is possible to provide secrets, you just have to add them via files. |
it should be accessible via the execution page
align in a reliable way with markdown add more links on the homepage
integrate it into the page, so that it does not disappear when the page width is reduced leave out unnecessary information
add functionality that user can create a new directory as working directory
automatically select a user when it has been added
adding versiob is now part of options for components the workarea is integretd into the page
since the function is now only used here
use a common layout for all dashboard pages
automatically select a digital twin when it has been added
when parameters files are uploaded for components, then add a check mark, so that the users know that this has been done succcessfully
that way there can be more progress seen in the dashboard logging when the steps are run also seperate log level on runs from the general log level
…n-dockerfile Feature/make sources editable in dockerfile
|
@caviri Can you please take another look at the PR and approve if possible. I have followed up on your suggestions and also added the following features:
|
|
Hello @sabinem, thank you! Can we have a two docker compose? One for dev and the other for "production"? It can happen that some users might change the branch on local potentially affecting to the files located on the docker, so I think it's better to reduce the amount of volumes mounted. What do you think? |
Make code base editable in docker compose depending on a variable in the `.env` file * feat: Add pip install args * fix(compose.yml): mount docker service --------- Co-authored-by: Gabriel Nützi <[email protected]> Co-authored-by: sabinem <[email protected]>
|
@caviri We added a setting that decides whether the code base will be editable. Hope this is considered by you good enough to take care of your concern on not having the code base editable in production. |
add log level settings and app path setting
|
Good morning @sabinem, not fully convinced. What would be the point of having an Also we can take the opportunity to simplify the "production" compose by uploading the image to dockerhub and making not necessary to clone the repo and build the image in order to deploy the platform. |
|
Hi, no, I think that it’s a good idea for developers. I was just worried about non experts users.
… On 19 Jun 2024, at 10:50, Sabine Maennel ***@***.***> wrote:
@caviri <https://github.com/caviri> Okay I can do that: but even then you would be against mounting the the app folder in the dev setup?
—
Reply to this email directly, view it on GitHub <#130 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AK2SKEPCRMBRIB4PHJOAEN3ZIFA6HAVCNFSM6AAAAABHYGXFZ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZYGEZDKNJWGU>.
You are receiving this because you were mentioned.
|
|
@caviri I have spilt the |
Relase 0.3.0:
Status of bug fixes and comments: