[Investigation] Figure out how to sunset fly.io
Summary
There were some experiments done with using fly.io, but we don't think we need it anymore. Confirm and produce a plan for sunsetting it.
Things to consider
We need to consider metabase. We probably need to copy our metabase setup from fly.io to cloud66, and then we can copy it over. This is a Daniel thing, and he will need access to metabase.
Criteria for Completion
No response
Need the login for metabase before I can do this 😄
This issue is marked as stale due to no activity within 30 days. If no further activity is detected within 7 days, it will be unassigned.
Due to the economics of moving this to cloud66 versus keeping it on fly for now, we are not going to do this. However, the fact that we are keeping it there does need to be documented. @dorner -- have we done that?
I think in general we have a to-do action to document our infrastructure correctly. We have a page on the wiki which is completely out-of-date and incorrect. Not sure if it should live there or in GitBook.
Ok. I've put a note regarding fly on the general documentation issue and am closing this issue.