search

NCC-CNC / whattodo

Interactive management action prioritization application
https://NCC-CNC.github.io/whattodo
2 stars 2 forks source link

Implementing major updates #5

Closed jeffreyhanson closed 2 years ago

jeffreyhanson commented 2 years ago

@ricschuster, my impression is that the redesign/updates for the what to do applications will involve changing a lot of things. May I ask if we need to keep the demo applications online and functioning correctly during this process? E.g., do you have any further demos planned? The reason I'm asking this is because the what to do applications/codebase (i.e. the template maker app, optimization app, and shared R library) share similar dependencies and assume similar input/output formats. So, if we want to ensure that the applications are still running correctly on the server, I'll need to make sure that I don't break anything and plan for a release strategy wherein apps/depedencies are updated at around the same time. But if that's not the case, then I can afford to be a bit more careless (which means I can add the updates at a faster pace).

ricschuster commented 2 years ago

Hi @jeffreyhanson, could we keep the docker containers available as is for now (maybe move to a new repo that we will eventually mothball). Generally speaking I don't want you to be restricted by the current demo applications. Break things as you like. Does that make sense?

jeffreyhanson commented 2 years ago

Sorry, I'm not sure I understand. In order to keep the docker containers as is for now, I can't exactly break things as I like. One option could be that we could set up a "fixed" release for the what to do applications, and then pin the shiny proxy launcher to only use docker containers associated with this fixed release?

ricschuster commented 2 years ago

Hmmm, how about cloning the repo and calling the old one whattodo_archive or something like that? Would that be weird? I have no idea how these things work. I would just copy things, but I bet that's not how proper developers do things.

jeffreyhanson commented 2 years ago

Yeah, we could do that - but it would mess up the Docker images. So, if we want to ensure that the Docker containers and web apps continuoue to work, then that won't work.

jeffreyhanson commented 2 years ago

I'll see if I can implement the fixed release idea.

ricschuster commented 2 years ago

Sounds good to me. Hope that allows you the flexibility you were hoping for.

jeffreyhanson commented 2 years ago

Sorry, I forgot to respond. Thanks for clarifying that - I'll close this issue now.