Documentation: Create Installation Directory Standards Guide #95
Labels
No labels
apache
api
api-contract
api-gateway
authentication
automation
breaking-change
comments
component/deployment
component/documentation
component/service-management
configuration
contact-form
coordination/cross-repo
coordination/needed
core
deployment
development
development-ready
digital-sovereignty
distribution
effort
large
effort
medium
effort
small
enhancement
frontend
furt-service
furt/gateway
furt/installation
gateway
gateway-integration
generator
gitea-testing
health-check
help-wanted
hugo
hugo-integration
infrastructure
installation
logging
low-tech
mail
meta
meta/duplicate
meta/planning
meta/wontfix
monitoring
observability
openapi
organization
packaging
performance
planning
platform/linux
priority
high
priority
low
priority
medium
production
question
sagjan
security
service
service-analytics
service-development
service-formular2mail
service-newsletter
service-request
service-sagjan
session
blocker
session
handover
session
next
shortcode
specs
ssl
status
blocked
status
done
status
in-progress
status
review
status
to-go
systemd
testing
tooling
type
admin
type
bug
type
config
type
deployment
type
docs
type
enhancement
type
feature
type
handover
type
infrastructure
type
installation
type
maintenance
type
migration
type/refactor
type
research
type
security
type/testing
v0.1.0
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: DAW/furt#95
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Dokumentation: Linux/BSD Installation Directory Standards
Zusammenfassung der Research aus Issue #71 und #94 in strukturierte Dokumente.
Problem:
Wir haben umfangreiche Research zu Installation-Pfaden durchgeführt:
Aber: Knowledge ist in Issues verstreut → schwer auffindbar für Entwicklung
Lösung: Standard-Pfade-Dokumentation
Dokument 1: Vollständige Dokumentation
Pfad:
docs/meta/meta-installation-paths.mdInhalt:
Dokument 2: Essenz für Claude-Context
Pfad:
docs/meta/meta-installation-paths-essenz.mdInhalt:
Research-Basis:
/etc/vs/usr/local/etc/(BSD vs Linux)/usr/local/bin/(universell)/usr/local/lib/+ Lua-Module-PfadeNutzen:
Akzeptanzkriterien:
meta-installation-paths.mdmit vollständiger Distribution-Matrixmeta-installation-paths-essenz.mdfür Quick-ReferenceAufwand: Medium (Research ist komplett, nur strukturieren)
Priorität: High (blockiert saubere furt-Installation)
Status: Ready to implement - Research aus #71 und #94 zusammenfassen
Issue #95 Complete - Installation Directory Standards Documentation (2025-08-30)
Research aus Issue #71 und #94 erfolgreich in strukturierte Dokumente konsolidiert.
Deliverables Complete:
✅ Vollständige Dokumentation erstellt:
Datei: docs/meta/meta-installation-paths.md (2.800+ Zeilen)
Inhalt:
✅ Essenz für Claude-Context erstellt:
Datei: docs/meta/meta-installation-paths-essenz.md
Inhalt:
Key Standards Definiert:
Universal Standard: /usr/local/ PREFIX
Distribution-spezifische Config-Pfade:
Service-Separation-Pattern:
Detection-Order standardisiert:
Research-Basis:
Nutzen für DAW-Projekte:
Akzeptanzkriterien Complete:
Status: Ready for use in furt and all DAW-projects
Files Created: