I think its stable. I use it in production.
Same here. Done a lot of customization and no problems so far, using version 1.1.2 for now.
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
fatal: No names found, cannot describe anything.
... and I'm assuming you're logged in as
Yeah, logged in as ubuntu.
Haha yeah I just deleted the cache again and it started working. Is this problem going to resurface? Does it look like I have permissions set incorrectly?
Hey @aaron, it looks like your permissions are set correctly (if you can
git pull, that should be fine). You're not using
sudo or anything to run NodeBB, are you?
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
Everything else got better when I deleted the cache. But forking doesn't seem to work for me. Here's a screenshot of what happens when I try to fork. It doesn't let me select anything to fork.
Did you click on posts that you want to fork out? The button should became available when you do.