- Nov 02, 2015
-
-
Vermaat authored
-
- Oct 26, 2015
-
-
Vermaat authored
-
- Oct 20, 2015
-
-
Vermaat authored
Caching of transcript protein links received from the NCBI Entrez service is a typical use case for Redis. This implements this cache in Redis and removes all use of our original database table. An Alembic migration copies all existing links from the database to Redis. The original `TranscriptProteinLink` database table is not dropped. This will be done in a future migration to ensure running processes don't error and to provide a rollback scenario. We also remove the expiration of links (originally defaulting to 30 days), since we don't expect them to ever change. Negative links (caching a 'not found' result from Entrez) *are* still expiring, but with a longer default of 30 days (was 5 days). The configuration setting for the latter was renamed, yielding the following changes in the default configuration settings. Removed default settings: # Expiration time for transcript<->protein links from the NCBI (in seconds). PROTEIN_LINK_EXPIRATION = 60 * 60 * 24 * 30 # Expiration time for negative transcript<->protein links from the NCBI (in # seconds). NEGATIVE_PROTEIN_LINK_EXPIRATION = 60 * 60 * 24 * 5 Added default setting: # Cache expiration time for negative transcript<->protein links from the NCBI # (in seconds). NEGATIVE_LINK_CACHE_EXPIRATION = 60 * 60 * 24 * 30
-
- Aug 10, 2015
-
-
Vermaat authored
-
- Apr 30, 2015
-
-
Vermaat authored
This is a work in progress as there still seem to be some bugs. For example, some unit tests fail due to incorrect descriptions generated and others fail due to a crash.
-
- Aug 27, 2014
-
-
Vermaat authored
See http://pytest.org/
-
- Aug 26, 2014
-
-
Vermaat authored
Based on comments by Jeroen in issue #14.
-
- Apr 25, 2014
-
-
Vermaat authored
-
- Apr 23, 2014
-
-
Vermaat authored
This is quite a large commit, touching many things related to developer documentation. It is all focussed on getting as much of this as possible into the new Sphinx-based documentation. Some highlights: - Start Sphinx-based developer documentation, including fairly complete instructions for installation and configuration. - Remove epydoc API docs. - Rework some docstrings to conform to reStructuredText, so they can be used in the API docs generated by Sphinx. - Move all of the top-level text files to reStructuredText so they can linked from the Sphinx-based docs and for consistency. - Remove many obsolete things from the extras/ directory, including old installation scripts and migrations. Many of the installation related documentation and scripts are removed or adapted in light of the new automated deployment using Ansible.
-