I suppose. Given that it checks the AWS/GCP api on a schedule not sure how effective that would be.
Then again, it's not like the hosting is costing that much. Actually I currently run it on a machine with lost of resources that is used for other things as well...so technically I could keep running it forever. That is to say the cost isn't the main driver for shutting it down. It's more a psychological burden at this point where I'm thinking "ok I tried, it didn't work time to move on".
Then again, it's not like the hosting is costing that much. Actually I currently run it on a machine with lost of resources that is used for other things as well...so technically I could keep running it forever. That is to say the cost isn't the main driver for shutting it down. It's more a psychological burden at this point where I'm thinking "ok I tried, it didn't work time to move on".