------------
Audman
A simple wsgi web page to control a running audacious media player process.
Audman uses the standard python wsgi module to mount a web app,
using mako templates, and
IPC over dbus to access a runnning audacious process
Manual
------------
1. Install virtualenv
$ virtualenv --system-site-package audman && source audman/bin/activate
3. Install this package
(audman)$ pip install audman
4. Run audman
(audman)$ runaudman
Audman: Audacious Audio Player Control listening on http://192.168.H.HHH:8051
5. Use audman
browse to http://192.168.H.HHH:8051, replacing 192.168.H.HHH with the actual
ip address printed on the console by the runaudman command.
Notes
------------
* alternate system install by wheel
./setup.py bdist_wheel
sudo pip install --no-index -v -v -v dist/audman-0.2.1-py2.py3-none-any.whl
runaudman
* adhoc source installation
./setup.py sdist
cp dist/audman-0.2.0.tar.gz ~
cd ~
tar ztvf audman-0.2.0.tar.gz
cd audman
./audws.py
* quick setup and test
./setup.py bdist_wheel
PYTHONPATH=dist/audman-0.2.1-py2.7.whl python -m audman.audws
* options
"runaudman -e" or "runaudman --enque" => default to enqueing rather than playing
"runaudman -p <port>" or "runaudman --port=<port>" => listen on specified port
"runaudman -l" or "runaudman --playlists_locked" => no playlist select options
* todo
- get the browsers to cache images files (even on meta refresh)
-? mute button
<button type="button" id="mute">Mute</button>
- apache fcgi integration; other wsgi adapters (dbus permissions)?
-? async controls ala ajax
-? tracklist scroll bars; reacting in real-time vie ajax?
* issues
- switching to view a second playlist in the audacious gui causes
audacious<=3.5 to report the wrong current track
- can other playlist be scrolled through without making them active?
** playlist selection
- could we list the names other playlists without making them active?
- could we list the names of tracks (or the complete "playlist-display")
in playlists without making them active?
Note that the icons are from
https://github.com/google/material-design-icons
a much appreciated resource.
Metadata
Release files for audman 0.3.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| audman-0.3.2.tar.gz | 17.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| audman-0.3.2-py2.7.egg | Legacy Egg format | - | - | Details |
Total release size: 51.6 kB
Release files / audman-0.3.2.tar.gz
| Download URL | audman-0.3.2.tar.gz |
|---|---|
| Size | 17.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
79ab7498dd7c38b0f75aafe28f02381c5dcb4bc2341e6dc123257b384205655d
|
|
BLAKE2b-256 checksum How to use checksums |
05208ae2ec841f10fa936673ed4ca415b7c24b29353858dcdad4dc2c596532ed
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / audman-0.3.2-py2.7.egg
| Download URL | audman-0.3.2-py2.7.egg |
|---|---|
| Size | 34.3 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
4e1aa9fe75dc4b0b90d58ec7acb8fa0474bd57de18c74fd4272f4ac9866942dc
|
|
BLAKE2b-256 checksum How to use checksums |
9c26f85c413e8561bf77562c98306ab5552adb8958854936dc6d1b21f2479ad8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for audman 0.3.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.