You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Possible idea: instead of downloading files to the current folder, they could be stored in a /files folder (or a folder provided as an argument, for example: a temp file on a ram drive to save space and dump old files on reboot). This can currently be accomplished by making a folder, cding into it, and running ../stream. This does, however, require/generate a new client/usercred.secret file.
The text was updated successfully, but these errors were encountered:
To achieve this on my own machine, I've created an alias: alias fediplay="(cd /path/to/fediplay/files; ../stream)"
This creates a subprocess so as not to mess with the current directory, but still keeps the credentials and media files contained in the subfolder. These two paths could be changed arbitrarily to allow fediplay to run and live in two different arbitrary folders, if someone did want to do that to keep things organized.
Possible idea: instead of downloading files to the current folder, they could be stored in a /files folder (or a folder provided as an argument, for example: a temp file on a ram drive to save space and dump old files on reboot). This can currently be accomplished by making a folder, cding into it, and running ../stream. This does, however, require/generate a new client/usercred.secret file.
The text was updated successfully, but these errors were encountered: