Cool but simple web-app mobile-compatible to gamify your life and self-improvement
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Go to file
Arthur POULET 35b69ef33a
continuous-integration/drone/push Build is passing Details
Loosen on dependencies version
11 months ago
config Improve registering new users with default value and redirection to today 2 years ago
documentation doc: add a french user guide 2 years ago
init env: fix scripts env loading 2 years ago
public layout: add the full date (today/yesterday) 1 year ago
scripts other: minor script & ci update 2 years ago
src Merge remote-tracking branch 'origin/master' 1 year ago
test recap: add input to control how much data to fetch 2 years ago
.drone.yml drone: update ruby image 1 year ago
.env.sample userpex: improve error and fix test databases 2 years ago
.gitignore boot: add dotenv to load env variables 2 years ago
Gemfile Loosen on dependencies version 11 months ago
Gemfile.lock Loosen on dependencies version 11 months ago prefs: add offset as a user pref 1 year ago
Rakefile script: improve db migration 2 years ago user_pex: add user pex json api with tests 2 years ago


Build Status

Install the software on a server

Install the dependencies

You should have the following systems installed: git ruby 3 AND gems sqlite OR postgresql Git is required to clone the project and fetch the tags in order to expose them in the webapp.

Then make sure you have installed bundler gem install bundler if not already done.

Then install the ruby dependencies.

bundle install

Configuration setup

A sample file contains all the variables you will need in order to start the server. This is the .env.sample file. You should copy it under the name .env.local.

  • LIFEPEX_DB: is an url to your database. It may include a user/password
  • LIFEPEX_BIND: what your socket will listen to (should probably be or
  • LIFEPEX_BASE_URL: base url for the whole app (for local usage you can leave if empty)
  • LIFEPEX_SECRET: you must put randomness in this variable to secure tokens and cookies
  • LIFEPEX_ENV: may be empty, test, or production to avoid showing the stacktrace when there is a bug

Database setup

The recommanded way is simply to init the database you configured with


If you have postgresql, you may want to create a specific user/password for this. Since I suck with SGDB administration, this is a sample of what you may do.

TODO: show how to create a simple attribute with full permission on this database

psql -U postgres postgres -c "CREATE USER root WITH PASSWORD 'toor' SUPERUSER;"
psql -U postgres postgres -c "CREATE DATABASE life_pex"
echo LIFEPEX_DB=postgres://root:toor@localhost/life_pex >> .env.local
rake db:migrate


  • configuration: check
  • setup dependencies: check
  • setup database: check

You can simply start the application.


Service, update, etc.

You may want to take a look at the scripts/ directory which contains tons of config helper, for nginx, systemd, etc.

recap image today image


Generate documentation

xdg-open ./public/doc/index.html


Generate first a specific configuration file

cp .env.local .env.test.local
editor .env.test.local # don't forget to set a new database !!!

Then init the database

LIFEPEX_ENV=test rake db:migrate

Then if you want to run the test, simply type rake test (you will need the startup env variable to be set first).


Some debug options can be enabled with the env variable