Put a new site live on its domain
Attach a domain to a new site, point its DNS, follow the certificate until it is live, tidy up production settings and verify on the live host.
On this page
Start it
Paste this into an assistant that is connected to Corefinity.
Use the Corefinity MCP prompt "go-live" with site: <the site: its domain, or the id of any of its environments>, domain: <the domain to put live, for example shop.example.com>, www: <which form is canonical: apex (example.com) or www (www.example.com)>. Follow it step by step and tell me before anything that changes my account.Arguments
siteRequired
The site: its domain, or the id of any of its environments.
domainRequired
The domain to put live, for example shop.example.com.
www
Which form is canonical: apex (example.com) or www (www.example.com).
What your assistant is told
Purpose: put <the site's domain> live on the domain <domain>.
- The canonical form: <www> (
apexorwww; when not given, ask the person).
A site you migrated from another host uses the cutover-and-rollback prompt instead.
Before you start
- The row you work on is site row <the id of the site row you work on> (<the environment's name>). Use it as
site_id. - Ask before every change, and type a
confirm_*value only after the person has said yes to that exact action. - If a call is refused because this token lacks a scope or the site is outside its limits, the person is asked to allow it in the Control Panel; carry on once they have.
Steps
- Check. Run
corestack_site_attach_domain_checkandcorestack_domains_check_dnsfor the domain and itswwwtwin. If the check'sblockerslistsplatform_plugins_off, the site's platform plugins are turned off and it cannot go live: tell the person itsmessage, and with their agreement turn them back on withcorestack_. Follow the task it answers until it completes before you attach. Ifsite_ platform_ plugins_ set {enabled: true} blockerslistsplatform_plugins_applying, they are back on but not applied yet: check again in a minute, and if it stays, turn them on again the same way and follow the new task. If the check lists a host inproxied_unconfirmed, Cloudflare proxies it and the Control Panel cannot see the address behind it. When its certificate path blocks it (challenge_path.okfalse), tell the person itschallenge_path.note, the change to make in Cloudflare, and check again once they have made it. When itsverification.foundis false, ask the person to add the TXT recordverification.namewith the valueverification.valuein Cloudflare (it shows the host is theirs), then check again. Once a host isconfirmable, ask the person to check in Cloudflare that its record points at itsexpected_ip, and givecorestack_site_attach_domainproxied_records_checked: trueonly once they say it does. - Attach. Use
corestack_site_attach_domain, orcorestack_domains_updatewhen the domain is already attached, with the canonical form the person chose. A Magento install with several stores stays on one Control Panel site. Readcorestack_site_magento_stores_list; attach each store's domain withaliasesentries{host,. Map itsserve: "storefront", store: {code, type}} wwwform to the same store. Add a store domain later withcorestack_domains_update; change which store an existing address shows withcorestack_. If store codes in URLs were a workaround, switch Add Store Code to URLs off in Magento. Each website's base URL belongs on its own domain, or is left for the attach to set from the site's own addresses. A foreign base URL is left alone unless the person chooses otherwise.site_ magento_ store_ mapping_ update - DNS. If
corestack_company_cloudflare_getshows the domain's zone, point it withcorestack_domains_point_dns. Otherwise give the person the exact records to add. - Follow until the certificate is live, with
corestack_site_operation_getandcorestack_domains_get. - Production settings the person confirms: HTTP authentication off with
corestack_http_auth_update, and search engines allowed withcorestack_domains_update. - Verify on the live host with
corestack_site_http_checkor the smoke test,corestack_site_smoke_test. For each Magento store domain: Request/withcorestack_site_smoke_test, settinghostto the store domain. The final URL must be on that store'sbase_urlhost fromcorestack_site_magento_stores_list(the domain itself, or its bare orwwwform when the base URL uses it), and the title must be that store's. Magento redirects to the store's base URL; a redirect to any other host means its base URL points elsewhere. GraphQL picks its store from theStoreheader, so it cannot prove a domain's store.
Stop and ask
- Before attaching the domain, before changing DNS, and before turning HTTP authentication off.
- If the domain is already live on another server: this is a migration; use
cutover-and-rollback.
When you are done
Report the live address, the certificate's state, and anything the person still has to do at their DNS provider.
Was this helpful?