[Custom domain] - Implement procedure for processing custom domain requests #105
Labels
No Label
administration
Akkoma
Android
Bare metal
bug
Communication
Community
Cryptpad
Discussion
Documentation
duplicate
enhancement
etherpad
Feature request
Feedback
finances
Fixed
forgejo
fun_project
Goal 2024
help wanted
Howto
🤔️ Investigate
ios
jitsi
lacre
Lacre Test
ldap
Lemmy
LibreTranslate
low prio
Lufi
macos
Mail
Merch
monitoring
movim
needs_refine
New Auth
Nextcloud
nice to have
on hold
proposal
question
Ready
refined
Roundcube
searX
spam-protection
Staging Server
Themes
TOR
Urgent!
Website
windows
wontfix
xmpp
Yearly Report
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Disroot/Disroot-Project#105
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
To process custom domain requests we need to have a clear prodecure that includes all the steps we as admins need to provide for the users as well as having a clear set of post-process tasks both for admins but also for users.
Procedure should document:
I thought we were going to use a form to request a custom domain, isn't it?
I think @muppeth mentioned something about to make it more like an automated process mostly, but we still need to check the donation before enable the feature, right?
This issue was a placeholder to add additional stuff we might need internally to process custom domain requests.
I will change the topic of this issue and add in the first post some things we should have in place for processing custom domain.
[Custom domain] - Implement and document new request workflowsto [Custom domain] - Implement procedure for processing custom domain requests