tilburgsciencehub
Future dev: Using docker - advanced
Contact Details
No response
Shoot!
I need
Docker for reproducible, long-term maintenance
- docker for replication packages that allow me to (1) update my codebase if bugs are reported or extra statistics are being requested, and (2) ideally allow me to have a proper "interface" in which to play around with code, rather than writing one perfect code file and then process the entire image
Docker for development and production
- i have multiple pipeline stages (e.g., scrape, dataprep, analysis, post-analysis, paper)
- I want to be able to "develop" certain stages - e.g., open R(Studio)?, fiddle around, make commits, save it.
- I want to be able to "ship" the production of these pipeline stages to remote computers
[to be continued]
Code of Conduct
- [X] I agree to follow this project's Code of Conduct
I just had a session today at JADS where I got to pick some brains about what they want out of Docker, and how we could sell it best to people (h/t @alexandervossen). I'll take that alongside your points, get in a meeting @Fernando-Iscar and @krzysztof99xd , and then we can get started! FYI I have a huge deadline today, so I can meet Friday earliest, how does Friday 11am sound?
Sure, Friday at 11:00 works for me. Just for the heads up, in the past few days, a lot of ideas about what to work on arose and I am still in the process of figuring out what to pick and how to prioritize them. However, this issue sounds interesting. Lets have a meeting on Friday.
@gbocsardi when you have time could you maybe share here a use case for such an article (you mentioned during the meeting that you could provide me and @Fernando-Iscar with one) that we discussed during the meeting on the 8th of March? In this way, it will be easier to visualize what steps are needed to break down this article into smaller pieces. Thanks in advance!