Tags: SpatiumPortae/portal
Tags
> Prompt - (default!) Prompt with a [Y/n] for each file that would be overwritten when receiving files. - Adds `--yes`, `-y` flags that will automatically overwrite files without prompting. > Copying passwords when sending - Adds the `--relay [relay-address]` flag to the copiable `portal receive 1-x-x-x` command when a sender is sending files through a relay which is not the default. > Configuration - New `config` command with useful subcommands to handle your config file. - `portal config view` outputs current config with syntax highlighting. - `portal config path` outputs the path of the config file. - `portal config edit` opens the config file in default $EDITOR. - `portal config reset` resets the config file to its default values. - New configuration options. - `relay: [addr:port|domain]` replaces the `default_rendezvous_address` and `default_rendezvous_port` options. It incorporates both the IP and port into one value, so `relay: 1.2.3.4:8726` is a valid value. - `verbose: [true|**false**]` can now be configured in the config to always output verbose info. - `prompt_overwrite_files: [**true**|false]` can be configured to always prompt, or never prompt when overwriting files. - Changes to config file behavior. - fixes reading configs from the config file (it was broken!). - **moved the config file to `$HOME/.config/portal/config.yml`.** > Valid relay addresses - Now you can use loopback relay addresses on the form `localhost:5432` or `:5432`. Previously, one had to use `127.0.0.1:5432` to address a relay on the loopback interface.
- transfer speed and ETA shown during transfer, total time spent show… …n after transfer - use command completion from cobra - includes completion of passwords from the password-wordlist when invoking portal receive [...] - version (SEMVER) checking, comparison and warnings/errors on non-matching - show summary table of sent/received files during and after transfer - Fix a bug where transfer ID:s would not be released from the relay server in some circumstances
* feat: use zap everywhere * handle absolute and relative paths as expected Previous behavior would take the absolute or relative path and expand the directory structure onto the receiver. This is not what one expects when for instance sending files using the absolute path "portal send /home/zinokader/data/somefile.txt", which previously would actually try to recreate the same directory structure "/home/zinokader..." on the receiver end. Now, we handle absolute paths by sending the last directory or file (and its subfiles/subdirectories), this means "/home/zinokader/folder" will just send and expand "folder" and all of its contents on the receiving end.
PreviousNext