01Application
A reachable HTTP target.
Record the HTTP or HTTPS address and port, the application owner and its required login. Check that the selected connector can reach it. Identify WebSockets, redirects, uploads and any non-HTTP dependencies.
Fibmesh Publish / Getting started
Start with one app.
Verify the whole path.
Choose an application, prepare its connector and define who needs access. Use this guide to plan, check and arrange your first Publish deployment.
Explore a first setup Setup guide · Confirm platform and deployment support during assisted setup.Publish is available with assisted setup. Confirm supported platforms and deployment requirements. Separately marked proposals remain outside the released scope.
01 / Picture the publication
One public address.
One selected application.
Change the application or connector location to see the target and checks change. This local illustration provisions nothing.
Visitors usehttps://studio-portal.publish.fibmesh.example
Fibmesh gateway → WireGuard → host connector- Application target
http://127.0.0.1:3000- Audience and authentication
- Customers sign in to the portal using its own login.
- What to verify
- Login, customer permissions, uploads and logout.
The target address is read from the selected connector. An Edge connector uses a reachable LAN address instead of another machine’s localhost. The Fibmesh subdomain above is illustrative; .example is not live and the production suffix is not final.
Host connector127.0.0.1 is local to the machine running the connector.
Edge connector192.168.1.20 is an explicit LAN target. Edge hardware remains a development/pilot option.
02 / Before setup
Bring four answers.
A useful first deployment has a known target, a working connector, an audience and an owner.
02Connector
A supported place to run it.
Choose the application host or an approved Edge connector with a route to the LAN service. Confirm supported software, installation permissions, reliable power and an internet connection that permits WireGuard UDP traffic.
03Audience
A clear authentication check.
Identify the people or systems that need access. The application supplies its own login or API authentication. Protected browser access and managed machine credentials remain separate planned extensions.
04Operating owner
Someone responsible for the path.
Name the person responsible for the publication, application and host. Decide who can change the target, respond to a fault or remove access.
03 / Assisted setup
Connect. Select.
Review. Verify.
Arrange setup with Fibmesh. Confirm supported software and the operator procedure for your deployment before activation.
- 01Workspace & connector
Establish the connection.
Select the workspace and enroll a supported connector. Confirm that it belongs to that workspace and has established its outbound WireGuard tunnel to Fibmesh.
Check: correct workspace · enrolled connector · tunnel online - 02Application target
Check from the connector.
Enter the protocol, address and port from the selected connector’s point of view. Verify that the application responds locally before troubleshooting public routing. Localhost belongs to the connector’s environment; an Edge connector needs the app’s reachable LAN address.
Check: intended protocol · explicit address · selected port - 03Address & audience
Choose public reachability.
Use a managed hostname for the core workflow, and make public reachability an explicit choice. Check the app’s own login or API authentication. Custom-domain attachment is planned and requires its own ownership and certificate checks; Fibmesh-managed visitor gates are also planned.
Check: assigned name · deliberate public choice · app authentication - 04Review & activation
Review the exact exposure.
Review the selected connector, exact application target and intended exposure. The gateway and connector apply the authorised configuration. Confirm certificate readiness and application health before treating the public endpoint as ready.
Check: authorised target · HTTPS ready · app reachable - 05Outside visitor
Complete a real task.
Use a browser or API client outside the application’s network. Complete the task your real visitor needs, then test a request that should be denied. A working homepage alone is not an acceptance result.
Check: external task succeeds · unauthorised request is denied
04 / Acceptance checks
Test beyond
the first response.
Verify the application people will actually use. Exercise failure, recovery and removal of access before expanding the deployment.
Application behaviour
Check login and logout, links, redirects, uploads and downloads, and live updates. For an API, verify authentication, error responses and webhook signatures.
Only the intended app
Confirm that another application on the same host does not acquire access through this publication. The selected application and port define the exposure.
Failure and recovery
Disconnect the connector and inspect the public failure response. Restore it and verify that the application recovers through the same public path.
Pause and active sessions
Pause the publication and check new requests. Inspect how existing sessions, including long-lived connections, are handled before relying on pause operationally.
Keep a recovery path
Administration must stay independent.
Keep a separate local administration path to the host or Edge device. Do not depend on the publication you are testing to recover its own connector.
Before expanding
Record the supported software version and observed results, including recovery and existing-session handling.
05 / Your next step
Bring a useful
first application.
Start the conversation with the application, where it runs and who needs access. Fibmesh helps confirm the connector, hostname and deployment requirements.
Application → connector → public name → verified taskAvailable · Assisted setup
Tell us what you want to put online.
Tell us about the application, where it runs and who needs access. We’ll help you confirm the connector, hostname and deployment requirements. Do not include credentials, private keys or customer data.
Request Publish setupOpens your email application. Your request is sent only when you send the email.
Deployment scope, timing and commercial terms are agreed with Fibmesh before setup.