This is my blog, powered by quarto. For more details about site content see the deployed instance. To see coverage reports, got see the artifacts on github pages.
For all set ups, make the configuration dir config
and provide the kaggle
configuration in config/kaggle/kaggle.json
:
mkdir config/kaggle -p
To run in development mode, use docker compose like
docker compose --file docker/compose.yaml
This will provide access to quarto
, python
, and r
.
First, ensure that quarto>=1.6
is installed. Then set up a virtual
environment using pyenv
and add install the dependencies using poetry
:
# Add python 3.11
pyenv install 3.11
# Create a virual environment
pyenv virtualenv 3.11 blog
# Make sure that the executables are seen
export PATH=$PATH:$VIRTUAL_ENV/bin
# Verify python version. Should be under ``~/.pyenv``
which python
which pip
# Install poetry
pip install poetry
# Install with poetry
poetry install
# Run the development server
acederbergio serve dev
In theory this should work but I am yet to do this myself. So be aware this is only roughly the process of setting up neovim to play nice with the project and virtual environment.
# Create an ipython kernel. This is necessary to use `molten.nvim` inside of
# neovim. It neads `pynvim` to be setup correctly.
poetry run pip install pynvim
poetry run python -m ipykernal install --user --name blog
git clone https://github.com/acederberg/nvim-ez --output=~/.config/nvim
Next, open neovim
and run :Lazy
in normal and then install the dependencies
by hitting I
.
To render the website, just
cd blog
quarto add quarto-ext/iclude-code-files
quarto render
cd -
To build the docker image, run
export ACEDERBERG_IO_GOOGLE_TRACKING_ID="tracking id here"
docker build --tag acederberg/quarto-blog-builder \
--file ./docker/dockerfile \
--secret id=kaggle_json,src=./config/kaggle/kaggle.json . \
--secret id=google_tracking_id,env=ACEDERBERG_IO_GOOGLE_TRACKING_ID
or use the production compose project:
export ACEDERBERG_IO_GOOGLE_TRACKING_ID="tracking id here"
docker compose --file docker/compose.prod.yaml build
To verify the build metatags use scripts.meta
.