Wallabag - A self hostable application for saving web pages: Save and classify articles. Read them later. Freely.

	Commit message (Collapse)	Author	Age	Files	Lines
*	Fold migrations & fixtures command on Travis	Jeremy Benoist	2017-05-19	1	-36/+0
\|
*	fixup! Manually import file for PostgreSQL	Jeremy Benoist	2016-12-19	1	-6/+6
\|
*	Remove comment	Jeremy Benoist	2016-12-19	1	-11/+0
\| \| \| \|	"The string "--" is not permitted within comments."
*	And of course it doesn't work for SQLite	Jeremy Benoist	2016-12-19	1	-0/+9
\|
*	Manually import file for PostgreSQL	Jeremy Benoist	2016-12-19	1	-8/+13
\|
*	Run migration in test, ready for MySQL	Jeremy Benoist	2016-12-19	1	-11/+90
\|
*	Move test parameters out of parameters.yml	Jeremy Benoist	2016-04-12	1	-6/+6
\| \| \| \|	The end user doesn't care to about the test database.
*	Disable xdebug all the time	Jeremy Benoist	2016-01-21	1	-12/+4
\| \| \| \| \| \|	Use travis_wait to avoid travis timeout on `composer up` Jump to `memory_limit -1` for `composer up` Also, since composer.lock is ignored, we can remove it.
*	Ignore composer.lock	Jeremy Benoist	2016-01-20	1	-1/+1
\| \| \| \| \| \| \| \| \| \| \|	Having a big composer.lock on a final project can have side effect on incoming PR that add a new vendor. Mostly because conflict are too frequent. By ignoring composer.lock we ease the PR submission and rebase. BUT we need to be careful when we release a new version of wallabag. We should manually `git add -f composer.lock` to update it. Since composer.lock will no longer be commited I switch the `composer install` to a `composer up` in the travis configuration.
*	Update path in build file	Jeremy Benoist	2016-01-15	1	-9/+9
\|
*	Add multiple database tests on Travis	Jeremy Benoist	2015-09-26	1	-2/+50
\|
*	And phpunit with html coverage to ant	Jeremy	2015-04-01	1	-0/+7
\| \| \| \|	Launching `ant phpunit` will now generate HTML Coverage
*	Simplify build system	Jeremy	2015-03-03	1	-0/+43