To make startup of pupcloud easier we can use a config file

[marioscube]

When I first used pupcloud I started it with

pupcloud -r /home/user/pupcloud

That is easy and relatively quick to type.

After some experimenting with pupcloud my startup line evaluated to

pupcloud -r /home/user/Share/pubcloud -H 1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef --max-upload-size 128 -E --share-profile John:S3cr3t --share-profile James:S5cr5t --share-prefix 'http://domain.com:12345/pupshare' --follow-symlinks

This is a bit much to type .............

ENHANCEMENT: wouldn't it be nice to ha a config file (pupcloud.conf) to start pupcloud.

pupcloud might be started with: pupcloud -c pupcloud.conf
option -c is config.file

[proofrock]

I feel you're right 😬; it was a conscious design decision to try and do without any kind of database, dotfile or config file... right or not, I wanted to play within the constraint and see what I can still do.

To address your issue: in "next" version of pupcloud there will be support for env variables. They can be used to write a "rich" shell script that looks like a config file, maybe? Something like:

export PUP_ROOT=/home/user/Share/pubcloud
export PUP_PWD_HASH=1234567890abcde...
export PUP_MAX_UPLOAD_SIZE=128
export PUP_ALLOW_EDITS=1
export PUP_SHARE_PROFILES=John:S3cr3t,James:S5cr5t
export PUP_SHARE_PREFIX=http://domain.com:12345/pupshare
export PUP_FOLLOW_SYMLINKS=1
./pupcloud

You need to export them, it seems. I'm a bit surprised about this, it seems there's something about Go. Also putting in the same command as pupcloud works, but to format it you must use \:

PUP_ROOT=/home/user/Share/pubcloud \
PUP_PWD_HASH=1234567890abcde... \
PUP_MAX_UPLOAD_SIZE=128 \
PUP_ALLOW_EDITS=1 \
PUP_SHARE_PROFILES=John:S3cr3t,James:S5cr5t \
PUP_SHARE_PREFIX=http://domain.com:12345/pupshare \
PUP_FOLLOW_SYMLINKS=1 \
./pupcloud

[proofrock]

I wrote some docs reflecting this discussion, thanks.