<img src="./frontend/src/assets/silicolab_logo.png" align="right" alt="Size Limit logo by Anton Lovchikov" width="100" height="100">
The BIBBOX Framework serves as a Basic Infrastructure Building Box (BIBBOX), which provides software solutions in form of apps for biobanking and bioinformatics. It provides the possibility to install apps and serve them directly towards the End-User. In the current state we are building apps to support pathologists, bioinformaticians and biobanks in their direct work as well as in Data-Management.
Please refer to the online documentation at bibbox.readthedocs.io, which includes installation instructions, a user guide and a developer guide for the BIBBOX system.
The frontend is built automatically. If you want to make some changes you can rebuild it with the following command:
docker compose -f docker-compose_frontend_builder.yml up --build -d
Please follow the install instructions on our read the docs page - Install Bibbox(Linux) - for further details.
After the first installation please login in as tempadmin --> switch to the Users tab and create a propper admin user. Logout and login as the newly created admin user so that you can delete the tempadmin, this ensures no one else can access your bibbox using the default tempadmin login. Please note that the tempadmin user is not a fully functional user.
http://127.0.0.1:5011
http://127.0.0.1:5012
http://127.0.0.1:5013
In order to customize the login theme use the theme files in keycloak/themes/custom/login
.
Simply change the html text in the frontend/src/assets/landing.html
file. The changes will automatoically be loaded.
After installation, this text can still be changed under the following path: /opt/bibbox/sys-bibbox/frontend/dist/sys-bibbox-client/assets/landing.html
.
The BIBBOX is structured in multiple docker containers:
Proxy to enable access to the individual installed app and serves the angular frontend.
The backend is built with Flask. Flask is a Python web application framework based on the Web Server Gateway Interface (WSGI) toolkit.
Celery is a task manager which distributes tasks to worker instances. Celery usually uses a message broker such as Redis for the distribution of tasks.
Monitor to inspect celery task.
Postgres is used as database and stores activity ,and system log information, which can be accessed via the frontend.
Redis is an in-memory data structure store, used as a (NoSQL) database, cache, and message broker.
Adminer can be used to access and manage databases.
cadvisor (Container Advisor) provides resource usage and performance characteristics of the running containers.