2015-09-27 20:46:58 +02:00
|
|
|
# Fimfarchive
|
|
|
|
|
2021-01-27 16:24:58 +01:00
|
|
|
Fimfarchive aims to release all stories on Fimfiction as a single ZIP-file. The
|
|
|
|
archive contains not only stories, but also metadata such as tags, ratings, and
|
|
|
|
descriptions. It is organized by author and could be used for backup, offline
|
|
|
|
reading, or data mining.
|
|
|
|
|
|
|
|
Releases can be found on Fimfarchive's [user profile] at [Fimfiction]. Note
|
|
|
|
that this is **not** an official Fimfiction project, so do not send questions
|
|
|
|
to Fimfiction staff. Instead, send a private message or post a comment to the
|
|
|
|
Fimfarchive user profile.
|
|
|
|
|
|
|
|
A new version will be released each season via BitTorrent, approximately once
|
|
|
|
every three months. When suitable, an xdelta3 patch will also be provided for
|
|
|
|
users who do not wish to redownload unchanged stories.
|
|
|
|
|
|
|
|
Note that the archive contains a large number of files. Unzipping it to your
|
|
|
|
file system may not be necessary if the archive is to be used together with
|
|
|
|
some application. If you are a developer, reading directly from the ZIP-file
|
|
|
|
may be preferable.
|
|
|
|
|
2021-01-27 17:32:58 +01:00
|
|
|
This repository contains code for updating and building the archive. While the
|
|
|
|
API is not guaranteed to be stable, it can also be used as a library for easy
|
|
|
|
access to stories and metadata within the archive. A [Fimfiction API] key is
|
|
|
|
however needed to stories directly from Fimfiction.
|
2021-01-27 16:24:58 +01:00
|
|
|
|
|
|
|
[Fimfiction]: https://www.fimfiction.net
|
2021-01-27 17:32:58 +01:00
|
|
|
[Fimfiction API]: https://www.fimfiction.net/developers/api/v2/docs
|
2021-01-27 16:24:58 +01:00
|
|
|
[user profile]: https://www.fimfiction.net/user/116950/Fimfarchive
|
2021-01-27 17:32:58 +01:00
|
|
|
|
|
|
|
|
|
|
|
# Installation
|
|
|
|
|
|
|
|
There are primarily two ways to install this tool. The first is installation as
|
|
|
|
a library for use within other projects, and the second is installation for
|
2021-02-03 16:57:48 +01:00
|
|
|
development of Fimfarchive. Using a [virtual environment] is recommended for
|
2021-01-27 17:32:58 +01:00
|
|
|
both cases in order to avoid contaminating the rest of the Python installation.
|
|
|
|
|
|
|
|
## Installation as a Library
|
|
|
|
|
|
|
|
Make sure a virtual environment has been created and activated. When done,
|
|
|
|
simply install the library directly from the `master` branch on GitHub.
|
|
|
|
|
|
|
|
```bash
|
|
|
|
python3 -m pip install git+https://github.com/JockeTF/fimfarchive.git
|
|
|
|
```
|
|
|
|
|
|
|
|
Optionally also install `lz4` to lower the memory footprint of open archives.
|
|
|
|
|
|
|
|
```bash
|
|
|
|
python3 -m pip install lz4
|
|
|
|
```
|
|
|
|
|
|
|
|
That's it! Import a class to make sure things work as expected.
|
|
|
|
|
|
|
|
```python
|
|
|
|
from fimfarchive.fetchers import FimfarchiveFetcher
|
|
|
|
```
|
|
|
|
|
|
|
|
## Installation for Development
|
|
|
|
|
|
|
|
Start by creating a clone of the Fimfarchive repository.
|
|
|
|
|
|
|
|
```bash
|
|
|
|
git clone https://github.com/JockeTF/fimfarchive.git
|
|
|
|
```
|
|
|
|
|
|
|
|
Enter the cloned repository and create a virtual environment called `venv`
|
|
|
|
within it. Make sure to activate the virtual environment before proceeding to
|
|
|
|
install the development dependencies.
|
|
|
|
|
|
|
|
```bash
|
|
|
|
python3 -m pip install -r requirements.txt
|
|
|
|
```
|
|
|
|
|
|
|
|
Optionally also install `lz4` to lower the memory footprint of open archives.
|
|
|
|
|
|
|
|
```bash
|
|
|
|
python3 -m pip install lz4
|
|
|
|
```
|
|
|
|
|
|
|
|
All done! Run the test suite to make sure everything works as expected.
|
|
|
|
|
|
|
|
```bash
|
|
|
|
pytest
|
|
|
|
```
|
|
|
|
|
|
|
|
[virtual environment]: https://docs.python.org/3/tutorial/venv.html
|
2021-02-03 16:57:48 +01:00
|
|
|
|
|
|
|
|
|
|
|
# Running
|
|
|
|
|
|
|
|
Fimfarchive has a command line interface which is invoked as a Python module.
|
|
|
|
It can't do much except prepare new Fimfarchie releases. For archive browsing
|
|
|
|
you will need to use third-party tools, or make your own.
|
|
|
|
|
|
|
|
```
|
|
|
|
$ python3 -m fimfarchive
|
|
|
|
Usage: COMMAND [PARAMETERS]
|
|
|
|
|
|
|
|
Fimfarchive, ensuring that history is preseved.
|
|
|
|
|
|
|
|
Commands:
|
|
|
|
build Builds a new Fimfarchive release.
|
|
|
|
update Updates stories for Fimfarchive.
|
|
|
|
```
|
|
|
|
|
|
|
|
The command line interface features multiple subcommands, each with its own
|
|
|
|
brief help text. The subcommand is specified as the second program argument.
|
|
|
|
|
|
|
|
```
|
|
|
|
$ python3 -m fimfarchive update --help
|
|
|
|
usage: [-h] [--alpha] --archive PATH [--refetch]
|
|
|
|
|
|
|
|
Updates stories for Fimfarchive.
|
|
|
|
|
|
|
|
optional arguments:
|
|
|
|
-h, --help show this help message and exit
|
|
|
|
--alpha fetch from Fimfiction APIv1
|
|
|
|
--archive PATH previous version of the archive
|
|
|
|
--refetch refetch all available stories
|
|
|
|
```
|
|
|
|
|
|
|
|
Some commands (such as `update`) require a Fimfiction API key. The program
|
|
|
|
reads this key from the environment variable `FIMFICTION_ACCESS_TOKEN`. Any
|
|
|
|
data downloaded from Fimfiction is stored in the current working directory,
|
|
|
|
typically in the `worktree` subdirectory. The same thing goes for rendered
|
|
|
|
stories, built archives, or anything else related to the release process.
|