#631: remove -D on server add #448
Manually merged
coop-cloud
merged 2 commits from 2024-11-27 19:48:32 +00:00
ammaratef45/abra:removeDomainCheck into main
Dismiss Review
Are you sure you want to dismiss this review?
Labels
Clear labels
bug
build
ci/cd
critical fix
design
documentation
duplicate
easy-first-issue
enhancement
help wanted
i10n
i18n
installer
invalid
question
release
release-candidate
security
tech-debt
test
wontfix
Something is not working
go build related issues
Building things with CI/CD
https://docs.coopcloud.tech/federation/resolutions/passed/010/
UI/UX
Documenting all the things
This issue or pull request already exists
Something for new people to get stuck into. We hope it's easy!
New feature
Need some help
Everything to do with localisation
Everything to do with internationalisation
Everything to do with the install script.
Something is wrong
More information is needed
Release management
Related to the new release candidate
Security related
Unit/integration testing
This won't be fixed
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
3wordchant
aadil (Aadil Ayub)
abra-bot (Abra Bot)
ammaratef45
amras (Sarma)
Apfelwurm
BornDeleuze
Brooke
carla
cas (Cassowary)
coopcloud
cyrnel
decentral1se (d1)
dede
devydave
fauno (fauno)
iexos
jade (Jade Ambrose)
jjsfunhouse
jmakdah2 (Jackie Makdah)
joe-irving (Joe Irving)
kawaiipunk (KawaiiPunk)
knoflook
kolaente
lambdabundesverband
linnealovespie (April)
moosemower
moritz
notplants
oxaliq (sorrel)
p4u1
pharaohgraphy (Andrew 🐦🔥❤️🔥✴️)
renovate-bot (Comrade Renovate Bot)
ripclap
simon
sixsmith (Sixsmith)
stevensting
trav (Trav Fryer)
val (val (he/him))
yksflip
Clear assignees
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: toolshed/abra#448
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
toolshed/organising#631
Nice one @ammaratef45! That's a great start.
There are however still some places where domain checks are carried out. See
EnsureDomainsResolveSameIPv4also underabra app deploy ...which relates to toolshed/organising#631 (comment).I think taking a scan of
pkg/dns/..., seeing what is in there in terms of functions and where those get called will give you an overview of the logic. I think the idea is that domain checking happens once on theabra server addand from then on in, it's "up to you"./cc @p4u1 @fauno
@@ -122,3 +119,1 @@of your ~/.ssh/config. Checks for a valid online domain will be skipped:abra server add -D example`,`,Might seem like a nitpick but this "`" needs to be on the same line as the
"default"or else a newline is created in the help output ofabrawhich is inconsistent with the rest of the commands as far as I remember 🙃Ah, mia culpa
I thought the idea is that domain checking results only in a warning for
server addbut since apps can have domains that are not subdomains of the server then we need to keep domain checking for them?Or do we want to have this as a warning in all of the cases? I could just remove the
-Dparameterinternal/cliand go chase everywhere where an error shows up if that's the goal@ammaratef45 I understood from toolshed/organising#631 (comment) that perhaps the additional domain checks on deploy were also a hindrance? @fauno will hopefully weigh in on this shortly.
We can also just merge as-is as @p4u1 is suggesting (this change stands on its own and is good anyway pending coop-cloud/abra#448 (comment))! Feel free to click the big green button!
😢