Repository files navigation

🏦 ⌛ Time Bank management system.Learn more about Time Banks.

TimeOverflow is a software developed in an altruistic way to offer a system thatfacilitates the interaction of the members and the management of the Time Banks.The model on which we work is guided by the needs of the Time Banks that make useof it and is prepared to be able to accommodate several Time Banks in a single installation,for this account with three levels of privileges: superadmin, admin (only manages a bank)and members of a bank.

TimeOverflow is divided into 2 large blocks:

• Management system for administrators
• Social network and online banking for users

NOTE A physical Time Bank can work only with the management block, it could happen, for example, that the vast majority of its members do not use the Internet and may want to operate only with listings, checks and a management office.

Physical Time Banks (mainly focused on TimeOverflow) often work without the Internet, performlists of services and members and pay the hours with heels that are finally entered in the office, thereforethe management system allows us to manage the members and their services, draw lists and keep accounting.It is important that Bank managers (admin) have useful information about the community so that they can act on it(for example, statistics on weak users, incident management, balance of accounts, etc.)

The social network makes it easy for members to meet and meet outside the events scheduled by the Time Bank,as well as being able to post offers / demand ads explained in detail.

On the other hand the members can be paid the services of virtual way to save the passage through the office of the Bankof Time and also have the possibility to consult the extract of their account.

This site is ready to be deployed in production with an optimized Docker image which uses two stages in order to minimize the final image size.

You can locally test the production deployment by the include docker-compose.yml file:

docker compose up

The first time running it will build the image and setup the database along with some seeds in it (testing data). If the database already exists, it will run migrations (if needed) and just start the application.

Go tohttp://localhost:3000 to see the application running.

Note that the current docker-compose.yml is not suitable for a real production deployment, it's just for testing the production Dockerfile locally.For production deployment you should use a real database and a reverse proxy like Nginx or Apache (with SSL enabled).Refer to the next section in order to see the relevant ENV variables to configure the application.

In order to configure the application you can use the following ENV variables:

Make sure to configure at least the ones without a default value (empty).

Any kind of feedback, bug report, idea or enhancement are really appreciated.

To contribute, just fork the repo, hack on it and send a pull request. Don't forget to add tests for behaviour changes and run the test suite by:

bundle exec rspec

You can also run the linter by:

bundle exec rubocop

👉 Further information in ourWiki.

AGPL3

You can find the license filehere.