xavi/slcl - Small and lightweight cloud storage written in C99 and POSIX.1-2008.

	Commit message (Collapse)	Author	Age	Files	Lines
*	man1: Replace LICENSE/AUTHORS with COPYRIGHT	Xavier Del Campo Romero	2023-09-27	2	-10/+14
\| \| \| \| \|	LICENSE is not copied to the installation prefix, so adding a short copyright notice instead might be a better reference.
*	CMakeLists.txt: Install targets	Xavier Del Campo Romero	2023-09-27	1	-0/+4
\|
*	Makefile: add install target	Xavier Del Campo Romero	2023-09-27	2	-0/+24
\|
*	slcl.1: Remove obsolete TODO	Xavier Del Campo Romero	2023-09-27	1	-3/+0
\| \| \| \| \| \| \| \| \| \|	This feature was already implemented by: commit 0822a982ef3b085dc109ec373ff537974503eb04 Author: Xavier Del Campo Romero <xavi.dcr@tutanota.com> Date: Sat Jul 8 00:54:59 2023 +0200 Implement file/directory removal
*	Add screenshots	Xavier Del Campo Romero	2023-08-08	2	-0/+0
\|
*	Do some minor rebranding	Xavier Del Campo Romero	2023-08-01	1	-1/+1
\| \| \| \| \| \|	Despite designed around portability and minimalism, I feel slcl no longer aligns with the philosophical views from the suckless project. Therefore, I think it was appropriate to unlink its branding from it.
*	Add man page for usergen(1)	Xavier Del Campo Romero	2023-03-16	2	-0/+95
\|
*	slcl.1: Update TODO	Xavier Del Campo Romero	2023-03-16	1	-1/+1
\| \| \| \| \|	- User quota was implemented by commit ff8da797a. - Public file sharing was implemented by commit 2e1b1313.
*	Implement user quota	Xavier Del Campo Romero	2023-03-06	1	-1/+2
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	This feature allows admins to set a specific quota for each user, in MiB. This feature is particularly useful for shared instances, where unlimited user storage might be unfeasible or even dangerous for the server. Also, a nice HTML5 <progress> element has been added to the site that shows how much of the quota has been consumed. If no quota is set, slcl falls back to the default behaviour i.e., assume unlimited storage. Limitations: - While HTTP does specify a Content-Length, which determines the length of the whole request, it does not specify how many files are involved or their individual sizes. - Because of this, if multiple files are uploaded simultaneously, the whole request would be dropped if user quota is exceeded, even if not all files exceeded it. - Also, Content-Length adds the length of some HTTP boilerplate (e.g.: boundaries), but slcl must rely on this before accepting the whole request. In other words, this means some requests might be rejected by slcl because of the extra bytes caused by such boilerplate. - When the quota is exceeded, slcl must close the connection so that the rest of the transfer is cancelled. Unfortunately, this means no HTML can be sent back to the customer to inform about the situation.
*	Add man page	Xavier Del Campo Romero	2023-02-28	1	-0/+123