From architecture standpoint, bundling these sounds quite messy and complex. If you want open source and web site based - why not choose containers and spin up whatever fits your use-case?
Programming
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
You sound a little confused here. An enterprise application server or EAS is a piece of software that can host applications, but doesn't bring any with it. EAS are complex programs that have to implement and support a multitude of specifications for the apps that are going to run on them. Many of them are already open source, and there should be very little need for new ones.
What you seem to want is some ecosystem of software that may or may not run on an EAS, which satisfies your list of high level requirements.
Yes definitely a beginner with anything networking or web design.
Modular is good though, ideally I would like to bring them all together as one package to share as open-source. I don't know how that would work with permissions for the applications, but I imagine it would be OK with most (foss) licenses.
There are also some things that might need customization. For example, the value of someone's vote is determined by the equity recorded in the accounting books, so those two applications will need to share information.
In any case you have given me some direction and I appreciate it, thanks.