Crates.io | spotify-launcher |
lib.rs | spotify-launcher |
version | |
source | src |
created_at | 2022-05-10 23:27:00.956833+00 |
updated_at | 2025-01-02 17:16:16.195207+00 |
description | Client for spotify's apt repository in Rust for Arch Linux |
homepage | |
repository | https://github.com/kpcyrd/spotify-launcher |
max_upload_size | |
id | 584223 |
Cargo.toml error: | TOML parse error at line 18, column 1 | 18 | autolib = false | ^^^^^^^ unknown field `autolib`, expected one of `name`, `version`, `edition`, `authors`, `description`, `readme`, `license`, `repository`, `homepage`, `documentation`, `build`, `resolver`, `links`, `default-run`, `default_dash_run`, `rust-version`, `rust_dash_version`, `rust_version`, `license-file`, `license_dash_file`, `license_file`, `licenseFile`, `license_capital_file`, `forced-target`, `forced_dash_target`, `autobins`, `autotests`, `autoexamples`, `autobenches`, `publish`, `metadata`, `keywords`, `categories`, `exclude`, `include` |
size | 0 |
Spotify has a free linux client but prohibits re-distribution, so this is a freely distributable opensource program that manages a spotify installation in your home folder from the official spotify release server.
If you work for spotify please reach out so we can talk. 👉👈
spotify-launcher is going to look for a configuration file at the following locations (in this order):
${XDG_CONFIG_HOME:-$HOME/.config}/spotify-launcher.conf
/etc/spotify-launcher.conf
If no config is found it's going to start with default settings. Your configuration file may look like this:
[spotify]
## Pass extra arguments to the spotify executable
## You can test this with `spotify-launcher -v --skip-update --no-exec`
#extra_arguments = []
## On HiDPI displays spotify doesn't pick up the scale factor automatically
#extra_arguments = ["--force-device-scale-factor=2.0"]
## On wayland you might need
#extra_arguments = ["--enable-features=UseOzonePlatform", "--ozone-platform=wayland"]
GPLv3+