Feature Request: lifetime restrictions in server config

[bioryb]

Hi once again :) It would be nice - I think not only for my requirements - to set the lifetime more restrictive by the admin. So the admin could say maybe it is only allowed to set 1d and 1w . Maybe another admin would like to have that files are generally and only available for 1 day (1d). If this could be set in the server config - that would really be cool. The client must not really be changed. If he selects a time that is not supported by the server, the file lifetime is set to default.

For the upload by the webui, I changed the template to only support 1w . That works, but not for the terminal client ;) (I do not know programing in go :-/ )

Thank you very much!

[depado]

Thanks for your input once again. I had this in mind, and at the start of goploader it was configured like that. I'll think of something for the next version. I'll work on that tomorrow.

Something like :

allowed_limits:
    - 1d
    - 1w

If you had something else in mind for the configuration file, please tell me :+1: I'll have to think of a more generic system for that. I love getting inputs on my projects. I'll set that for the 1.1 milestone which I intend to release soon, with the other improvements you asked.

As for #31 I still don't know where that comes from.

[bioryb]

Maybe

• allowed file types?
• set defaults in config (client)
• monitoring intervall for cleanup

[depado]

As for the allowed file types, I'm not sure I can provide a safe way of filtering. Plus that would cause issues for files uploaded from stdin from the client.

The defaults for the client is a pretty good idea indeed. I'll investigate that.

Shouldn't be a problem to add a monitoring interval for cleanups.

I'll create the issues (otherwise I'll forget) Thanks a lot :+1:

[bioryb]

Forget about the filetypes;)