Deploying a Website

Use the SetFN WebSpace release console to deploy a website from individual files or an archive, then manage previous releases and retention.

Before you begin

For an individual-file deployment, place index.html at the selected root. An archive should place index.html at the archive root. If it is absent there, exactly one top-level folder other than hidden folders and __MACOSX must contain index.html; zero or multiple candidates cannot be deployed. You also need the frontend release permission configured by an administrator. The console shows only the actions available to your account and the upload limits configured on the server.

If you have no homepage development experience

Describe the page you want to an AI (ChatGPT, Claude, etc.) and ask it to produce a ZIP file with index.html and separate CSS and JS files. You can upload the ZIP file you receive right away. A site released for the first time uses Strict mode, which blocks styles and scripts written directly inside the HTML. To use a page that keeps its CSS and JS in a single index.html, switch to Web app compatibility in API & site security.

Navigating to the WebSpace admin page

Click Webspace Admin in the upper right of the admin page, then select Frontend releases under Deployment in the left menu.

Deploying a website

1. Open the Deploy Now tab and select the upload area.
2. For a small deployment, select individual files that include index.html. To preserve folders or upload more files, select a .zip, .tar.gz, or .tgz archive.
3. Enter a Release Label and Release Notes.
4. Select Deploy Now and confirm. Archive uploads show progress and can be cancelled while the file is being transferred.

Individual files require index.html at the selected root. An archive requires it at the archive root. If it is absent there, exactly one top-level folder other than hidden folders and __MACOSX must contain it. If an individual-file selection exceeds the file-count or size limit shown in the console, use an archive.

Deployment result

Once deployment is complete, you can view the website immediately at the configured address (https://my-company.setfn.me or a connected custom domain).

Accessing the same address with /@team takes you to the workspace. (e.g., https://my-company.setfn.me/@team)

Review history and activate a previous release

Open Deployment History to review each release's version, creation time, deployer, file count, and size. Select Activate This Version on a previous version to make it public. The previously active release remains in history.

If your account has permission, you can download a release archive, pin or unpin a release, and delete an unprotected release. Protected releases (the current public version, the previous version, and pinned releases) cannot be deleted. Use the actions visible in your console.

Manage storage and retention

In Deployment History, use Storage and retention to review archive, public, and temporary storage. Set the number of recent releases to keep, the maximum pinned releases, and the archive storage limit, then clean up in this order:

1. Select Preview cleanup and review the releases to be removed and the space to reclaim.
2. Select Save policy.
3. Review the preview again, then select Run cleanup.

The current and protected releases are excluded from cleanup. Use Recent activity on the same tab to review deployments, activations, deletions, pin changes, retention changes, and cleanup results.

Choose the operating environment

Webspace serves the website from the Workspace server prepared by the operator. Choose internal-only or public access, and prepare domain, certificate and network access settings for a public site. If you connect external AI or APIs, selected data may be sent to those services. Review the data path and access permissions for each connection.

Related Documents

• What is WebSpace?
• Building a Publicly Accessible Web Service
• Checking the Frontend Sample
• Folder Web View