Recently I have created a rail app for local business that they like this app so much that they Some other local businesses interested in the version of their own have found.
Here's the problem that I'm unsure about how to fix the main business logic behind the app for these new and future customers (about 80% of the code). While each customer can get their own stylesheets along with their own static pages.
Ive thought of multi-tenancy, but these people are ripe enough to honestly find it easier to create an app function as they have DB stored customer preferences (maybe I'm wrong here) Contrary to the creation, want.
I would like to configure this application so that I can make changes to the main business logic without overwriting a specific part of the client, maybe the site has only client specific content in making a second repo.
How can I configure this App / GIT repo so that I can not create a group of parallel repos?
road.
No comments:
Post a Comment