Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/nens/nens-meta
Plone/meta-like repo for keeping project infra up to date
https://github.com/nens/nens-meta
Last synced: 4 days ago
JSON representation
Plone/meta-like repo for keeping project infra up to date
- Host: GitHub
- URL: https://github.com/nens/nens-meta
- Owner: nens
- License: mit
- Created: 2024-02-07T20:34:04.000Z (9 months ago)
- Default Branch: main
- Last Pushed: 2024-05-08T09:34:12.000Z (6 months ago)
- Last Synced: 2024-10-12T17:45:51.016Z (about 1 month ago)
- Language: Python
- Size: 301 KB
- Stars: 0
- Watchers: 3
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGES.md
- License: LICENSE
Awesome Lists containing this project
README
# N&S "meta" repository
Documentation: https://nens-meta.readthedocs.io/ .
Modeled after https://github.com/plone/meta , it is a tool to keep lots of repositories up to date regarding minutia such as "editorconfig", "ruff", "pre-commit" and "github actions". Stuff that's often generated once with a cookiecutter and never afterwards modified, even though there's much goodness to be found in new settings.
The settings and config files go hand in hand with some recommended local settings in your development environment, like recommended vscode extensions.
The basic idea is **make it easy to write clean and neat and correct code without making the process irritating**. Installing vscode's "editorconfig" plugin once is hardly a chore. If a project's editorconfig file then prevents you from ever having to worry about lineendings, trailing spaces, indentation and other non-content-related stuff... that's a win.
Note that [our cookiecutter template](https://github.com/nens/cookiecutter-python-template) normally should have been the basis from which you started your project. But it might have been created by hand. Or it might have been a long time ago. "Meta" tries to fix up your project a bit.
## Installing/developing this project
For the basic instructions, see [our own documentation](https://nens-meta.readthedocs.io/en/latest/usage.html). So:
$ python3 -m venv .venv
$ source .venv/bin/activate
$ pip install -r requirements
$ pytest
$ pre-commit run --all## TODO
- manifest.in
- docker-compose
- Projectnummer
- testen met vscode
- `DJANGO_SETTINGS_MODULE = artifact_handler.developmentsettings` in tool:pytest?