You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
A single command, to setup any omniport app (along with all the dependent services) in local for development.
Why this is required?
For example, If someone wants to setup faculty-profile app locally, along with the respective Backend and Frontend repos, he/she also needs to clone two services i.e. common-biodata and faculty-biodata. But sadly, user gets to know about these dependent repos only by errors which occurs when he/she tries to migrate the database after cloning app's backend.
Describe the solution you'd like
Since every omniport app and service have a generic nomenclature, we can make a conf file for each app, which will contain names for all the dependent repos.
We can execute this script in codebase/ which will correspondingly,
Clone app's Backend and Frontend repos in respective directories.
Clone dependent services in respective directories.
We can have a something like python mange.py resolve-dependancy which we can execute in python shell itself.
Since it isn't necessary for cloning Frontend sometimes, we can make this optional and ask user if he/she wants to setup Frontend as well.
Additional context
This script would save time and efforts which goes into running git clone multiple times in different directories before migrating the app :-)
Want to take up?
yes
The text was updated successfully, but these errors were encountered:
Not sure about a manage.py script because that would be backend-specific but I do agree that app configs should have a way to specify dependencies that will automatically be downloaded (if not present already). Something similar to depends_on seen in docker-compose.yml would be nice.
Is your feature request related to a problem? Please describe.
A single command, to setup any omniport app (along with all the dependent services) in local for development.
For example, If someone wants to setup
faculty-profile
app locally, along with the respective Backend and Frontend repos, he/she also needs to clone two services i.e.common-biodata
andfaculty-biodata
. But sadly, user gets to know about these dependent repos only by errors which occurs when he/she tries to migrate the database after cloning app's backend.Describe the solution you'd like
Since every omniport app and service have a generic nomenclature, we can make a conf file for each app, which will contain names for all the dependent repos.
We can execute this script in codebase/ which will correspondingly,
Describe alternatives you've considered
@algomaster99 suggested that,
python mange.py resolve-dependancy
which we can execute in python shell itself.Additional context
This script would save time and efforts which goes into running
git clone
multiple times in different directories before migrating the app :-)Want to take up?
yes
The text was updated successfully, but these errors were encountered: