|Erik Moeller dce2c62868 Merge branch 'master' of git+ssh://github.com/eloquence/lib.reviews||1 hour ago|
|assets||8 months ago|
|bin||4 months ago|
|config||2 weeks ago|
|frontend||4 days ago|
|locales||20 hours ago|
|maintenance||2 weeks ago|
|manifests||5 months ago|
|models||2 weeks ago|
|routes||1 week ago|
|static||1 hour ago|
|tests||1 month ago|
|tools||2 months ago|
|util||3 weeks ago|
|views||2 hours ago|
|.eslintrc.json||4 months ago|
|.gitignore||5 months ago|
|.jshintrc||7 months ago|
|CODE_OF_CONDUCT.md||7 months ago|
|Gruntfile.js||2 weeks ago|
|LICENSE||9 months ago|
|README.md||2 weeks ago|
|Vagrantfile||5 months ago|
|app.js||1 month ago|
|auth.js||5 months ago|
|db.js||6 months ago|
|package.json||3 weeks ago|
|process.json||6 months ago|
|search.js||2 weeks ago|
A free/libre code and information platform for reviews of absolutely anything.
The site is at: https://lib.reviews/
At this point, you need an invite code to make an account. Follow lib_reviews on Twitter and send a public ping, and we'll respond with the private invite code. To keep up with development, add our development diary to your favorite feed reader.
Our technical choices include:
We also try to add keyboard shortcuts where relevant, and generally follow existing conventions for those (from Wikipedia, Google and other sites).
We aim to be multilingual in UI and content, and are exclusively using translatable strings throughout the user interface.
This is very much an open project and we'd love your help! :) To get started,
clone the repository to your local computer. You will need the current Node.js
stable release. Switch to your check-out directory and then run
and running before starting the service.
You can customize your development configuration by copying
config/development.json5. Finally, run
npm start and visit
at the configured port number. Note we require access to two ports -- one for
HTTP, one for HTTPS.
The startup scripts use pm2, which you can
safely install globally alongside the local version. It's a handy tool that
keeps the process running in the background, balances it across multiple cores
if available, lets you manage log files, etc. If for any reason you just want
to run the server without pm2, you can always fire up
node bin/www instead.
If you're familiar with Vagrant and VirtualBox, you may find it easier to configure a working environment using our Vagrantfile. To install using Vagrant, simply type
in the main directory, and follow the instructions printed on screen. All dependencies will be installed automatically within a virtualized Debian environment.