bellingcat/auto-archiver
1
0
Fork 0
mirror of https://github.com/bellingcat/auto-archiver.git synced 2026-06-08 03:18:28 +03:00
Code Issues Packages Projects Releases Wiki Activity

further tweaks

Browse Source
This commit is contained in:
Patrick Robertson
2025-02-11 18:52:28 +00:00
parent 1b976f4c09
commit 22fa9ba456
2 changed files with 2 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
docs/source/development/creating_modules.md
View File

@@ -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:

4
docs/source/installation/configurations.md
View File

@@ -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:
<details>
<summary>View example.orchestration.yaml</summary>
<summary>View example orchestration.yaml</summary>
```{literalinclude} ../example.orchestration.yaml
:language: yaml
:caption: example.orchestration.yaml
:caption: orchestration.yaml
```
</details>