Files
supabase/apps/studio/components/interfaces/Settings/General/CustomDomainConfig/CustomDomainActivate.tsx
Ivan Vasilov 56de26fe22 chore: Migrate the monorepo to use Tailwind v4 (#45318)
This PR migrates the whole monorepo to use Tailwind v4:
- Removed `@tailwindcss/container-queries` plugin since it's included by
default in v4,
- Bump all instances of Tailwind to v4. Made minimal changes to the
shared config to remove non-supported features (`alpha` mentions),
- Migrate all apps to be compatible with v4 configs,
- Fix the `typography.css` import in 3 apps,
- Add missing rules which were included by default in v3,
- Run `pnpm dlx @tailwindcss/upgrade` on all apps, which renames a lot
of classes
- Rename all misnamed classes according to
https://tailwindcss.com/docs/upgrade-guide#renamed-utilities in all
apps.

---------

Co-authored-by: Jordi Enric <jordi.err@gmail.com>
2026-04-30 10:53:24 +00:00

137 lines
5.3 KiB
TypeScript
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
import { useState } from 'react'
import { toast } from 'sonner'
import { Button } from 'ui'
import { Admonition } from 'ui-patterns/admonition'
import ConfirmationModal from 'ui-patterns/Dialogs/ConfirmationModal'
import { DocsButton } from '@/components/ui/DocsButton'
import Panel from '@/components/ui/Panel'
import { useProjectSettingsV2Query } from '@/data/config/project-settings-v2-query'
import { useCheckCNAMERecordMutation } from '@/data/custom-domains/check-cname-mutation'
import { useCustomDomainActivateMutation } from '@/data/custom-domains/custom-domains-activate-mutation'
import { useCustomDomainDeleteMutation } from '@/data/custom-domains/custom-domains-delete-mutation'
import type { CustomDomainResponse } from '@/data/custom-domains/custom-domains-query'
import { DOCS_URL } from '@/lib/constants'
export type CustomDomainActivateProps = {
projectRef?: string
customDomain: CustomDomainResponse
}
export const CustomDomainActivate = ({ projectRef, customDomain }: CustomDomainActivateProps) => {
const [isActivateConfirmModalVisible, setIsActivateConfirmModalVisible] = useState(false)
const { data: settings } = useProjectSettingsV2Query({ projectRef })
const { mutate: checkCNAMERecord, isPending: isCheckingRecord } = useCheckCNAMERecordMutation()
const { mutate: activateCustomDomain, isPending: isActivating } = useCustomDomainActivateMutation(
{
onSuccess: () => {
toast.success(`Successfully activated custom domain`)
setIsActivateConfirmModalVisible(false)
},
}
)
const { mutate: deleteCustomDomain, isPending: isDeleting } = useCustomDomainDeleteMutation({
onSuccess: () => {
toast.success(
'Custom domain setup cancelled successfully. It may take a few seconds before your custom domain is fully removed, so you may need to refresh your browser.'
)
},
})
const endpoint = settings?.app_config?.endpoint
const onActivateCustomDomain = async () => {
if (!projectRef) return console.error('Project ref is required')
checkCNAMERecord(
{ domain: customDomain.hostname },
{ onSuccess: () => activateCustomDomain({ projectRef }) }
)
}
const onCancelCustomDomain = async () => {
if (!projectRef) return console.error('Project ref is required')
deleteCustomDomain({ projectRef })
}
return (
<>
<div className="flex flex-col items-start">
<Panel.Content>
<div className="flex flex-col gap-2">
<h4 className="text-foreground">Enable your custom domain</h4>
<p className="text-sm text-foreground-light">
Set up is almost complete. Press Activate below to enable{' '}
<code className="text-code-inline">{customDomain.hostname}</code> for this project.
</p>
<p className="text-sm text-foreground-light">
We recommend that you schedule a downtime window of 20 - 30 minutes for your
application, as you will need to update any services that need to know about your
custom domain (e.g client side code or OAuth providers).
</p>
</div>
<div className="mt-4">
<Admonition
type="note"
title="Retain your CNAME record for service continuity after activation"
>
<p>
Your custom domain CNAME record for{' '}
<code className="text-code-inline">{customDomain.hostname}</code> should resolve to{' '}
{endpoint ? (
<code className="text-code-inline">{endpoint}</code>
) : (
"your project's API URL"
)}
. If you're using Cloudflare as your DNS provider, disable the proxy option.
</p>
</Admonition>
</div>
</Panel.Content>
<div className="w-full border-t border-muted" />
<Panel.Content className="w-full">
<div className="flex items-center justify-between">
<DocsButton href={`${DOCS_URL}/guides/platform/custom-domains`} />
<div className="flex items-center space-x-2">
<Button
type="default"
className="self-end"
onClick={onCancelCustomDomain}
loading={isDeleting}
>
Cancel
</Button>
<Button
disabled={isDeleting}
onClick={() => setIsActivateConfirmModalVisible(true)}
className="self-end"
>
Activate
</Button>
</div>
</div>
</Panel.Content>
</div>
<ConfirmationModal
size="small"
loading={isCheckingRecord || isActivating}
visible={isActivateConfirmModalVisible}
title="Activate custom domain"
confirmLabel="Activate"
confirmLabelLoading="Activating"
onCancel={() => setIsActivateConfirmModalVisible(false)}
onConfirm={onActivateCustomDomain}
>
<p className="text-sm">
Activating <code className="text-code-inline break-normal!">{customDomain.hostname}</code>{' '}
will make it visible to users in place of your projects Supabase domain. The Supabase
domain will continue to work too.
</p>
</ConfirmationModal>
</>
)
}