This project provides both a CLI (using click) and a webapp (using flask), which generate a playlist of 10 Bible Chapters (represented by 10 mp3 files) to be listened to on any given day x, according to Professor Grant Horner's Bible-Reading System. The audio Bible is as downloaded from the Faith Comes by Hearing® website.
You can see the webapp in action here
Start by ensuring that you have Docker and Docker Compose:
# check that you have docker on your machine
docker -v
# check that you have docker-compose on your machine
docker-compose -v
If you don't have Docker and Docker Compose, then click the respective links above for installation instructions for your platform.
Good to have if you'd like to hack on the project. Not required if you just wanna run it, in which case Docker and Docker Compose will suffice.
pip install --upgrade pip
pip install -r requirements.txt
.pre-commit install
followed by pre-commit install --hook-type commit-msg
. Optionally run pre-commit run --all-files
to make sure your pre-commit setup is okay.npm install
Upon cloning this repository (or forking + cloning your fork), navigate to the cloned project directory.
Then create the required environment variables file (.env
) by making a copy of the provided sample file env/.env.example
and renaming it to env/.dev.env
:
cp -v env/.env.example env/.dev.env
NOTE: If you're not using a docker-based deployment approach, then, for production, the file should be
.prod.env
, for staging.stage.dev
You should be able to run the project without updating anything. If you wanna update the mail settings (which you probably don't really need immediately) -- you could use a service like mailtrap.io for development. If you choose Mailtrap, then the variables to update are TENLISTS_EMAIL_USER_DEV
and TENLISTS_EMAIL_PWD_DEV
. The other settings are for use in production (SERVER_NAME
and SENTRY_DSN
).
Build the images and spin up the containers:
docker-compose up -d --build
When you run the above for the first time, it may take a while, depending on your internet connection speed.
If everything goes well, you should be able to get into the web
container and access the shell.
docker-compose exec web bash
Once you're in the container, run the following to simultaneously launch the Flask development server and the frontend tooling:
inv start
You can access the dev server at http://127.0.0.1:8000.
Note
Now, at this stage, you probably won't get much from the now running app, because you actually need the MP3 files to work with! So, especially for the CLI tool, you have to download the Audio Bible from the Faith Comes by Hearing® website. The 2001 ESV dramatized Bible (size is over 2Gb) formed the basis for this project's code, including the expected filenames. If the file naming convention has changed, then there's a chance everything will break. Anyway, I hope that won't be the case ...
For the web app, we previously would create a directory ENGESVC2DA
in tenlists/webapp/ten_lists/static/
and place your downloaded MP3 files in there. See this line in tenlists/webapp/ten_lists/main/routes.py
.
However, the code has been rewritten in such a way as to use a cloud service (s3, MinIO, Backblaze, Cloudinary, etc.) for the files. This should hopefuly simplify both on-boarding and deployment, especially that at the time of writing this the webapp is deployed using Dokku. You'll therefore have to upload these files to your preferred cloud provider, and set the environment variable TENLISTS_MP3_CLOUD_STORAGE_BASE_URL
(see that .env.sample
file for details).
This project started off initially as a CLI tool to generate these mp3 files on my computer and play them on a USB stick or copy them over to my phone. However, the scope later changed to have a web application that can allow me to listen from anywhere. So lately the focus has been more on the webapp than the CLI.
Notwithstanding, if you wanna use the CLI, you need to firstly ensure that you have a folder containing the required MP3 files, as described above. If you don't specify the folder when running the CLI tool, it'll assumes that there's a directory ENGESVC2DA
in the project root. Once you've sorted this out, then you can run the CLI tool with the --help
option so that you see how to use it:
If you have a setup a python virtual environment and installed the python dependencies as described earlier in this README
python tenlists/cli/__main__.py --help
So, for example 1, if I have my Bible folder ENGESVC2DA
in the project root, and I run python tenlists/cli/__main__.py -d 87
, I'll see the following in the console
❯ python tenlists/cli/__main__.py -d 87
_ _ __
|_)o|_ | _ |_)| _. |o __|_ /__ _ ._ _ .__._|_ _ ._
|_)||_)|(/_ | |(_|\/||_> |_ \_|(/_| |(/_|(_| |_(_)|
/
Welcome to the Bible Playlist Generator
Creating a playlist for day 87 ...
✓ playlist for day 87 successfully created.
✓ Copying of the Bible Chapters into the day087 directory was successful.
✓ ID3 tag info for the generated files in this directory has been updated.
✓ The files have been renamed in a sequential order.
-----Soli Deo Gloria-----
What has happended here? Well,
day087.m3u
in the project rootday087
, in the project root -- containing the 10 MP3 files in the above playlistExample 2; if I want to use tenlists/webapp/ten_lists/static/ENGESVC2DA/
as my folder, then I'll go ahead and
python tenlists/cli/__main__.py -d 87 -f tenlists/webapp/ten_lists/static/ENGESVC2DA/
And I'll see the same results!
If you're using Docker
docker-compose exec web python tenlists/cli/__main__.py --help
Everything remains the same as the case where you're not using Docker.
docker-compose exec web pytest
WARNING: Running this test will delete the directory `tenlists/webapp/ten_lists/static/ENGESVC2DA/, so please ensure that you have a copy of your MP3 files somewhere. This shouldn't be the case though, and I intend to fix it soon, as you can see it's top on the TODO list. Feel free to submit a PR if this hasn't been fixed!
You can deploy this project using your preferred choice of deployment (Docker, Heroku, Linux Server, etc.). However, I have set it up to be ready "out of the box" for deployment to a VPS using Dokku.
If you're gonna use Dokku, feel free to use @engineervix/pre-dokku-server-setup to setup an Ubuntu Server on your VPS prior to installation of Dokku. You can have a look at this gist for more details of how to deploy an application to Dokku. Other excellent resources:
tenlists/webapp/ten_lists/static/ENGESVC2DA/
and deleting its contentsdocker-compose exec web python tenlists/cli/__main__.py --help
is too long to type!configparser
might come in handy here.webapp
directory for the source code. Also see the package.json
file.og:image
: https://unsplash.com/photos/TNlHf4m4gpI