conceptual question

This commit is contained in:
Moritz 2023-07-28 16:40:04 +02:00
parent 21e983a086
commit fd3a926f34
2 changed files with 4 additions and 3 deletions

View File

@ -154,6 +154,8 @@ Please note any ideas and arguments you have: https://pad.local-it.org/dB0FsiomR
- A go binary that is build on top of the abra library
- An abra command like `abra compose`
- Put `config.yml` into `~/.abra/servers/<server>/` or let the user decide?
- Should we move completely away from .env files?
- This would skip the translation step into env files
- It reduces the complexity!
@ -165,4 +167,3 @@ Please note any ideas and arguments you have: https://pad.local-it.org/dB0FsiomR
- better configuration versioning for different recipe versions
- harder to maintain the recipes: requires knowledge about the connectable apps
- Global config?

View File

@ -269,7 +269,7 @@ def deploy_apps(apps):
for app in INSTANCE["apps"]:
domain = map_subdomain(app)
if (apps and app in apps) or domain not in deployed_domains:
logging.info(f'deploy {domain}')
print(f'deploy {domain}')
print(abra("app", "deploy", "-C", "-n", domain))
logging.info(f'execute commands for {domain}')
execute_cmds(app)
@ -284,7 +284,7 @@ def undeploy_apps(apps):
apps = INSTANCE["apps"]
for app in apps:
domain = map_subdomain(app)
logging.info(f'undeploy {domain}')
print(f'undeploy {domain}')
if domain in deployed_domains:
print(abra("app", "undeploy", "-n", domain))