PRODUCT GUIDE / PRODUKTLEITFADEN
Hosting & Domains
Vigthoria Hosting publishes supported static websites from your project. Use a preview, a Vigthoria subdomain or a verified custom domain, inspect provisioning and HTTPS status, and keep versioned releases with rollback. Domain ownership and registration remain explicit parts of the workflow.
Your first workflow
- 01
Prepare and test the static project output.
- 02
Select preview, subdomain or custom domain.
- 03
Complete required DNS and account setup.
- 04
Check the public URL, HTTPS and saved release status.
Available working areas
Static project releases
Publish the supported HTML, CSS, JavaScript and asset output of your site.
Preview and subdomain
Choose a preview or available Vigthoria subdomain for the reviewed project.
Custom domain verification
Follow the displayed DNS instructions and verify ownership before custom-domain provisioning completes.
HTTPS and provisioning status
Inspect the actual deployment and certificate state rather than assuming the first request is already live.
Version history and rollback
Keep saved releases and restore a supported earlier version through the hosting workflow.
Check the actual result
A public static-site URL, deployment status and saved release history.
Review the output against your task before sharing, publishing or relying on it. Retain the project files or records needed to continue.
Access and product scope
Use an authorized project and the required hosting access. Custom domains need control of the DNS zone and any applicable registration purchase.
The current hosting product is static. Server runtimes, environment-variable execution, managed build commands and a global CDN are not included in that static runtime.
If the next step does not work
I reach sign-in or access is denied.
Sign in with the intended Vigthoria account and reopen this product. Check the selected project, owner or team role and the current product entitlement in User Hub.
The task is queued or a required feature is unavailable.
Inspect the actual job and service state. Check whether the chosen route needs a provider connection, device support, signing setup or an enabled account feature. Keep a saved copy before retrying a completed action.
I need product support.
Include the product, action, time, visible error and relevant job or project identifier. Use a minimal example and keep passwords, secret keys and confidential source material out of the public form.