Looks really good Cory! I deployed to AWS and all the status changes looked legit (i like the inclusion of '/etc/hosts registration' in addition to the normal boring enhanced status).
What if we want to shove things in ./resources that aren't pip'able? We can either cross that bridge when we get to it, or shove pip stuffs in ./resources/pip. Thoughts?
Looks really good Cory! I deployed to AWS and all the status changes looked legit (i like the inclusion of '/etc/hosts registration' in addition to the normal boring enhanced status).
I have a beef, though. This feels heavy:
+ archives = glob('resources/*') check_call( ['pip', 'install'] + archives)
+ subprocess.
What if we want to shove things in ./resources that aren't pip'able? We can either cross that bridge when we get to it, or shove pip stuffs in ./resources/pip. Thoughts?