Open rishitc opened 3 years ago
A Dockerfile will be an overkill and not something I would be willing to maintain. Aspell is fairly portable and has very little dependencies.
I've used Docker before and it's fairly easy to maintain. Also as you mentioned in the case of Aspell, due to its fewer dependencies, I think it would actually be quite easy to maintain over time. If possible I would like to participate in maintaining it because I strongly feel that it can make the setup process easier, for contributors, especially if any dependency changes occur. There would be no need to install/uninstall/update any packages, just pull and run the latest Docker image, and you can continue working.
Aspell is fairly portable and has very little dependencies.
I agree, but using a container during the time of development, helps keep things sandboxed and easier to set up and get started. It also helps to reduce the impact, in case any changes made to the code, don't work correctly.
Finally, it makes it easier to try different base environments on the same development system (this is quite similar to what CircleCI does, but this can now be done locally on the contributors' system(s) itself)
I am also not a huge fan of Docker, but if you are willing to maintain a Dockerfile I will consider adding it.
Hi, While browsing the repository, I noticed that there is no Dockerfile, to create a build environment for the project. I feel that using Docker would make it easier to set up the development environment for building and testing any changes made to the code locally.
Do you think it would make sense, to try working on writing a Dockerfile for the project? so that people can use it to easily setup the development environment on their local systems? If you think that adding a Dockerfile to the project makes sense, I would like to work that.
Any inputs on this would be really helpful!
Thanks