Refactoring Idea: Installation history #10
Description
Problem
Currently, all the outcomes of an installation as stored into individual, statically-named files at the current folder. This is great for finding and customizing the file contents when needed, but it makes it harder to update and might be confusing if the number of files increases.
Proposal
Instead of generating configuration and credential files, store all the relevant installation data into a single history file/folder, so that the actions that runs next can rely on that information.
- Remember which port is being used by the "expose" action and consider it when running the demos
- Add actions to show the credentials instead
- Potentially build a dashboard action that lists everything that the user has installed