1. 214

Hey folks,

If you can read this, you’re on the new server. You’ll have to log in again - we didn’t carry over the secret token for cookies. (Just good practice to rotate security keys during a migration.)

It looks like everything’s good, but if you see anything wrong please leave a comment on this thread.

Thanks to @alynpost for donating the hosting and the ansible configuration.

And, most of all, thanks to @jcs for creating such a wonderful community.

    1. 31

      It’s been a pleasure orchestrating this hand-off with both of you, @pushcx and @jcs.

      If any of your experience performance degradation or see any error messages please feel free to reach out. I expect we’ll do some performance tuning as we subject the server to it’s normal load. For reporting slowness, I would also be helped to see a traceroute from your location.

      1. 13

        Congratulations on a smooth migration!

      2. 4

        Thanks for your work. Did the favicon go missing?

        1. 5

          They did, yes. Some quirk of the deployment is copying the files into a nested subdir. I’ve manually fixed them for now and we’ll keep debugging.

          EDIT: This is fixed now.

        2. 1

          I can access favicon.ico. Does that link work for you?

          EDIT: I was seeing a cached entry.

    2. 15

      I haven’t posted in a while, but just wanted to chime in and congratulate the moderators on a successful migration. As someone sitting on the sidelines, I found the entire process transparent and incredibly well executed. Kudos to everyone involved.

    3. 13

      I, for one, welcome our new overlords.

    4. 9

      Yay! I didn’t notice a thing (apart from being logged out)

    5. 5

      Cheers \o/

      What are the specs of the new server?

      1. 11

        I’ve allocated 2 VCPUs, 4GiB RAM and 48GiB disk to the server. It’s using about half that RAM and 10% of the disk.

    6. 5

      Great work and thanks to @jcs for starting all this!

    7. 5

      Thank you @pushcx, @alynpost and @jcs. Great work.

    8. 5

      +1. The change was unnoticeable :)

    9. 4

      Smooth as butter. Great job!

    10. 3

      Did we lose the HSTS headers in the transition? I think lobste.rs is in the preload list, but as far as I know, the headers should still be supplied.

      1. 2

        Yes, thank you for catching this. I’ve added this to our migration checklist for cleanup.

        1. 1

          I don’t recall if lobsters used to have a Content-Security-Policy set, but might be worth looking into as well.

    11. 3

      Awesome! Thanks to everyone who took on this work. And yes, thank you @jcs for building this community over the years.

    12. 3

      Im glad you made it - works like a charm! I hope you will still be around, @jcs

    13. 2

      The website feels snappier

    14. 2

      Congrats and thank you. Well done!

    15. 2

      Wow, impressive! Thanks for all the hard work that led to this flawless migration!

    16. 2

      Worked until the read-only part which was brief. Great job on the migration! Appreciate everyone who helped make it happen. :)

    17. 2

      Great work!

    18. 2

      What an amazing community this is! Congratulation guys, this transition was seamless.

    19. 2

      Works great. Thanks to everyone involved putting in the effort.

    20. 2

      Smoothly done!

    21. 2

      Love how this community organizes itself!

    22. 2

      that was about as smooth a transition as I have ever been part of - congrats to the whole team!

    23. 2

      Wow, that was smooth. Thanks!

    24. 2

      Congrats guys. Nice and easy transitions are the best!

    25. 1

      Going to “Your Threads” seems slower now, probably database limited but I don’t know.

    26. 1

      That went smooth! Thank you all!

    27. 1


    28. 1

      Great job. Thank you for keeping this alive.

    29. 1

      Wow, this was smooth! Congratulations to everyone involved!

      Just out of my curiosity, the site was running on OpenBSD before?