Launchstead / First-site guide
From your project to a client website
A practical guide for approved private-access users. Start with a small, non-critical website you already own or have permission to manage.
Access is arranged with Ivan. This guide does not create an account or promise a paid plan. Ask about your project before moving a client site.
1. Check the fit
Bring a static HTML, CSS and JavaScript website, or a supported Node.js web app. If you use a frontend framework, a locally built static output folder may be the simplest starting point. Ask first if your app depends on a database, persistent uploads, background workers, native dependencies or external services.
Docker and GitHub deployment are not enabled in the current private service. Domain purchasing and live payment collection are not available. You can connect a domain you already own.
2. Prepare your ZIP
- Static website: place
index.htmlat the ZIP root alongside its assets. Avoid an extra enclosing folder. - Node.js app: include
package.jsonwith a start script andpackage-lock.json. The server must listen on0.0.0.0and use the suppliedPORT. The build uses npm. - Keep the ZIP within the displayed upload limit, currently 10 MiB. Omit secrets, private keys,
.envfiles andnode_modules. Check with the operator before deploying anything requiring secret configuration.
3. Create and publish
Sign in to your approved account, choose your workspace and create a website of the appropriate type. Check the displayed website allowance first. Add an internal client label in Website settings if you manage sites for several clients.
Upload the ZIP. For Node.js, build the uploaded version before publishing it. Follow the website’s displayed next action. Uploading files or seeing “Ready to publish” does not mean the new version is online.
While work runs, the website shows its current stage. If it needs attention, review the message and available logs before retrying. A long wait alone does not prove a failure; avoid creating duplicate requests. Send support the displayed reference if you need help, without sending credentials.
4. Connect your existing domain
Open the website’s domain controls and enter the exact hostname you want, such as www.example.com. Add the ownership and routing records shown by the portal at your current DNS provider, then verify. Keep unrelated email and DNS records intact.
Wait for the portal to confirm publishing and HTTPS. Open the exact connected address and check the main pages, assets and any application routes. DNS changes can take time; do not replace an existing live route until you are ready for the switch.
5. Review it with your client
Use Clients to invite an approved account to this website. Client review access shows its publication status and connected address. It does not permit uploading, publishing, reading logs or managing billing. You can revoke access and review recent access changes.
Team membership covers the entire workspace. A client label is only an organizational label; it grants no access and does not transfer ownership.
6. Make one real update
Upload a small content change, build if needed and publish it. Confirm the result at the connected address. Review retained release history and the available restore controls so you know where to recover from an unsuccessful update.
Use the portfolio’s client and status filters to find work needing attention. An older version can remain live while your next update awaits publication. “Share summary” prepares a reviewable status snapshot you can copy into your own message; it sends nothing automatically.
Before calling the pilot successful
- Your intended domain opens over HTTPS and key pages work.
- You have published one update and know how to find recovery controls.
- Your client can see only the website shared with them.
- You know the current limits, who maintains the site and how to request help.
Tell us how long the first publication took, where you needed help and what prevented a second website. We use this feedback to improve the private pilot. No public pricing or service-level commitment is offered yet.