⚙️💻 A macOS app that makes it a breeze to manage multiple GitHub Actions runners in ephemeral virtual machines on a single host machine. The benefits are that runners can run in parallel, and each job runs in an isolated environment.
This PR removes the need for mounting a shared folder in the virtual machine to transfer credentials and the start command from the host machine to the virtual machine. Instead, Tartelet now has the host machine communicate with the virtual machine using SSH. This fixes #64.
As a consequence of this, the pre- and post-scripts are no longer supported as the old approach of transferring the pre- and post-scripts is not compatible with the new approach. If there is demand for Tartelet to support pre- and post-scripts, then we'll figure out a way to support this again.
The PR also brings a lot of modifications to the codebase that I've been meaning to make for a long time. Specifically, the codebase has become much simpler and smaller with fewer packages and targets.
I'm fully aware that it's bad practice to put a ton of unrelated changes in a single PR, and I'm sorry that's where we're at. My priority has been to get these changes out ASAP rather than following best practices.
This PR removes the need for mounting a shared folder in the virtual machine to transfer credentials and the start command from the host machine to the virtual machine. Instead, Tartelet now has the host machine communicate with the virtual machine using SSH. This fixes #64.
As a consequence of this, the pre- and post-scripts are no longer supported as the old approach of transferring the pre- and post-scripts is not compatible with the new approach. If there is demand for Tartelet to support pre- and post-scripts, then we'll figure out a way to support this again.
The PR also brings a lot of modifications to the codebase that I've been meaning to make for a long time. Specifically, the codebase has become much simpler and smaller with fewer packages and targets.
I'm fully aware that it's bad practice to put a ton of unrelated changes in a single PR, and I'm sorry that's where we're at. My priority has been to get these changes out ASAP rather than following best practices.