Special purpose entry points beyond client & server?

help
9

Seems with an opinionated stack I can spike out everything without blocking issues then circle back to general concepts / other or how to DRY up even more, and make agent implementations easy to add:

  • minio in common between client and server and agent via slingshot if not directly
  • Gitea container and package registry ( interchangeable, but focusing on independence by default )
  • meteor-base with startup.sh to pull settings.json into process.env.METEOR_SETTINGS
  • Dockerfile.* instances per flavor of server/agent side-by-side and build/deploy scripts
  • Meteor with mongo and hopefully imports/ that can be pulled into Agents not just Clients
  • Client with meteor-vite and vite-bundler packaging Vue.js and Tailwind
  • BullMQ with redis and not just streams of jobs, but beyond-cron job scheduling
  • Server with both BullMQ ( Queue abstracted ) and Meteor ( and WebApp abstracted )
  • Agent(s) with BullMQ ( Worker abstracted ) and just Mongo without Meteor
  • Native applications as variants of Client with the options there ( seeing discussion about changes to Electron and Cordova details, and similar, but have not gone native yet; would hold out a while )

No worthwhile framework for agents, but that is the most proprietary and “designer specific” aspect, and for me having the most to port from prior systems in other languages and modalities into this environment.