- Bento v18 implements some new features for branding, which may require changes as described below.
- It also adds MinIO as a backend for future S3-compatible object storage.
- This can be enabled now, but will not be used until a future version.
- For instances hosted on the Secure Data for Health (SD4H) infrastructure, the SD4H object store should be used for production instances when S3-compatible services become ready in a future version.
./bentoctl.bash stop
./bentoctl.bash pull
# set up new Docker networks for MinIO (needed even if MinIO is not set up)
./bentoctl.bash init-docker
- Make sure
lib/public/branding.png
andlib/web/branding.png
are images which work on dark backgrounds. - If you have a light-background logo to add: put this file at
lib/public/branding.lightbg.png
. - If you do not have a light-background logo: run
./bentoctl.bash init-web public
to copy the Bento logo to the above location, or copybranding.png
tobranding.lightbg.png
Version 18 includes two new Bento Public environment variables for customizing an instance:
BENTO_PUBLIC_SHOW_PORTAL_LINK
: Whether to show a link to the private data portal in the headerBENTO_PUBLIC_SHOW_SIGN_IN
: Whether to show a "Sign In" button in the headerBENTO_PUBLIC_FORCE_CATALOGUE
: Whether to force the data catalogue to display, even with only a single project.
The first two are set to true
by default, and the last is set to false
. If desired, they can be toggled to
non-default settings by modifying local.env
, for example:
# ...
BENTO_PUBLIC_SHOW_PORTAL_LINK='false'
BENTO_PUBLIC_SHOW_SIGN_IN='false'
BENTO_PUBLIC_FORCE_CATALOGUE='true'
# ...
To enable the deployment of a MinIO server for S3 storage, refer to the documentation on configuring MinIO for Bento.
./bentoctl.bash start