I’m planning to upgrade to 0.18 today and move the storage to S3, so I’ll bring the instance down between 5-6pm PDT.
Update: this took longer than I expected. I started at 6pm because of work. I shut down the instance and took a snapshot, then brought it back up and upgraded to 0.18. The upgrade worked fine. I brought the services down and configured the instance to use S3 for object storage. That required migrating existing objects to an S3 bucket, which took quite some time. Then, after bringing the services back up again I got a “Server error” message. Unfortunately I had to stop at 8pm since I had something scheduled. At 9:15pm I was able to bring the services up successfully, and we’re back!
Update 2: turns out we hit this bug, and the instance was down around 11pm. I changed the hostname of the instance and now it seems to be working fine.
Do what you gotta do, my dude. We’ll be here when you come back. Err…we’ll come back when you’re back? You know what I mean. :)
Thank you, it’ll be nice to try Jerboa again.
Thanks Beto for maintaining this place. It’s great to see a music oriented open source community begin to thrive.
I was just wondering when you would update to 0.18! It turns out the client Jerboa requires version 0.18, so I was just about to post asking when you were planning to update as it seems to be a pretty nice client. I should also be able to finally set up 2FA, which I have been wanting to do for a while.
I saw! It was annoying, sorry for that. I wanted to upgrade earlier, but I moved this weekend so my last week was crazy.
