devol
/
wallabag
mirror of https://github.com/wallabag/wallabag.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
wallabag/.gitignore

52 lines
833 B
Plaintext
Raw Normal View History

Switch to Symfony 3 structure
2016-01-14 18:15:07 +01:00
# Cache, logs & sessions
/var/*
!/var/cache
1st implementation of wallabag api, yeah
2015-01-28 17:09:27 +01:00
/var/cache/*
!var/cache/.gitkeep
Switch to Symfony 3 structure
2016-01-14 18:15:07 +01:00
!/var/logs
/var/logs/*
1st implementation of wallabag api, yeah
2015-01-28 17:09:27 +01:00
!var/logs/.gitkeep
Switch to Symfony 3 structure
2016-01-14 18:15:07 +01:00
!/var/sessions
/var/sessions/*
!var/sessions/.gitkeep
!var/SymfonyRequirements.php
Remove binary from repo Since Composer 1.2, binaries are re-installed from vendors if there aren't found. This avoid us to commit binaries vendors into the repo. :warning: You have to update your Composer to the 1.2 (`composer selfupdate`)
2016-07-20 10:44:46 +02:00
/bin/*
!/bin/console
!/bin/symfony_requirements
1st implementation of wallabag api, yeah
2015-01-28 17:09:27 +01:00
# Parameters
/app/config/parameters.yml
# Managed by Composer
symfony is there
2015-01-22 08:30:07 +01:00
/vendor/
1st implementation of wallabag api, yeah
2015-01-28 17:09:27 +01:00
# Assets and user uploads
/web/bundles/
/web/uploads/
symfony is there
2015-01-22 08:30:07 +01:00
Simplify build system
2015-03-03 19:20:08 +01:00
# Build
/app/build
/build
symfony is there
2015-01-22 08:30:07 +01:00
1st implementation of wallabag api, yeah
2015-01-28 17:09:27 +01:00
# Composer PHAR
/composer.phar
change gitignore, last time, I promised
2015-01-28 13:28:12 +01:00
1st implementation of wallabag api, yeah
2015-01-28 17:09:27 +01:00
# Data for wallabag
data/assets/*
Add LiipThemeBundle Re-defined the config / user relation to be OneToOne bidirectionnal. ConfigType is now a service so I can inject the list of available themes that are also used by LiipThemeBundle Force sqlite for test In case of people use a different driver in parameter.yml (yes I do :))
2015-02-23 22:55:06 +01:00
data/db/wallabag*.sqlite
Add basic docker-compose configuration
2016-01-09 14:47:32 +01:00
Add Docker configuration for Postgres and MariaDB
2016-01-09 17:27:21 +01:00
# Docker container logs and data
Add basic docker-compose configuration
2016-01-09 14:47:32 +01:00
docker/logs/
Add Docker configuration for Postgres and MariaDB
2016-01-09 17:27:21 +01:00
docker/data/
Ignore composer.lock 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.
2016-01-20 18:49:45 +01:00
# To avoid crazy stuff on some PR, we must manually FORCE ADD IT on each new release
composer.lock
manage assets through npm first draft remote assetic totally work nearly there use at least nodejs > 0.12 use proper version of grunt bump nodejs version for travis update npm workaround for materialize install node 5.0 add grunt-cli baggy theme & cache node modules cache bower & npm make travis build assets on php7 only exclude installing node & npm if not needed & use bash clean & try to make icomoon work on baggy ready config for travis rebase make travis work more travis work impove travis & update deps add missing pixrem deps add module through oddly lost ui updates install latest nodejs add install_dev.sh, link local binaries for npm/bower/grunt ui improvements (mostly baggy) fix travis build no need to install on travis Add unread filter to entries pages Add the ability to filter for unread pages in the filters menu. Add unread filter test to EntryControllerTest Add a new test to the EntryControllerTest collection which checks that only entries which have not been archived (and are treated as "unread") are retrieved. Improve English translation Update FAQ -Fix grammar -Add notes about MTA, firewall, and SELinux Update installation instructions -Fix grammar -Add SELinux section add screenshots of android docu in English Fix the deletion of Tags/Entries relation when delete an entry Fix #2121 Move fixtures to the right place Display a message when saving an entry failed When saving an entry fail because of database error we previously just returned `false`. Now we got an error in the log and the displayed notice to the user is updated too. Change ManyToMany between entry & tag Following https://gist.github.com/Ocramius/3121916 Be sure to remove the related entity when removing an entity. Let say you have Entry -> EntryTag -> Tag. If you remove the entry: - before that commit, the EntryTag will stay (at least using SQLite). - with that commit, the related entity is removed Prepare wallabag 2.0.5 enforce older materialize version
2016-03-08 17:02:34 +01:00
# assets stuff
/node_modules/
!app/Resources/static/lib
app/Resources/static/lib/*
/bin
!/src/Wallabag/CoreBundle/Resources/public
/src/Wallabag/CoreBundle/Resources/public/*