Mercurial > libervia-backend
view misc/README @ 3647:57d43e3e0095
docker: set `DBUS_SESSION_BUS_ADDRESS` so that it uses remote TCP with local fallback:
When connecting to Docker service, first the `backend` container will be tried with TCP,
then an Unix Socket will be used as fallback.
The Unix Socket is put in Libervia local dir which is a volume shared between containers.
This way D-Bus can be used with a remote backend, or the backend can be run locally
(notably during build when accounts creation or other settings must be done via Libervia
CLI).
author | Goffi <goffi@goffi.org> |
---|---|
date | Wed, 08 Sep 2021 11:16:00 +0200 |
parents | a27fd445c7c7 |
children |
line wrap: on
line source
This directory contains files related to Libervia but not directly used by it. * file _li: This is the completion file for zsh. To use it, you need to have it in a path accessible in your fpath variable, and to have completion activated. This can be done by the following commands in your .zshrc: ### .zshrc completion ### fpath=(/path/to/directory/with/_li/ $fpath) autoload -U compinit compinit ### end of .zshrc completion ### Then, you should be able to complete a li command line by pressing [TAB]. * org.libervia.Libervia.service: This file is used by D-Bus to know how to launch the backend, you have to put in in D-Bus services dir (usually /usr/share/dbus-1/services) * org.libervia.Libervia*.metainfo.xml: AppStream metadata as specified at https://www.freedesktop.org/software/appstream/docs/ * org.libervia.LiberviaTUI.desktop: Desktop entry for TUI frontend as specified at https://specifications.freedesktop.org/desktop-entry-spec/