Config backup, a Docker dev/prod split, and a Gitea-built release image.
Added
- /settings -> General -> "Configuration backup": JSON export/import of the
panel's general settings + attribute definitions
(App\Services\ConfigBackupService); audited as config.export / config.import.
Export can leave out the attribute-encryption key. No AD data included.
- docker/compose.dev.yaml: live-reload dev stack that bind-mounts the working
tree. docker/php/Dockerfile is now multi-stage (base -> dev / prod).
- .github/workflows/release.yml: on every vX.Y.Z tag, builds the prod image and
pushes gitea.kzbikowski.pl/kzbkowski/adconsole:{X.Y.Z,X.Y,latest}.
Changed
- docker/compose.yaml: self-contained prod image (app code + composer install
--no-dev baked in via COPY); persistent state in docker/data/{app_storage,db};
defaults to the released image (ADCONSOLE_VERSION pins a tag, ADCONSOLE_IMAGE
replaces the ref). Apache now honours public/.htaccess (AllowOverride All).
Run from the repo root with --env-file .env.
- Repo root now holds only README.md; CHANGELOG / CONTRIBUTING / SECURITY /
CODE_OF_CONDUCT moved under docs/.
Upgrade notes: docs/upgrading.md#v110--docker-layout. Full log: docs/CHANGELOG.md.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01JKT9p3bfP8RZesExdYCS52
47 lines
1.8 KiB
Markdown
47 lines
1.8 KiB
Markdown
# Code of Conduct
|
|
|
|
## Our pledge
|
|
|
|
We as members, contributors and maintainers pledge to make participation in the
|
|
ADconsole project a harassment-free experience for everyone, regardless of age,
|
|
body size, visible or invisible disability, ethnicity, sex characteristics,
|
|
gender identity and expression, level of experience, education, socio-economic
|
|
status, nationality, personal appearance, race, religion, or sexual identity
|
|
and orientation.
|
|
|
|
## Our standards
|
|
|
|
Examples of behaviour that contributes to a positive environment:
|
|
|
|
- Being respectful of differing opinions, viewpoints and experiences
|
|
- Giving and gracefully accepting constructive feedback
|
|
- Focusing on what is best for the project and its users
|
|
- Showing empathy towards other community members
|
|
|
|
Examples of unacceptable behaviour:
|
|
|
|
- Sexualised language or imagery, and unwelcome sexual attention
|
|
- Trolling, insulting or derogatory comments, and personal or political attacks
|
|
- Public or private harassment
|
|
- Publishing others' private information without explicit permission
|
|
- Other conduct which could reasonably be considered inappropriate in a
|
|
professional setting
|
|
|
|
## Enforcement
|
|
|
|
Instances of abusive, harassing or otherwise unacceptable behaviour may be
|
|
reported to the project maintainer through the channel listed in
|
|
[`SECURITY.md`](SECURITY.md) (mark it "conduct"). All complaints will be
|
|
reviewed and investigated promptly and fairly. Maintainers are obligated to
|
|
respect the privacy and security of the reporter.
|
|
|
|
Maintainers may remove, edit or reject contributions that violate this Code of
|
|
Conduct, and may temporarily or permanently ban any contributor for behaviours
|
|
they deem inappropriate, threatening, offensive or harmful.
|
|
|
|
## Attribution
|
|
|
|
Adapted from the [Contributor Covenant][cc], version 2.1.
|
|
|
|
[cc]: https://www.contributor-covenant.org/version/2/1/code_of_conduct/
|