-
Notifications
You must be signed in to change notification settings - Fork 286
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Docker support wanted? #147
Comments
ok, the more I think about it, I still want to ask the question from the issue. What is the attitude of the upstream to an own integration into a docker container? The advantage of this is the support of a CI pipeline, which might be interesting for later tests. In addition, direct support provides faster onboarding for new developers and users who want to get started with the solution. Chrisns' approach is an excellent one, but I still believe that an all-in-one package promoted by upstream would allow a much easier start within the sources of Scrumonline. Hence the question whether the integration of four files in the default branch is useful and helpful:
Included are currently (and working):
The files are so simple that in my opinion there is no need for extensive upstream maintenance and they can be easily maintained by the project. The goal of this approach is to enable the user to start up the solution with just one command. |
Docker support is obviously important and has great community interest, which is why I added Docker a few years ago. However with limited Docker experience and time the image was barely functional and poorly maintained. Options were limited and the image wasn't available anywhere. So when @chrisns first proposed fixes to the Docker image, I was quite happy, but it still meant I was responsible for overseeing and merging the changes. So we agreed on turning his fork into a dedicated "scrumonline docker" project and removed all upstream files in #123. Reintegrating into into upstream obviously is more comfortable for everyone else, but it kinda takes me back to my previous dilemma of having to maintain it. Since Docker is important, but not essential I prefer keeping the current solution and think you could discuss your ideas with @chrisns. Let me add, that I appreciate your recent contributions and interest in the project and value your input.I just feel your expectations might be a little to high. I started this pretty much 5 years ago, because I was tired of forgetting the damn paper cards and none of the free solutions really had what we wanted: Good master view for the projector and comfortable mobile view with the card deck. So I said to @dbeuchler "Guess we could write something better after work in 2 weeks". I even chose PHP for the sole purpose of learning it. So we built it, posted it on facebook and it somehow took off, with a peak around April with over 100k users per month. Long story short: I never intended for this to become a big project, it's a hobby and I try my best to maintain it, but I am quite happy about everything I don't have to take care of. Hope this answers your question. |
Hi, I would like to ask if there is still interest in an updated Docker Image? I have prepared something that I would like to provide as PR ;) Or is this a feature to be managed and maintained outside the upstream?
The text was updated successfully, but these errors were encountered: