|
|
|
# ForgeFed packaging: overview
|
|
|
|
# Forge Self-Hosting
|
|
|
|
|
|
|
|
- [[Trax/Projects/ForgeFed/forgefed-packaging/overview]]
|
|
|
|
- [[Trax/Projects/ForgeFed/forgefed-packaging/NGI-proposal]]
|
|
|
|
- [[./NGI-proposal]]
|
|
|
|
|
|
|
|
This proposal is to package software components related to the development of forge federation.
|
|
|
|
---
|
|
|
|
|
|
|
|
This proposal facilitates self-hosting software forges.
|
|
|
|
|
|
|
|
To encourage and facilitate work on forge federation, by making it easier for both developers and early adopters to host the components, by providing integrations into existing hosting frameworks.
|
|
|
|
It is packaging work, which in itself is mundane, but it benefits in three directions at the same time. First, it directly helps a person or small group to reclaim self-agency by hosting their own forge. Second, it contributes to the further development of self-hosting systems, by furthering the usefulness of two existing self-hosting systems, encouraging the communities behind them. Third, it facilitates work towards forge federation, by making it easier for both developers and early adopters to deploy multiple forge instances, including both established (Forgejo) and new experimental forges (Vervis+Anvil).
|
|
|
|
|
|
|
|
We are talking about web service deployment packaging (like Docker, Yunohost) rather than OS-level packaging (like Deb, RPM).
|
|
|
|
|
| ... | ... | |
