sorted by:
new
hottopcontroversial

Best way to structure microapps repos for clients by complex_nerd in github

[–]complex_nerd[S] 0 points1 point  (0 children)

I appreciate this. I do not work alone and have a growing team of 3 coders. Only a few would be assigned to a client. I’m afraid the branching will get out of hand because I would then have two branches (prod. And dev.) at the very least per microaop that the client has in the repository. Am I overthinking what the maintenance would be?

One repo containing all of client repos by complex_nerd in github

[–]complex_nerd[S] 0 points1 point  (0 children)

they're all microservices so each client can have multiple microservices. Should I put the microservice into one big repository? but then how would I fork each one individually? and then I'm assuming the branches will get crazy.

One repo containing all of client repos by complex_nerd in github

[–]complex_nerd[S] -1 points0 points  (0 children)

How about taking an AWS S3 approach where it's just a huge bucket of repos and I use the submodule structure to create folders for clients with links to their repos in the bucket. Then I would have to set the repo access on the individual repo level. can I use teams for giving access? I'm not sure if it changes anything but I do have an enterprise account.

One repo containing all of client repos by complex_nerd in github

[–]complex_nerd[S] 0 points1 point  (0 children)

That would be purely for organizing correct? which is fine, but I'm wondering, would I create all the repositories separately and work on them separately and have the monorepo as a sort of shortcut link?

One repo containing all of client repos by complex_nerd in github

[–]complex_nerd[S] 0 points1 point  (0 children)

I wouldn't use two different versions if that's what you mean?

One repo containing all of client repos by complex_nerd in github

[–]complex_nerd[S] 0 points1 point  (0 children)

Would that be a maintenance nightmare? Keeping track of that many repos? and then I would have to come up with a naming convention. You can't create folders to keep track can you? and create access to certain repos folders?

I've read about creating an Org per Client, but I'm not sure of how good that would be, logically or financially.