git repo structure for multiple apps. cloud servers + deployed agent

[trashhalo]

My business requires us to deploy “agent” nodes inside peoples network’s that will communicate with a cloud elixir cluster. Like an exe file, not a piece of hardware.

These agents will share some code with the server cluster but should be isolated from configs and dependencies leaking over and have its own minimal release build.

I could make multiple github repos, but if I was going to structure it as a monorepo is there a recommend structure for this setup?

[paulstatezny]

Hey @trashhalo Welcome to the forum!

It sounds like your requirements are:

• Multiple Elixir apps in a monorepo
• Some shared code
• Exclude unused code from releases (minimal size)

It so happens that we have been working on a library called Uniform to handle scenarios like this.

https://hexdocs.pm/uniform/Uniform.html

Uniform - Less boilerplate, more code reuse in your portfolio of Elixir apps

Announcing Uniform. Uniform tries to minimize the work required to maintain a large portfolio of Elixir apps. It does this via centralization and automation. How it works Uniform works best when you have a portfolio of apps whose core is very similar. (For example, a suite of Phoenix LiveView apps that all use TailwindCSS.) Here’s how it works: You build your entire portfolio of apps in a single, “vanilla” Elixir app. (No “umbrella” or “poncho” setup.) You can generate this “Base Project” …

I’m curious if you think it’s a good fit. I’m here if you have any questions. Or on Elixir Slack @paulstatezny.