ohAitch
commented
4 years ago For the former, would a |hi ~dip zod be enough to establish all three? (Assuming ames can privilege the source of correctly signed packets over DNS, when it hears any.)
Probably still recommend the email, to make sure the new neighbor entry isn't overlooked :P
On Tue, Jan 28, 2020 at 08:10, Fang notifications@github.com wrote:
The infrastructure ops page https://urbit.org/using/operations/stars-and-galaxies/ as it currently exists is useful for stars, but doesn't address some of the operations galaxies might want to perform. Specifically:
- Setting up galaxy.urbit.org DNS, which I'm pretty sure is still a manual process. I believe they should be instructed to email urbit.org with their galaxy name, ip address, and some proof of ownership(?).
- Configuring automated software updates through |sync %base ~zod %kids, so that they don't have to worry about doing OTAs themselves if they're fine with the ~zod-sanctioned Arvo version.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/urbit/operators.urbit.org/issues/11?email_source=notifications&email_token=AAOFPBQGWQOELB2OKM64SQ3RABKHFA5CNFSM4KMVDG52YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IJIVIZQ, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAOFPBV5NOB7ROVADWPVKUTRABKHFANCNFSM4KMVDG5Q .
matildepark
The infrastructure ops page as it currently exists is useful for stars, but doesn't address some of the operations galaxies might want to perform. Specifically:
galaxy.urbit.orgDNS, which I'm pretty sure is still a manual process. I believe they should be instructed to email urbit.org with their galaxy name, ip address, and some proof of ownership(?).|sync %base ~zod %kids, so that they don't have to worry about doing OTAs themselves if they're fine with the ~zod-sanctioned Arvo version.