Expose Pro
Expose by Beyond Code
Pricing Docs Open Source
Sign up Sign in

Sharing local sites
#

Expose allows you to share any kind of HTTP/HTTPS traffic for websites that you can reach on your own computer, with anyone on the internet.

There are multiple ways to share a site with Expose.

Sharing the current working directory
#

To share the current working directory with Expose, all you need to do is go into the directory and call expose.

This makes the assumption that you have access to the current working directory name as a domain with the .test TLD.

If you are using Laravel Valet, the configured Valet subdomain will automatically be detected.

If you are using a different domain for your local sites, you can change the default TLD that expose uses in the configuration file.

For example:

# Will share a local site "my-site.test" as "my-site.EXPOSE-SERVER"
~/Sites/my-site/ expose

# Will share a local site "api.my-site.test" as "api-my-site.EXPOSE-SERVER"
~/Sites/api.my-site/ expose

If you are using the Expose network on the free plan, you get a random subdomain on every connect. You can upgrade to Expose Pro and use custom subdomains as if you'd host your own server.

Sharing a local site explicitly
#

If your local sites are not available at foldername.test you can explicitly share a local URL, without going into a specific folder first. You can do this by using the expose share command and specify the domain directly.

This is required when sharing sites that have HTTPS locally or Expose can't map local directory names to URLs automatically.

# Will share access to http://192.168.2.100
expose share http://192.168.2.100

# Will share access to http://my-local-site.dev
expose share my-local-site.dev

# Will share access to https://my-local-site.dev
expose share https://my-local-site.dev

Share a local site with a given subdomain ::pro
#

You can also share one of your local sites explicitly and specify the exact subdomain that you want to use when sharing the site. This is very useful if you are testing webhooks and want to use the same webhook configuration and don't update the webhook endpoints on every Expose connect. Custom subdomains require an own Expose server in your infrastructure or Expose Pro.

To specify the subdomain, pass the --subdomain option to expose:

expose share my-site.test --subdomain=my-site

If someone already uses the chosen subdomain on the Expose server, you will see an error message and the Expose server closes the connection.