-
Notifications
You must be signed in to change notification settings - Fork 323
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
pbem as a standalone module #417
Comments
Python is an excellent programming language, and is used in other parts of Freeciv-web, such as freeciv-proxy, publite2 and in the scripts directory. |
Thank you for your answer Andreas. The point I'm trying to push here is that the entire freeciv is a monolith so you always build just one docker image instead of several for modules you would or would not want. This would allow easier development of the other modules and give the administrators the ability to not use certain modules they don't want to support on their servers. Would that be ok? I could prepare a change and, say, separate just pbem to see how that aligns with the freeciv-web devs and work on separating other modules if that's right or abandon the idea altogether. Would love to get your feedback as you probably have the most to say regarding the python modules |
Hello, this is more of an architecture thing but I don't understand why is pbem, which is written in different language than the rest of freeciv-web isn't a standalone module. It would make more sense as if you wouldn't want to use pbem you could just not build it and make the footprint of your server smaller. Instead, the entire freeciv-web is a monolithic docker image containing everything, forcing you to rebuild the entire monolith in case you want a tiny bit of it changed.
Is it a subject to change? Does it have to be like this? Thank you
The text was updated successfully, but these errors were encountered: