add equivalents of the local commands, so it is possible to manage the env remotely:
[x] add apps - registers apps in the system, with a switch to assign apps to an org
[x] add org with an option to make it a master org
[x] add users
- [ ] add users with an option to add org users moved to a separate ticket
[x] add test users
[x] destroy user
[x] drop org
[x] register email templates
The point of the above is to be able to set up extra apps in the system without having to log onto the server
Note: the remote commands should be the default commands, but it should be possible to switch to local commands used now.
[x] need to add a switch - use local: true; or something like this.
the env setup would therefore look like this:
set up db
set up api app
run initial env setup on the server (or connected to the db server) - setup dbs (mh meta, identity, id srv), set up master org & user so can perform admin tasks
the local dev setup for a new app would be similar:
set up env as above, but localy
create own stuff - core, cmd
perform apps, orgs, users registration against a remote (or local) web api
add equivalents of the local commands, so it is possible to manage the env remotely:
- [ ] add users with an option to add org usersmoved to a separate ticketThe point of the above is to be able to set up extra apps in the system without having to log onto the server
Note: the remote commands should be the default commands, but it should be possible to switch to local commands used now.
the env setup would therefore look like this:
the local dev setup for a new app would be similar: