===========================================================
.___ __ __
_________________ __ __ __| _/|__|/ |_
/ ___\_` __ \__ \ | | \/ __ | | \\_ __\
/ /_/ > | \// __ \| | / /_/ | | || |
\___ /|__| (____ /____/\____ | |__||__|
/_____/ \/ \/
grep rough audit - static analysis tool
v2.8 written by @Wireghoul
=================================[justanotherhacker.com]===
mopidy-3.0.2/docs/api/http-server.rst-73-called :class:`MyRequestHandler` that responds to HTTP GET requests with the
mopidy-3.0.2/docs/api/http-server.rst:74:string ``Hello, world! This is Mopidy $version``, where it gets the Mopidy
mopidy-3.0.2/docs/api/http-server.rst-75-version from Mopidy's core API.
##############################################
mopidy-3.0.2/docs/api/http-server.rst-143-The example below shows how a WSGI application that returns the string
mopidy-3.0.2/docs/api/http-server.rst:144:``Hello, world! This is Mopidy $version`` on all requests. The WSGI application
mopidy-3.0.2/docs/api/http-server.rst-145-is wrapped as a Tornado application and mounted at
##############################################
mopidy-3.0.2/docs/config.rst-84- When running Mopidy as a regular user, this should usually be
mopidy-3.0.2/docs/config.rst:85: ``$XDG_CACHE_DIR/mopidy``, i.e. :file:`~/.cache/mopidy`.
mopidy-3.0.2/docs/config.rst-86-
##############################################
mopidy-3.0.2/docs/config.rst-94- When running Mopidy as a regular user, this should usually be
mopidy-3.0.2/docs/config.rst:95: ``$XDG_CONFIG_DIR/mopidy``, i.e. :file:`~/.config/mopidy`.
mopidy-3.0.2/docs/config.rst-96-
##############################################
mopidy-3.0.2/docs/config.rst-109- When running Mopidy as a regular user, this should usually be
mopidy-3.0.2/docs/config.rst:110: ``$XDG_DATA_DIR/mopidy``, i.e. :file:`~/.local/share/mopidy`.
mopidy-3.0.2/docs/config.rst-111-
##############################################
mopidy-3.0.2/docs/ext/http.rst-76- Name of the HTTP service when published through Zeroconf. The variables
mopidy-3.0.2/docs/ext/http.rst:77: ``$hostname`` and ``$port`` can be used in the name.
mopidy-3.0.2/docs/ext/http.rst-78-
##############################################
mopidy-3.0.2/docs/history/changelog-0.x.rst-493-- The default for the :option:`mopidy --config` option has been updated to
mopidy-3.0.2/docs/history/changelog-0.x.rst:494: include ``$XDG_CONFIG_DIRS`` in addition to ``$XDG_CONFIG_DIR``. (Fixes
mopidy-3.0.2/docs/history/changelog-0.x.rst-495- :issue:`431`)
##############################################
mopidy-3.0.2/docs/history/changelog-0.x.rst-613-- When ``mopidy`` is started for the first time we create an empty
mopidy-3.0.2/docs/history/changelog-0.x.rst:614: :file:`{$XDG_CONFIG_DIR}/mopidy/mopidy.conf` file. We now populate this file
mopidy-3.0.2/docs/history/changelog-0.x.rst-615- with the default config for all installed extensions so it'll be easier to
##############################################
mopidy-3.0.2/docs/history/changelog-0.x.rst-1396- ``glib``. The bug can be worked around by overriding the settings that
mopidy-3.0.2/docs/history/changelog-0.x.rst:1397: includes offending ``$XDG_`` variables.
mopidy-3.0.2/docs/history/changelog-0.x.rst-1398-
##############################################
mopidy-3.0.2/docs/history/changelog-0.x.rst-1727-- Default value of ``LOCAL_MUSIC_PATH`` has been updated to be
mopidy-3.0.2/docs/history/changelog-0.x.rst:1728: ``$XDG_MUSIC_DIR``, which on most systems this is set to ``$HOME``. Users of
mopidy-3.0.2/docs/history/changelog-0.x.rst-1729- local backend that relied on the old default ``~/music`` need to update their
##############################################
mopidy-3.0.2/docs/history/changelog-0.x.rst-1732-
mopidy-3.0.2/docs/history/changelog-0.x.rst:1733:- File and path settings now support ``$XDG_CACHE_DIR``, ``$XDG_DATA_DIR`` and
mopidy-3.0.2/docs/history/changelog-0.x.rst:1734: ``$XDG_MUSIC_DIR`` substitution. Defaults for such settings have been updated
mopidy-3.0.2/docs/history/changelog-0.x.rst-1735- to use this instead of hidden away defaults.
##############################################
mopidy-3.0.2/docs/history/changelog-1.x.rst-96-- M3U: Changed default for the :confval:`m3u/playlists_dir` from
mopidy-3.0.2/docs/history/changelog-1.x.rst:97: ``$XDG_DATA_DIR/mopidy/m3u`` to unset, which now means the extension's data
mopidy-3.0.2/docs/history/changelog-1.x.rst-98- dir. This does not change the defaults for desktop users, only system
##############################################
mopidy-3.0.2/docs/history/changelog-1.x.rst-116-
mopidy-3.0.2/docs/history/changelog-1.x.rst:117:- File: Adjust log levels when failing to expand ``$XDG_MUSIC_DIR`` into a real
mopidy-3.0.2/docs/history/changelog-1.x.rst-118- path. This usually happens when running Mopidy as a system service, and thus
##############################################
mopidy-3.0.2/docs/history/changelog-2.x.rst-92-- Files: Fix crash due to mix of text and bytes in paths that come from
mopidy-3.0.2/docs/history/changelog-2.x.rst:93: ``$XDG_CONFIG_HOME/user-dirs.dirs``. (Fixes: :issue:`1676`, :issue:`1725`)
mopidy-3.0.2/docs/history/changelog-2.x.rst-94-
##############################################
mopidy-3.0.2/docs/running/service.rst-184-uncommenting or adding the TCP module to :file:`/etc/pulse/default.pa` or
mopidy-3.0.2/docs/running/service.rst:185::file:`$XDG_CONFIG_HOME/pulse/default.pa` (typically
mopidy-3.0.2/docs/running/service.rst-186-:file:`~/.config/pulse/default.pa`)::
##############################################
mopidy-3.0.2/mopidy/config/types.py-299- - ``~`` to the current user's home directory
mopidy-3.0.2/mopidy/config/types.py:300: - ``$XDG_CACHE_DIR`` according to the XDG spec
mopidy-3.0.2/mopidy/config/types.py:301: - ``$XDG_CONFIG_DIR`` according to the XDG spec
mopidy-3.0.2/mopidy/config/types.py:302: - ``$XDG_DATA_DIR`` according to the XDG spec
mopidy-3.0.2/mopidy/config/types.py:303: - ``$XDG_MUSIC_DIR`` according to the XDG spec
mopidy-3.0.2/mopidy/config/types.py-304- """
##############################################
mopidy-3.0.2/mopidy/internal/xdg.py-12- Additional keys, like ``XDG_MUSIC_DIR``, may be available if the
mopidy-3.0.2/mopidy/internal/xdg.py:13: ``$XDG_CONFIG_DIR/user-dirs.dirs`` file exists and is parseable.
mopidy-3.0.2/mopidy/internal/xdg.py-14-
##############################################
mopidy-3.0.2/mopidy/internal/xdg.py-37- """Returns a dict of XDG dirs read from
mopidy-3.0.2/mopidy/internal/xdg.py:38: ``$XDG_CONFIG_HOME/user-dirs.dirs``.
mopidy-3.0.2/mopidy/internal/xdg.py-39-