rendercad
computer-aided design for "infrastructure as code" files to be used on Render.
THIS IS EXPERIMENTAL SOFTWARE AND SHOULD NOT BE USED FOR CRITICAL INFRASTRUCTURE
- refactor to a more OOP design
- each machine type has a:
- type {'service', 'database', 'envvargroup'}
- template_file
- modifiable_fields
- ???
- each machine type has a:
- have user select services, then databases, then envVarGroups (implies being able to separate machines by type)
- have user be able to interactively supply non-default values
Proposed flow:
- If a render.yaml exists, throw up a prompt to either exit or continue by overwriting existing file
- Prompt user to select services to include
- for each selected service, present a sane default config and ask user if they'd like to modify it
- show user list of modifiable fields and allow them to select a field to modify
- repeat until user gives some kind of "done" input
- Prompt user to select databases to include
- for each selected database, present a sane default config and ask user if they'd like to modify it
- show user list of modifiable fields and allow them to select a field to modify
- repeat until user gives some kind of "done" input
- Prompt user to select envVarGroups to include
- for each selected envVarGroup, present a sane default config and ask user if they'd like to modify it
- show user list of modifiable fields and allow them to select a field to modify
- repeat until user gives some kind of "done" input
git clone [email protected]:zachwick/rendercad
poetry install
poetry run rendercad
Better usage docs forthcoming.
Copyright 2022 zach wick [email protected]
Licensed under the GNU AGPLv3 or later