Does anyone know the steps I'd need to go through in order to set-up a development copy of NodeBB? I've forked Persona and aim to submit some pull requests.
The problem is using my forked version of Persona (v2.0.21) inside /nodebb/node_modules/ doesn't seem to work with a 0.7.3 NodeBB install. The logs tell me an older version of Persona (v2.0.13) is required.
So far, I have NodeBB set up and running on Nginx at http://127.0.0.1:4567
Path to my NodeBB: /home/ubuntu/nodebb
Path to my forked .git enabled version of Persona: /home/ubuntu/nodebb-plugin-persona
I'm at a loss so any tips will be much appreciated!
If you want to fork Persona for your own changes, you'll need to rename the theme itself so NodeBB thinks it is a different theme.
Take care to change the values in package.json, plugin.json, and theme.json, and change references to nodebb-theme-persona to nodebb-theme-henrywright or whatever you'd like it to be named.
@julian problem is I was planning to contribute back up to the remote Persona repo. I recently made a pull request but I'd like to test my commits going forward. How do you guys do it? Do you have Persona as a .git repo inside your NodeBB .git repo? I've never nested repos like that before.
Also, I'm assuming I need the master branch of NodeBB?
In that case, you'll want to run NodeBB via ./nodebb dev, as that will bypass dependency checks 
@julian so I should run ./nodebb dev instead of ./nodebb start?
Also, I'm wondering if you can have a .git repo (Persona) inside another .git repo (NodeBB)?
Yes, and yes.
@julian great stuff. I'll give it a shot! And thanks for the info (...again) 
Or use grunt which makes theme development a bit speedier. Whenever you save a file it auto-reloads for you and bypasses compilation of things you didn't change (as opposed to compiling everything, which takes additional time on restarting)
@psychobunny Thanks, I'm going to look into Grunt!
