General Discussion

@arasbm said: But perhaps I should add a not in the sign up agreement that "by signing up you agree to receive emails from us" or something like that, to be safe. If you're in the EU, this wouldn't constitute as opt-in. The EU states that a user must specifically click a button that states "I want to receive these emails". Unless it's regarding their account. So, if the daily digest included notifications, it would be fine, but if it was just new topics, I'm not so sure. It should be fine either way, as you've said.

@a_5mith - thanks! yes the front page logo is in the works and should be updated shortly. @julian - thanks! yes the official way should always be a native install, using LXC or Docker makes it simpler and faster to launch, and provides added flexibility in deployment, but there should be some understanding of how the components work together which a native install, which can be also be done in an LXC container like we do, gives users. We are definitely going to look at how we can integrate github into our current build process. LXC has been baking since 2009, was merged into the kernel around 2.6.32 and has been mainly developed by a team led by Daniel Lezcano, Serge Halyn and Stephane Graber. Its an Ubuntu supported project since 2012. Serge and Stephane work for Ubuntu. LXC provides container management tools and container OS templates. Here is a video walk through of LXC Docker was based on the LXC project untill 0.9 when it switched to its own engine libcontainer, though users can still choose LXC as the underlying container engine. Docker containers and LXC containers are a bit different. Docker uses containers to build an app delivery platform and abstracts the container away to an app, while LXC gives you a full Linux environment like a lightweight VM, with some caveats. However due to the low profile of the LXC project, a lot of users first introduction to containers may have been Docker, and there are some misconceptions and a lot of users will be surprised by the flexibility and usability of LXC without the constraints of Docker.

@baris said: You can still use bcrpytjs on raspbian but you would need to lower the bcrpyt_rounds setting from the default 12. Yeah, either lower the rounds, or if you don't mind compiling it (npm does it automatically), use bcrypt instead.

@Baerrus It shouldn't, because following a topic will notify you of a new post in that topic, but that topic won't appear in Unread. They're two different features. Unless there's a specific check in NodeBB that I'm not aware of. Wouldn't be too difficult for me to test if you need a definitive answer.

@julian you'd hope that would be the end of rubbish like tapatalk, but people still want it.

@SANTO007 Have you tried searching for that error message online? This may help you: http://superuser.com/questions/709515/command-not-found-when-using-sudo

I attempted this last week. It's easier to redirect them. So category.forum.com redirects to forum.com/category/2 I pasted my configuration in another topic. Feel free to look through my topics from the last 2 weeks for one about subdomains

OK PROBLEM SOLVED

@SANTOSH-KUMAR Your redis is out of date. Needs to be greater than v2.4

Hi @Netto-Hikari, thanks for your feedback about our upgrade process We definitely try to make the upgrade process fluid and straightforward, but if files have been changed, then yes, there will be problems as git will not know how to handle changed files. Re: When it comes to upgrades, I just simply follow the docs and it always says that I have to commit the changes before. Did you mean Step 3? As far as I know, the only thing we ask admins to do before upgrading is back up their data. If you have never changed any of the core files, git should never complain. If this ever happens, and you are absolutely sure you didn't change anything, then you are advised to run the following: $ git fetch # to grab the latest code (but not apply it) $ git reset --hard origin/v0.5.x # force your local files to match the NodeBB repository *EXACTLY* $ ./nodebb upgrade # then proceed with upgrade as usual ^ Hooray, more unsolicited advice from strangers on the internet After running those commands, future attempts to git pull should not have git complain.

@psychobunny said: I'm falling in love with some of Google's Material Design. Not everything is great in my books but I wanted to see a bit more of it in action. Downloading inbox now, thanks @luke The material design (effects) is more so in the mobile application than in the desktop interface. I was pretty disappointed as it feels smooth but still didn't really see anything that was mind blowing in the desktop. I do like the colors and the padding/margins are on point, however, its nothing new for the most part. But like I said, the mobile app is a slightly different story.

[image: XOxEOM6.gif] :shipit:

Was in the queue Thuesday for it and the man before me took the last place. So going to see it this WE.

Sumblime Text 3 best I could find. The plugins makes it so worth it. Working with the base-16 eighties color scheme with space grey theme.

Hey there -- happening here? Looks to be zippy for me right now

Ah okay, looks good

@psychobunny apparently since version 31, and since we're now at 35 (at least the Aurora channel is), my rough guess was actually quite accurate

haha wow, and thanks for the rec, that'd be cool if they started using NodeBB

@Shaun Thanks but unfortunately the RSS feed plugin seems to be having some issues (at least for me), particularly with not grabbing all posts and/or duplicating them. I'll keep my eye on the rss thread and see if it gets any updates.

@a_5mith True, but honestly, it's easier to set up a quick Linux VM (and I say this as someone who is not at all a fan of Linux) and the support is far better.