:fa_bullhorn: The sound of AN ANNOUNCEMENT BEING MADE (or: Request for Comments: Comments)
-
-
It's very fitting that the start of the announcement is in EST and the rest uses UTC.
-
It's adjusted for a leap year. Duh.
-
It's very fitting that the start of the announcement is in EST and the rest uses UTC.
Correcting the times I was given would have exceeded my work quota.
-
By the way, after we're sure everything works, one of the admins will need to revoke my admin privileges. I can't do it to myself. I already added myself to registered-users, so there shouldn't be anything horribly broken about my account.
-
@dkf said:
Yes, we lost some people but we gained others,
I'd throw them all in the fire to get Dhromed back.
I'd throw certain of them in the fire even if it didn't get anybody back.
-
Will we need to reset our password on the main forums after the switcheroo too?
The email I used to register this account might not be the most permanent. (Still more secure than my password!)
Would changing my email now apply to the final import?
-
You'll need to reset your password, but I'm pretty sure changing your email address won't do anything. You'll have to contact an admin after the migration.
-
By the way, the IP of the new server 52.91.192.100. I'm telling you this early for a reason.
-
-
The surprise happens in just over nine and a half days.
/cc @aliceif
-
The surprise happens in just over nine and a half days.
You make it sound like the surprise is going to be one of those not fun ones, like that we've just moved to a new instance of Discourse.
-
You realize you've now committed yourself to MILLISECOND precision.
-
-
Sure, I'll promise MILLISECOND precision. Not millisecond accuracy, though.
-
Discourse is bisexual?
o_O
-
Alternative version: https://jsfiddle.net/2measbdz/3/show/
-
So apparently no fixed number of Blakeyrats have been transported by a goat.
But the real question is since when has there been more than one Blakeyrat?
-
What you observe as blakeyrat is actually an infinite number of blakeyrats being teleported by goats.
Source: https://bugs.chromium.org/p/chromium/issues/detail?id=31482
-
And how many goats are there doing this transportation? Three, maybe five tops?
-
Thanks, this time it's actually something understandable
-
Is there any way to figure out or configure the keyboard shortcuts on NodeBB? I've looked for some form of documentation, but have not found any and I'll be Belgiumed if I can figure them out.
-
Is there any way to figure out or configure the keyboard shortcuts on NodeBB?
It's the same arcane method used in gmail and Discourse:
-
Just press ? outside of a input-box?
Filed Under: No, really...
-
I love how on a topic page the banner appears as the page is loading, just to taunt us, and then disappears before we can finish reading.
At least it doesn't go away in topic lists.
Edit: I'm talking about Discourse here, to be clear.
-
@ben_lubar, forgive me if this has been asked and answered already, but will the "has been read"-ness of posts be ported as well?
Having to track down where I left off in every thread again will be super-annoying. I'm getting a glimpse of that already on https://discourse.local.lubar.me/
-
Ta. No way to change them, though? They usurp some of the key bindings in Conkeror...
-
Could you change "Discourse project" on that page to
-
will the "has been read"-ness of posts be ported as well?
Unfortunately, the only way to mark posts read in the base importer is to give it an array of all the topics the user has read. No way to say which posts, and with 10k+ topics, that's a bit much.
Having to track down where I left off in every thread again will be super-annoying.
For the threads you actually care about, just set a bookmark.
-
Ugh. How does NodeBB handle read/unread posts? Can we at least have the last read post in the Discourse thread delineate between read/unread posts after the transition?
-
This post is deleted!
-
-
@ben_lubar said:
52.91.192.100
Filed under: Did I spoil the surprise?
Now do one that reads:
DISCOURSE PROJECT COMPLETES IN
A years, 11 months, 12 hours, -1 mins, 61 seconds, NaN MS, 502 OK
-
@PJH future updates to NodeBB are as simple as
./update_nodebb.bash
. Here's the script if anyone is curious.The only thing you need to do special is that if you install any plugins, you need to add them to the
npm install
line. Also, if you do change thetag=latest
line, you'll have to manuallydocker rmi
the old image.#!/bin/bash set -e COOKIE_ENCRYPTION_SECRET=[redacted] # TODO: change this to the latest version after v1.0.0 tag=latest docker pull benlubar/nodebb:$tag docker stop wtdwtf-socat wtdwtf-nodebb docker rm -v wtdwtf-socat wtdwtf-nodebb docker run -d --name wtdwtf-nodebb --link wtdwtf-mongo:mongo -v /usr/share/nginx/wtdwtf-nodebb.uploads:/usr/src/app/public/uploads benlubar/nodebb:$tag npm start docker exec -ti wtdwtf-nodebb npm install 'git://github.com/BenLubar/nodebb-plugin-import-discourse.git#tdwtf' 'git://github.com/barisusakli/nodebb-plugin-emailer-amazon.git#patch-1' nodebb-plugin-{htmlcleaner,ns-login,google-analytics,gravatar,category-notifications,sso-{facebook,github,google,twitter},write-api,question-and-answer,shortcuts,emoji-{one,static}} # the admin information is only used if the database doesn't already exist docker exec -ti wtdwtf-nodebb node app --setup='{"url":"https://what.thedailywtf.com","secret":"'$COOKIE_ENCRYPTION_SECRET'","database":"mongo","mongo:host":"mongo","mongo:port":27017,"mongo:username":"","mongo:password":"","mongo:database":0,"admin:username":"admin","admin:password":"changeme","admin:password:confirm":"changeme","admin:email":"admin@example.com"}' docker exec -ti wtdwtf-nodebb ./nodebb upgrade docker restart wtdwtf-nodebb docker run -d --name wtdwtf-socat --link wtdwtf-nodebb:nodebb -v /usr/share/nginx/wtdwtf-nodebb.sock:/sock --user www-data:www-data -m 25M verb/socat -d -d UNIX-LISTEN:/sock/sock,fork,reuseaddr,umask=0 TCP4:nodebb:4567 docker images -q -f dangling=true | xargs docker rmi || true
-
I'm curious: how long would the downtime be for an upgrade?
-
-
-
It doesn't actually get created because there are already users, but the setup script errors when it's not given.
-
Ok - can't find it. Where is "ignore thread"? As in I don't want threads popping up in this read counter because they have new posts?
-
There's a per-category ignore button.
-
-
There's a per-category ignore button.
... which ignores... all new topics as well?
Not what I'm after.
-
I guess we could make a category for
-
Yup - click that makes them appear as notifications. The other option being Unwatch. And unwatched topics come up in Unread anyway. I want them to stop.
On a per-topic basis.
After I've decided I don't want to know about them (unless flagged of course.) I do want to know about new topics.
-
-
hey @ben_lubar i have a question
on the users migration. i log in with my google account, is that supported? should i get an email addres attached to my account?https://discourse.local.lubar.me/login if i go there i can't login, but i guess that's because the migration it's not done yet.
thanks!
-
I think you have to use password reset for now - the account associations won't work until NodeBB is running on this domain.
-
hey @ben_lubar i have a question
on the users migration. i log in with my google account, is that supported? should i get an email addres attached to my account?https://discourse.local.lubar.me/login if i go there i can't login, but i guess that's because the migration it's not done yet.
thanks!
You have to reset your password and then you can associate the Google account with your NodeBB account. NodeBB doesn't assume things about who owns which account, which means @riking wouldn't have been able to log in as @system.
-
Great!
i wanted to know if i had to do something prior to the migration.
-
Just so you know, there was a bug.
It got fixed before I remembered to write this post. Sorry.