moparisthebest
/
HttpUploadComponent
mirror of https://github.com/moparisthebest/HttpUploadComponent
1
0
Fork 0
Code Issues Releases Wiki Activity
HttpUploadComponent/config.yml

18 lines
810 B
YAML
Raw Normal View History

make sure we use same domain across different examples
2015-07-22 04:58:38 -04:00
jid: upload.yourdomain.tld
secret: yoursecret
inital commit
2015-06-28 05:21:30 -04:00
storage_path : ./
whitelist:
make sure we use same domain across different examples
2015-07-22 04:58:38 -04:00
- yourdomain.tld
- someotherdomain.tld
inital commit
2015-06-28 05:21:30 -04:00
max_file_size: 20971520 #20MiB
make sure we use same domain across different examples
2015-07-22 04:58:38 -04:00
http_address: 127.0.0.1 #use 0.0.0.0 if you don't want to use a proxy
inital commit
2015-06-28 05:21:30 -04:00
http_port: 8080
make sure we use same domain across different examples
2015-07-22 04:58:38 -04:00
get_url : http://upload.yoursite.tld:8080
put_url : http://upload.yoursite.tld:8080
Add expiry and user quotas Expiry and user quotas are controlled by four config options: ```expire_interval``` determines how often (in seconds) files should be deleted. As every expiry run needs to check all uploaded files of all users this should not be set too small. Files older than ```expire_maxage``` (in seconds) will be deleted by an expiry run. Set this to ```0``` to disable deletions based on file age. After an expiry run at most ```user_quota_soft``` space (in bytes) will be occupied per user. The oldest files will be deleted first until the occupied space is less than ```user_quota_soft```. Set this to ```0``` to disable file deletions based on a users occupied space. ```user_quota_hard``` sets a hard limit how much space (in bytes) a user may occupy. If an upload would make his files exceed this size it will be rejected. This setting is not dependend on ```expire_interval```. Set this to ```0``` to disable upload rejection based on occupied space. ```expire_maxage``` and ```user_quota_soft``` depend on ```expire_interval```. ```user_quota_hard``` is honoured even without expiry runs. But some kind of expiry is recommended otherwise a user will not be able to upload anymore files once his hard quota is reached. The difference between ```user_quota_hard``` and ```user_quota_soft``` determines how much a user may upload per ```expire_interval```.
2015-07-26 18:04:54 -04:00
#keyfile: /etc/ssl/private/your.key
#certfile: /etc/ssl/certs/your.crt
expire_interval: 82800 #time in secs between expiry runs (82800 secs = 23 hours). set to '0' to disable
expire_maxage: 2592000 #files older than this (in secs) get deleted by expiry runs (2592000 = 30 days)
user_quota_hard: 104857600 #100MiB. set to '0' to disable rejection on uploads over hard quota
user_quota_soft: 78643200 #75MiB. set to '0' to disable deletion of old uploads over soft quota an expiry runs