As discussed in “Passing the torch” we’re migrating Lobsters to new hosting. Here’s the current timeline, plans, and opportunities to help.
We’re planning for migration to take place next Sunday, October 15 in the early afternoon. If you’d like your email address or private messages removed before I could possibly see them in the database, please delete them by next Saturday.
Thanks for all the offers of financial support, but we’ve determined they’re not needed now. I’m covering the cost of the Lobsters domain ($77/y) and @alynpost, who runs prgmr.com, is donating a VPS that’s not even at his $20/m plan. Hosting a Rails CRUD side that’s almost all text is pretty undemanding.
The best ways to support Lobsters are:
Code help is last because it’s least important, but it has some details worth talking about. First, thanks to @355e3b for adding Travis CI support so we know the build stays green and @talklittle for a feature checking for dupe urls live on the story submission page. I’ve added filtering based on moderator (all/users/specific mod) and content (user/story/comment) to the moderation log page. Site features will go live with the migration.
I’ve triaged the open issues to filter out things not worth doing and I’ve tagged some
good-first-pr because they require little knowledge of how the site and community work. (Reminder: please don’t post feature requests to the issue tracker. Post a meta discussion to talk about feature ideas.) If you want to help with the development, there’s an introduction here or drop by the chat to discuss.
Anyways. That’s a lot about code but, again, the best way to support the site is to help it continue to grow as a good community for learning and discussing tech. Let’s be excellent to each other.
Finally, the migration itself. Here’s my migration checklist as a gist. I’ll be keeping this updated as things get done, and I’m posting it now to open it to bikeshedding. @alynpost will be setting up an ansible repo in the lobsters github org to handle the provisioning and deployment based on the current config files that jcs has already sent us. The use of Linux and ansible are not up for debate, but if you have suggestions or see things forgotten from this checklist I’d appreciate advice.
Knock on wood, this should be a pretty boringly smooth process with under an hour of downtime.