cookiecutter hooks used in MetWork Framework
-
Updated
Dec 1, 2023 - Python
cookiecutter hooks used in MetWork Framework
centos7 based docker image to build metwork/mfext module
internal mfserv plugin to copy integration branch for metwork-framework repositories
centos8 based docker image to build metwork/mfxxx modules (mfdata, mfserv, mfbase...)
Automatic mflog/nginx correlation for request_id (Metwork usage)
docker build image for python3_ia mfext addon on centos7
system dependencies checker (on various linux distributions)
opinionated python configparser library override to deal with configuration variants (PROD, DEV...)
centos6 based docker image to execute integration tests for metwork/mfxxx modules (mfdata, mfserv, mfbase...)
centos8 based docker image to execute integration tests for metwork/mfxxx modules (mfdata, mfserv, mfbase...)
metwork/mfsysmon module
a github hook as mfserv plugin for managing some pr labelling for metwork-framework organization
the metwork plugin api and tools in a dedicated repository
centos6 based docker image to build metwork/mfxxx modules (mfdata, mfserv, mfbase...)
a jinja2 extension to add a fnmatch filter
very low level C library/utilities for metwork/framework
yet another tool to generate a changelog from git history (with conventional commit spec)
rocky9 image to build metwork/mfserv plugins (with mfserv built on rocky8)
public website sources for metwork-framework.org
run some metwork integration tests on various linux distributions
Add a description, image, and links to the autoreadme topic page so that developers can more easily learn about it.
To associate your repository with the autoreadme topic, visit your repo's landing page and select "manage topics."