@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.
I'll soon be creating a custom theme and some plugins for a forum that is already in use and I'm thinking about running second instance on beta.forum.url with the new theme and plugins enabled when it's close to being ready (but in need of testing), that I'd like to work with the same database as the main forum - so that users can just use beta if they want to preview new features while still using the same forum as others.
Now, I know that the list of themes/plugins enabled is stored in database, so I'd probably need to do something about that, but is there anything else that would stop me from running two instances with a bit different configs off one database? Some sync issue with posts/topics or something like that?
EDIT: actually, since I might as well help others, would it be a good idea to add an option to add some instance identifier to db plugin entries to core? Perhaps in config.json? So that if it's set NodeBB would look for plugins:<instance>:active for example.