potistiri_fork_py3 is a fork of potistiri (https://gitlab.com/alexaf/potistiri) originally developped by Alexandros Afentoulis.
The present fork extends the original version in multiple ways:
- support for python 3 (and python 2),
- properly determine HOME directory for storing config files under linux and MacOS,
- support file uploads for files > 2GB (using requests_toolbelt),
- support uploading multiple files using the same settings.
For installation the original instructions apply using however a different download location:
wget https://raw.githubusercontent.com/roebel/potistiri_fork_py3/master/potistiri.py -O /usr/local/bin/potistiri3
chmod +x /usr/local/bin/potistiri3
potistiri is a python cli client for coquelicot file sharing instances. Currently supports two authentication methods: 'simplepass' and 'ldap'.
potistiri is a python script, consequently there are multiple ways to run it. Probably this will be sufficient:
wget https://gitlab.com/irregulator/potistiri/raw/master/potistiri.py -O /usr/local/bin/potistiri
chmod +x /usr/local/bin/potistiri
Alternatively, just clone the repository and run it from there.
potistiri has a configuration file placed in:
~/.config/potistiri/servers.conf
This file can store connection details for a certain coquelicot instance such as the service's url, authentication type and authentication credentials.
You can run potistiri with the '--setconf' parameter in order to initialize the configuration file. Alternatively,you may directly create and edit the file.
Sample configurations files are included in this repo, one for each authentication type, but it's basically like this.
[some_service_name]
server = https://files.provider.org
type = ldap
user = myuser
in case the coquelicot provider needs LDAP authentication. For LDAP providers you may also store the LDAP pass in the conf, but that's probably a bad idea. Also mind the permissions of the configuration file, perhaps:
chmod o-r ~/.config/potistiri/servers.conf
In case of a provider with simple pass authentication conf should look like that:
[some_service_name]
server = https://files.someprovider.org
type = simple
pass = some-upload-password
This pass is actually globally set for the provider and not bound to each user, thus can be considered safe to write on disk.
All the options offered in a coquelicot instance web UI can be passed as parameters to potistiri. Specifically:
- -s/--server : the url of the coquelicot provider
- -f/--file : the path to the file to be uploaded
- -e/--expire : lifetime of the uploaded file in minutes
- -o/--one-time : if set file will be available only for a single download
- -k/--file-key : a phrase key to symmetrically encrypt the uploaded file
- -p/--upload-password : auth in case of a simple pass provider
- -u/--ldap-user : user in case of a LDAP provider
- --setconf : guides user through configuration file initialization
potistiri --setconf
potistiri -f /tmp/ko
potistiri -s https://file.ohmy.net -p passme -f /tmp/la
potistiri -s https://arxeio.net -u ldapalex -f mysecrets.yaml