stallyns
Web app user switcher for RetroPie/EmulationStation.
What it is
stallyns lets you have separate ROM directories for different users of your system.
For now, it is expected that you have all of your ROMs stored in 'user' directories at ~/roms. See below:
/home/pi/roms/
├── kids
│ ├── atari2600
│ ├── mame-libretro
│ ├── ports
│ └── saves
└── me
├── atari2600
├── mame-libretro
├── ports
└── saves
Installation
$ pip install --upgrade stallyns
or clone this repo and install:
$ git clone https://github.com/dlawregiets/stallyns && cd stallyns && pip install .
Running
Copy the stallyns.service file to ~/.config/systemd/stallyns.service. Reload systemd for the user and then activate and start the service:
systemctl --user daemon-reload
systemctl --user enable --now stallyns.service
Usage
After installing, navigate to http://pi:5000. A list of users will be displayed at the top along with a list of system options at the bottom (useful for if your kids won't turn off the games and you just want to shut the whole thing down).
On your first run, all user buttons will be white. When a user directory is symlinked to ~/RetroPie/roms, their button will be blue.
On the initial user selection in stallyns, ~/RetroPie/roms is moved to ~/RetroPie/roms.orig and a symlink is created from ~/roms/USER to ~/RetroPie/roms.
Issues
I recommend that you quit games before switching users. Killing the active running retroarch or other running application seems to lead to funky states of the display and a restart of EmulationStation does not fix it.
Save States (optional)
I prefer to keep my save state and save files separate from the ROMs, so I do the following:
Modify /opt/retropie/configs/all/retroarch/retroarch.cfg to set the following:
savefile_directory = "/home/pi/RetroPie/roms/saves/"
savestate_directory = "/home/pi/RetroPie/roms/saves/"
Metadata
Release files for stallyns 0.1.2
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 | |
|---|---|---|---|---|
| stallyns-0.1.2.tar.gz | 4.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| stallyns-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 12.7 kB
Release files / stallyns-0.1.2.tar.gz
| Download URL | stallyns-0.1.2.tar.gz |
|---|---|
| Size | 4.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3466897d80a14a61b234becfa65d0bb945d6e8f75d2764cb71d5d7b42764376c
|
|
BLAKE2b-256 checksum How to use checksums |
1f6877451da6ef5b0b4be288ee86c11b5c5b77f88f60c3268e89d413eb52c211
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/40.8.0 requests-toolbelt/0.9.1 tqdm/4.31.1 CPython/3.6.7
|
Release files / stallyns-0.1.2-py3-none-any.whl
| Download URL | stallyns-0.1.2-py3-none-any.whl |
|---|---|
| Size | 8.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6a96af8693db0175872b151fe6269f5ac6d409c3a2251d2d61775dc94703801e
|
|
BLAKE2b-256 checksum How to use checksums |
83f3b13cbb4de5ef24ad830a5ae92803a01cb051751421a056499689453c7f88
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/40.8.0 requests-toolbelt/0.9.1 tqdm/4.31.1 CPython/3.6.7
|
Security for stallyns 0.1.2
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.