desired subdomains are assigned to deployed services #110
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
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
2 participants
Notifications
Due date
No due date set.
Blocks
#78 Start deployment migration
fediversity/fediversity
#99 applications deployed on command
fediversity/fediversity
#100 migrating application data between hosting providers
fediversity/fediversity
#118 Relevant email accounts are provisioned such that the operator may be contacted
fediversity/fediversity
Reference: fediversity/fediversity#110
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?
As a Fediversity user,
I want to use selected sub-domains for my services,
so that I may configure the URLs to my visitors' needs.
implementation notes
clients / utils
clan dyndns module: tied to their servicegodns(module, providers)dns.nix: zone files|godns| | | | | |given this compatibility matrix, the path of least resistance to automating DNS would seem server
bind(optionally with client octodns (thru TF / NixOS-DNS)).c.f.:
open questions
This needs to be rewritten to a user story instead of being phrased in terms of implementation details. If I try imagining what it would be like, I don't see the difference to #109. Isn't all of this actually about being able to (register and then) select a DNS record before deployment?
The deployment process informs the DNS service of the IP of provisioned VMs, so that the right subdomain can be assigned to itto desired subdomains are assigned to deployed services