Links and private services on one profile page.
dev.site gives you a page at dev.site/@you. It holds links and services. A service is a TCP port on one of your machines, for example a database or a development server. You choose who can see and use each item.
You run Postgres on port 5432 on your laptop. A teammate needs to query it. On your laptop, name the port and keep the daemon running:
devsite service host 5432 --name postgres
devsite daemon runShare postgres with your teammate on the dashboard. They accept the share, get a ticket from your profile, and run:
devsite connect dst_***
# connected to postgres
# listening on 127.0.0.1:43127Their psql now connects to 127.0.0.1:43127. The data goes from their machine to yours. Your laptop does not open a port to the internet.
Links work in the same way, without the daemon:
devsite link set --name docs --url https://docs.example.com --publicThen sign in, create a machine ticket on the dashboard, and use it on this machine:
devsite login dmt_***dev.site handles sign-in, profiles, shares, and permission for each connection. It does not carry your service data. It does not know your local port numbers.
A sandboxed agent can ask for a service by name. You see the request and approve it. The agent then gets a short-lived grant for that one service. You can revoke it.
devsite access request postgres --request request.json --key requester.keyOn your machine, find the service, check the plan, and approve it.
devsite access resolve postgres
devsite access grant --request request.json --plan
devsite access grant --request request.json --approved-plan dsp_***The agent connects with its grant.
devsite access connect dss_*** --key requester.keyStart devsite daemon run with Homebrew services or systemd. Your services then stay available after a restart.