NixOS service service portability scripts standardized #607
Labels
No labels
0 points
0.5 points
1 point
13 points
2 points
21 points
3 points
34 points
5 points
55 points
8 points
ambition
application-offering
ambition
configure-applications
ambition
front-end
ambition/install-applications
ambition
security
ambition
switch-host
ambition
update-applications
ambition
user-management
api service
blocked
component: fediversity panel
component: nixops4
documentation
estimation high: >3d
estimation low: <2h
estimation mid: <8h
infinite points
productisation
project-management
question
role: application developer
role: application operator
role: hosting provider
role: maintainer
security
technical debt
testing
type unclear
type: bug
type: deliverable
type: key result
type: objective
type: task
type: user story
user experience
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Depends on
#100 migrating application data between hosting providers
fediversity/fediversity
#601 applications imported from contract-based implementations
fediversity/fediversity
#602 contracts available in nixpkgs
fediversity/fediversity
Reference
fediversity/fediversity#607
Loading…
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?
As a Fediversity maintainer,
given that we are able to import applications from contract-based implementations (#601),
and back-up mechanisms are standardized in Nixpkgs (see #602),
and we have found best practices surrounding implementation of full-service portability (#100),
I want for such version migration scripts to be standardized for use in Nixpkgs,
so that we may upstream such logic and more often find support for this from NixOS service modules out of the box.