tre
/
fic-archive
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
master
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'f758ec46ad'
${ noResults }
fic-archive/README.org

2.2 KiB
Raw Blame History Unescape Escape

Code for my personal fic archive

Preliminaries

This is very much set up for my own use, but the code is public so others can see how this works and build similar things for themselves, if they like.

build.sh generates files in the build directory and uploads them to the remote using rclone. To build locally for testing, run python3 generate.py local, which generates links that point straight to index.html instead of the containing directory.

This is for my personal use and definitely won’t work as is for other people, but feel free to dig around in the files. I am an amateur and I almost certainly don’t follow best practices in any respect.

Fic metadata lives in originalsmeta/ following the template, translation metadata in translationsmeta/; the filename for each is a unique 3-digit number. Fic files with the corresponding filenames live in texts (HTML, PDF, and EPUB are recognised in the script, which then moves them into build/files/ or build/secret/ according to metadata).

On the server my secret/ folder is protected using .htpasswd. In the current setup the comments are sent to my private Discord server using webhooks, so do modify the POST request in the comments pages if you don’t want your own test comments being sent to my server, haha.

Requisites: rclone (just for uploading files to the server), Python 3.

My use case

  • most of my current fandoms are numbered parts of a bigger franchise
  • some of my fics have both English and French versions
  • I have a lot of juvenilia that I want to place behind a veneer of protection
  • some but not all of my fics are on AO3; HTML, PDF and EPUB formats exist for most, but this can be adjusted for individual entries as needed
  • whether commenting is enabled on a particular fic depends on a couple of factors

Future plans [3/6]

  • redirect to a consent page using local storage (h/t Fandom Coders)
  • pages for times and locations in FF fandoms
  • possibly a page for non-FF fandoms (as if I even care about these lol)
  • python-based browser for loading in fic metadata and grabbing stats (“what were my top ships in 2022” etc.) – in progress
  • drabble wall
  • link to singles pages from headers? on the number?