Shaarli - The personal, minimalist, super-fast, database free, bookmarking service

	Commit message (Collapse)	Author	Age	Files	Lines
*	Process main page (linklist) through Slim controller	ArthurHoaro	2020-07-23	1	-1/+8
\| \| \| \| \|	Including a bunch of improvements on the container, and helper used across new controllers.
*	Apply the new system (Bookmark + Service) to the whole code base	ArthurHoaro	2020-01-18	1	-5/+6
\| \| \| \|	See https://github.com/shaarli/Shaarli/issues/1307
*	Remove the redirector setting	ArthurHoaro	2019-02-09	1	-3/+1
\| \| \| \|	Fixes #1239
*	Optimize and cleanup imports	VirtualTam	2019-01-13	1	-2/+1
\| \| \| \|	Signed-off-by: VirtualTam <virtualtam@flibidi.net>
*	namespacing: \Shaarli\Bookmark\LinkDB	VirtualTam	2019-01-12	1	-1/+1
\| \| \| \|	Signed-off-by: VirtualTam <virtualtam@flibidi.net>
*	lint: apply phpcbf to application/	VirtualTam	2018-12-02	1	-2/+3
\| \| \| \|	Signed-off-by: VirtualTam <virtualtam@flibidi.net>
*	Add history entries for API endpoint	ArthurHoaro	2017-05-07	1	-2/+3
\| \| \| \|	CHANGED: datetime is now store as an object in history store file
*	application: introduce the Shaarli\Config namespace	VirtualTam	2017-03-04	1	-1/+1
\| \| \| \| \| \| \| \| \| \| \|	Namespaces have been introduced with the REST API, and should be generalized to the whole codebase to manage object scope and benefit from autoloading. See: - https://secure.php.net/manual/en/language.namespaces.php - http://www.php-fig.org/psr/psr-4/ Signed-off-by: VirtualTam <virtualtam@flibidi.net>
*	API: expect JWT in the Authorization header	VirtualTam	2017-01-15	1	-3/+8
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Relates to https://github.com/shaarli/Shaarli/pull/731 Added: - require the presence of the 'Authorization' header Changed: - use the HTTP Bearer Token authorization schema See: - https://jwt.io/introduction/#how-do-json-web-tokens-work- - https://tools.ietf.org/html/rfc6750 - http://security.stackexchange.com/q/108662 Signed-off-by: VirtualTam <virtualtam@flibidi.net>
*	REST API structure using Slim framework	ArthurHoaro	2016-12-15	1	-0/+132
	* REST API routes are handle by Slim. * Every API controller go through ApiMiddleware which handles security. * First service implemented `/info`, for tests purpose.