I would be happy to see the stupid glossy iOS emojis replaced with Emoji One's, to be honest.
I also feel that the iOS ones don't express things correctly, for example the :D
emoji looks like what I expect a xD
emoji to look like:
I would be happy to see the stupid glossy iOS emojis replaced with Emoji One's, to be honest.
I also feel that the iOS ones don't express things correctly, for example the :D
emoji looks like what I expect a xD
emoji to look like:
@a_5mith Even if you need to update NodeBB?
Wonder if CoreOS can be used to run a dual-NodeBB setup, with one instance being a dev environment and the other being the production environment, and then switch between them as needed with updates and stuff.
@baris I can't quite tell, but that commit looks like you guys added that feature. Awesome!
Would be cool, but I think this would be better off as a plugin due to the limitation factor.
@baris Fresh list of non-NodeBB sites:
http://starheartcoin.com (down)
http://community.onehundredfreebooks.com (down)
http://rabbitsraiders.net (different software)
http://discuss.stylespotter.com (redirects to blog)
http://www.gippy.com.ar (down)
https://melonmancy.net (down) aw man
http://warhub.tommytony.com (down)
http://forum.boundstar.com (down) shame, liked this site
http://gagbits.com (down)
http://earnabit.com (down)
Super excited about these changes. NodeBB restarts get a bit old when you're trying to set up your forum and you're playing with all the plugins.
Really awesome plugin. I'm excited to see the gif format being replaced by webm slowly but surely.
@bentael Well, will you add a flag that will not flush the data? I think the importer could be useful as a merge tool that way.
@julian I'm the same way, it can sometimes take me weeks to finish a design. Even when it's finally finished, it's still not finished to me.
So there isn't a way to make nginx monitor listen for requests on 1.2.3.4:4567 and 1.2.3.4:80 and block those requests or redirect them to my domain?
Not seeing a bug btw.
So I've got my forum running, and nginx set up as a proxy. Now I want to deny access to ports 80 and 4567 on my server through its IP address, so people can only visit my forum through example.com, instead of through 123.456.789.101:80 and 123.456.789.101:4567 as well.
Is there an nginx config I could use that will do that?
@baris Maybe a couple more pixels of padding and then a border on the bottom:
The very bottom doesn't look too good like that though.
@baris Seems to delete all content and then sets up an admin account with the username "admin" and the password "password", before it imports the data.
@a_5mith Yeah doesn't really bother me either, because I've also deleted a lot of the categories I've imported. It would be cool if I could change the IDs for the existing ones, but I've already started linking to them, so probably not a good idea.
This looks a lot better than "User made a new post, User made a new post, User made a new post..."
Might have been because I didn't use the --flush flag when I ran the importer command for this instance.