Weave Code
Server Laravel Package
exposedev/server
exposedev/server is the server-side component of Expose, the open-source PHP tunneling service. Run your own tunnel server to securely expose local Laravel or PHP applications to the web, with WebSocket-based connections and a self-hosted alternative to ngrok.
At a glance
Frequently asked questions about Server
- What is exposedev/server and what does it do?
- exposedev/server is the server-side component of Expose, an open-source PHP tunneling service. It lets you run your own tunnel server so local Laravel or PHP applications can receive public URLs through firewalls and VPNs. It uses WebSocket-based connections and is positioned as a self-hosted alternative to ngrok.
- How do I install exposedev/server with Composer?
- Install the package through Composer, then review and publish any configuration or environment settings required by your deployment. Start the Expose server process using the command and options documented in the repository. Because certificate-related behavior changed in 3.2.0, validate the setup in staging before production.
- Does exposedev/server require Laravel, or can I use plain PHP?
- The package is aimed at Laravel and PHP applications, so it can fit plain PHP deployments if your runtime meets the package requirements. Laravel teams benefit from the usual Composer, environment, and configuration workflow. Check the repository requirements before choosing it for a non-Laravel stack.
- Which Laravel versions are supported by exposedev/server?
- The provided material does not list exact Laravel version constraints, so check composer.json and the 3.2.0 release notes before upgrading. Confirm compatibility in a staging environment rather than assuming support from the overview alone. Pay particular attention to certificate-related configuration and permissions.
- How do I expose a local Laravel app through a firewall or VPN?
- Run the Expose client alongside your local Laravel application and point it at your self-hosted exposedev/server instance. The client opens a WebSocket connection to the server, which provides a public URL that routes traffic back to the local app. This outbound connection pattern is what allows the setup to work through many firewall and VPN environments.
- Is exposedev/server a good self-hosted alternative to ngrok?
- It is a reasonable option for teams that want more control over tunnel infrastructure and prefer not to depend entirely on a managed service. You run the server yourself, so you also own TLS, DNS, access control, updates, and monitoring. Evaluate the operational overhead against the control and cost benefits for your team.
- What security concerns should I consider when self-hosting Expose?
- Treat the tunnel server as internet-facing infrastructure and review authentication, host scoping, TLS settings, logging, and firewall rules carefully. Restrict which internal hosts and applications can be exposed, and protect certificate storage permissions. Monitor tunnel traffic and certificate issuance during rollout, especially if multiple teams or tenants share the server.
- What changed in exposedev/server 3.2.0 for TLS certificates?
- Version 3.2.0 extends the server’s certificate automation to its own infrastructure hosts. That reduces reliance on external certificate provisioning workflows and keeps TLS lifecycle management closer to the application control plane. No breaking changes are indicated, but certificate configuration should still be tested explicitly.
- How are certificates issued, renewed, and stored for infrastructure hosts?
- The 3.2.0 feature adds on-demand certificate automation for scoped infrastructure hosts, but the exact ACME or CA provider, validation method, and storage path depend on your configuration. Review certificate storage permissions, renewal behavior, revocation handling, and rate-limit safeguards before enabling it broadly. Test issuance and renewal with one low-risk internal host first.
- Does exposedev/server 3.2.0 affect multi-tenant isolation or existing tunnel certificates?
- No breaking changes are indicated, so existing tunnel behavior should remain stable if your configuration and permissions are correct. However, host scoping and multi-tenant certificate settings should be verified in staging before expanding the feature. Monitor existing tunnel traffic and certificate issuance during rollout.
Weaver
How can I help you explore Laravel packages today?