Send files to Nextcloud/Owncloud shared folder using curl

cloudsend.sh

#!/usr/bin/env bash
############################################################
# MIGRATED TO REPOSITORY
# https://github.com/tavinus/cloudsend.sh
#
# This gist will NOT be updated anymore
############################################################


############################################################
#
# cloudsend.sh
#
# Uses curl to send files to a shared
# Nextcloud/Owncloud folder
#
# Usage: ./cloudsend.sh <file> <folderLink>
# Help:  ./cloudsend.sh -h
#
# Gustavo Arnosti Neves
# https://github.com/tavinus
#
# Contributors:
# @MG2R @gessel
#
# Get this script to current folder with:
# curl -O 'https://raw.githubusercontent.com/tavinus/cloudsend.sh/master/cloudsend.sh' && chmod +x cloudsend.sh
#
############################################################


CS_VERSION="0.1.6"

CLOUDURL=""
FOLDERTOKEN=""

PUBSUFFIX="public.php/webdav"
HEADER='X-Requested-With: XMLHttpRequest'
INSECURE=''

# https://cloud.mydomain.net/s/fLDzToZF4MLvG28
# curl -k -T myFile.ext -u "fLDzToZF4MLvG28:" -H 'X-Requested-With: XMLHttpRequest' https://cloud.mydomain.net/public.php/webdav/myFile.ext

log() {
	[ "$VERBOSE" == " -s" ] || printf "%s\n" "$1"
}

printVersion() {
        printf "%s\n" "CloudSender v$CS_VERSION"
}

initError() {
        printVersion >&2
        printf "%s\n" "Init Error! $1" >&2
        printf "%s\n" "Try: $0 --help" >&2
        exit 1
}

usage() {
        printVersion
        printf "\n%s%s\n" "Parameters:" "
  -h | --help      Print this help and exits
  -q | --quiet     Be quiet
  -V | --version   Prints version and exits
  -k | --insecure  Uses curl with -k option (https insecure)
  -p | --password  Uses env var \$CLOUDSEND_PASSWORD as share password
                   You can 'export CLOUDSEND_PASSWORD' at your system, or set it at the call.
                   Please remeber to also call -p to use the password set."
        printf "\n%s\n%s\n%s\n" "Use:" "  $0 <filepath> <folderLink>" "  CLOUDSEND_PASSWORD='MySecretPass' $0 -p <filepath> <folderLink>"
        printf "\n%s\n%s\n%s\n" "Example:" "  $0 './myfile.txt' 'https://cloud.mydomain.net/s/fLDzToZF4MLvG28'"  "   CLOUDSEND_PASSWORD='MySecretPass' $0 -p './myfile.txt' 'https://cloud.mydomain.net/s/fLDzToZF4MLvG28'"
}

##########################
# Process parameters


if [ "$1" = "-h" ] || [ "$1" = "--help" ]; then
        usage
        exit 0
fi

if [ "$1" = "-V" ] || [ "$1" = "--version" ]; then
        printVersion
        exit 0
fi

if [ "$1" = "-q" ] || [ "$1" = "--quiet" ]; then
        VERBOSE=" -s"
	shift
fi

if [ "$1" = "-k" ] || [ "$1" = "--insecure" ]; then
        INSECURE=' -k'
        log " > Insecure mode ON"
        shift
fi

if [ "$1" = "-p" ] || [ "$1" = "--password" ]; then
        PASSWORD=${CLOUDSEND_PASSWORD}
        log " > Using password from env"
        shift
fi


##########################
# Validate input

FILENAME="$1"

CLOUDURL=''
# if we have index.php in the URL, process accordingly
if [[ $2 == *"index.php"* ]]; then
        CLOUDURL="${2%/index.php/s/*}"
else
        CLOUDURL="${2%/s/*}"
fi

FOLDERTOKEN="${2##*/s/}"

if [ ! -f "$FILENAME" ]; then
        initError "Invalid input file: $FILENAME"
fi

if [ -z "$CLOUDURL" ]; then
        initError "Empty URL! Nowhere to send..."
fi

if [ -z "$FOLDERTOKEN" ]; then
        initError "Empty Folder Token! Nowhere to send..."
fi


##########################
# Check for curl

CURLBIN='/usr/bin/curl'
if [ ! -x "$CURLBIN" ]; then
        CURLBIN="$(which curl 2>/dev/null)"
        if [ ! -x "$CURLBIN" ]; then
                initError "No curl found on system!"
        fi
fi


##########################
# Extract base filename

BFILENAME=$(/usr/bin/basename $FILENAME)


##########################
# Send file

#echo "$CURLBIN"$INSECURE$VERBOSE -T "$FILENAME" -u "$FOLDERTOKEN":"$PASSWORD" -H "$HEADER" "$CLOUDURL/$PUBSUFFIX/$BFILENAME"
"$CURLBIN"$INSECURE$VERBOSE -T "$FILENAME" -u "$FOLDERTOKEN":"$PASSWORD" -H "$HEADER" "$CLOUDURL/$PUBSUFFIX/$BFILENAME"

