The new community.nodebb.org theme!
-
@julian said:
git remote add upstream git@github.com:designcreateplay/NodeBB.git
Then to get the latest changes from NodeBB:
git fetch upstream
... and put them into your local master branch:
git merge upstream/master master
In other words black magic.
-
Haha thanks
I just did that and got this error:
$ git remote add upstream git@github.com:designcreateplay/NodeBB.git
Aarons-MacBook-Air-2:old-forum aaronclaytondunn$ git fetch upstream
Permission denied (publickey).
fatal: Could not read from remote repository.Please make sure you have the correct access rights
and the repository exists. -
Hi again,
I'm pretty sure I'm all upgraded now and I still get the same error. My browser console gives me this error:
Uncaught SyntaxError: Unexpected token <
And the page loads but without any styling. Even reverting the theme in admin > themes doesn't work anymore. Any idea what the issue is? By the way, here are my server logs while it is running:
info: NodeBB Ready
warn: [socket.io] Unrecognized message: event:enter_room
warn: [socket.io] Unrecognized message: reconnected
warn: [socket.io] Unrecognized message: api:updateHeader
warn: [socket.io] Unrecognized message: api:updateHeader
warn: [socket.io] Unrecognized message: event:enter_room
warn: [socket.io] Unrecognized message: api:updateHeader
warn: [socket.io] Unrecognized message: api:notifications.getCount
warn: [socket.io] Unrecognized message: api:unread.count
warn: [socket.io] Unrecognized message: api:updateHeader
warn: [socket.io] Unrecognized message: api:updateHeader
warn: [socket.io] Unrecognized message: api:user.get_online_users
warn: [socket.io] Unrecognized message: api:meta.buildTitle
warn: [socket.io] Unrecognized message: post.stats
warn: [socket.io] Unrecognized message: api:user.active.getPlease get back to me as soon as you get a chance! Thanks!
-
what's the output of
git describe --tags
-
caching is not working for you - something is up with your git repo. My gut says incorrect user permission.
-
but that wont fix it for your users, you need to investigate why ur local git repo is doing that
-
Thanks in advance for the help! Here's the readout--
$ ls -l .git total 688 drwxrwxr-x 2 ubuntu ubuntu 4096 Jan 22 22:48 branches -rw-rw-r-- 1 ubuntu ubuntu 284 Jan 23 19:17 config -rw-rw-r-- 1 ubuntu ubuntu 73 Jan 22 22:48 description -rw-rw-r-- 1 ubuntu ubuntu 104 Jan 23 19:17 FETCH_HEAD -rw-rw-r-- 1 ubuntu ubuntu 23 Jan 22 22:48 HEAD drwxrwxr-x 2 ubuntu ubuntu 4096 Jan 22 22:48 hooks -rw-rw-r-- 1 ubuntu ubuntu 657968 Jan 23 19:17 index drwxrwxr-x 2 ubuntu ubuntu 4096 Jan 22 22:48 info drwxrwxr-x 3 ubuntu ubuntu 4096 Jan 23 18:40 logs drwxrwxr-x 4 ubuntu ubuntu 4096 Jan 22 22:48 objects -rw-rw-r-- 1 ubuntu ubuntu 41 Jan 23 19:17 ORIG_HEAD drwxrwxr-x 5 ubuntu ubuntu 4096 Jan 23 18:30 refs
-
Hey @aaron, it looks like your permissions are set correctly (if you can
git pull
, that should be fine). You're not usingsudo
or anything to run NodeBB, are you?Once the
git describe
command starts to work correctly, you shouldn't have any further problems with client-side script caching... -
@julian it would be awesome if you can publicly share like a pre-setup Ubuntu/Debian/CentOS etc. (or whatever) DigitalOcean images, with nginx setup, correct permissions, redis/mongo dbs, oh the awesomeness, I suck at sysadmin.
oh wait, maybe i just let you host it -
@bentael You mean people don't have computers like my 3GHz Dual Core with 6GB memory running Desktop Ubuntu 12.10?
I'm not sure if Digital Ocean would let their images be made public, although if so, I'd be more than happy to share a working one!
Edit: Seems like people are asking for it already