From 22fa9ba456a76a09e4510019ea350bf3d8dc6264 Mon Sep 17 00:00:00 2001 From: Patrick Robertson Date: Tue, 11 Feb 2025 18:52:28 +0000 Subject: [PATCH] further tweaks --- docs/source/development/creating_modules.md | 7 ------- docs/source/installation/configurations.md | 4 ++-- 2 files changed, 2 insertions(+), 9 deletions(-) diff --git a/docs/source/development/creating_modules.md b/docs/source/development/creating_modules.md index 7ee65ef..87137ca 100644 --- a/docs/source/development/creating_modules.md +++ b/docs/source/development/creating_modules.md @@ -27,13 +27,6 @@ Check out the [core modules](https://github.com/bellingcat/auto-archiver/tree/ma The manifest file is where you define the core information of your module. It is a python dict containing important information, here's an example file: -```{code} python -:filename: myfile.py - -def setup(): - pass -``` - ```{include} ../../../tests/data/test_modules/example_module/__manifest__.py :name: __manifest__.py :literal: diff --git a/docs/source/installation/configurations.md b/docs/source/installation/configurations.md index b83a064..d534106 100644 --- a/docs/source/installation/configurations.md +++ b/docs/source/installation/configurations.md @@ -21,11 +21,11 @@ The recommended way to configure auto-archiver for long-term and deployed projec A default `orchestration.yaml` will be created for you the first time you run auto-archiver (without any arguments). Here's what it looks like:
-View example.orchestration.yaml +View example orchestration.yaml ```{literalinclude} ../example.orchestration.yaml :language: yaml - :caption: example.orchestration.yaml + :caption: orchestration.yaml ```