Hi, there are many ways to do that.

You could create a separate script that calls cloudsend.sh $1 <hardcodedUrl>.
So <file> would come from $1 (first parameter) and the URL could be a fixed variable or the URL string.

Example (untested)

#!/bin/bash
CLOUDSENDBIN='/path/to/cloudsend.sh'            # Using full path can avoid errors
SHAREURL='https://cloud.domain.tld/s/xdFvws'    # Your folder share URL

"$CLOUSENDBIN" "$1" "$SHAREURL"

If the share has a password that should also be added.

Example (untested)

#!/bin/bash
CLOUDSENDBIN='/path/to/cloudsend.sh'            # Using full path can avoid errors
SHAREURL='https://cloud.domain.tld/s/xdFvws'    # Your folder share URL

CLOUDSEND_PASSWORD='MySecretPass' "$CLOUSENDBIN" -p "$1" "$SHAREURL"

---

Or you could modify this gist and hard code the URL inside it as well (around line 103).
https://gist.github.com/tavinus/93bdbc051728748787dc22a58dfe58d8#file-cloudsend-sh-L103
Will have to add a new var and use it in place of $2.

Example mod (untested)

SHAREURL='https://cloud.domain.tld/s/xdFvws'    # Your folder share URL
CLOUDURL=''
# if we have index.php in the URL, process accordingly
if [[ $SHAREURL == *"index.php"* ]]; then
        CLOUDURL="${SHAREURL%/index.php/s/*}"
else
        CLOUDURL="${SHAREURL%/s/*}"
fi

FOLDERTOKEN="${SHAREURL##*/s/}"

---

I would argue that it is cleaner the way it is now though.
It behaves like copy A B, which makes more sense for me than using a --url parameter.
So I don't think I will change the main script to behave in a different way.

Cheers! 🍺

Thanks for the lengthy response with examples! I'd prefer to avoid hardcoding modifications or creating secondary scripts though.

I think there's a way that'd satisfy both use cases - how about adding support for both positional parameters and flags?

The script would still be convenient to use by real people, but you could use it in scripts/aliases without hardcoding modifications or ugly workarounds.

I actually went ahead and did just that(along with some other small changes), please take a look - https://haste.rys.pw/raw/afisuwosoz

You can either use the positional arguments like until now, or you can use --file together with --url (have to use both or nothing) and positioning is then ignored.

All the code is there, what's left is to modify usage() to reflect the new changes.

Hi again.
I guess that if you already have a fork that works the way you want, you are good to go.
Like I said, I see no reason to add that complexity and I prefer it the way it is ( copy <source> <destination> ).
Cheers!

I'm not sure if we're on the same page - copy <source> <destination> is still available with my changes, my point was to not break existing usage, it's just that you can ALSO use parameters for easy use in scripts.

There's no real 'complexity' added, I simply put the Process parameters stage into a case statement (which is cleaner) and added a condition if it encounters an unknown(positional) parameter.

I'd prefer to have my changes merged rather than have to maintain my own fork.

I've updated the URL to a file with the usage() changes already present.

@tavinus You may want to move everything here into a github repo, it's maybe getting too large for a single gist ^^

Migrated to repository

https://github.com/tavinus/cloudsend.sh

This gist will not be updated anymore.

Rebuild

I have just rebuilt most of the script and added many improvements.
But it is only available at the new repository.
This gist will be kept as is for all eternity.

The only 'downside' is that the old -p option is now -e, because -p now receives the password as a parameter, as in -p <myPass>.

From here to there, this is the current log (Aug 2020)

• v0.1.7 - Rename
  • Adds option -r / --rename to change the destination (uploaded) file name.
• v2.0.0 - Rebuild
  • Script rebuild; many internal changes
  • Changes how options and parameters are parsed
  • Added many validation and checking functions
  • Options can now come in any order and after the filename and URL Link
  • Updated and added verbose messages
  • Updated quiet mode
  • Updated --help and readme.md
  • Password parsing has changed and is NOT compatible with prior versions
    • -p now asks for a password as a parameter, as in -p <pass>
    • new option -e uses an envrionment variable password (substitutes the old -p option)
• v2.1.0 - Pipes and Globs
  • Adds stdin as input option (piped content)
    • uses either - or . as input file name
    • requires -r <filename>
  • Allows to use globbing at the input
    • can send multiple files by using globs
    • requires -g option
    • not compatible with -r <name> option (rename)
  • Adds new checks and parsing
  • Cleaned up unused code
  • Updated readme and --help
• v2.1.1 - Pipes and Globs (fix)
  • Small fix to file name parsing VS globbing
  • Updated readme globbing link
• v2.1.2 - Pipes and Globs (readme-help)
  • Better help and readme text and examples.
• v2.1.3 - Pipes and Globs (fix2)
  • Disables curl globbing when not globbing.

---

More info on globbing:

• https://github.com/tavinus/cloudsend.sh/wiki/Input-Globbing
• https://ec.haxx.se/cmdline/cmdline-globbing

---

CLICK HERE to see how to send an entire folder (and subfolders?) with the new script and find