A place for developers to talk about building on Farcaster.

/dev

Orbiter now has full @ensdomains support! In just a matter of seconds you can link your Orbiter site to your ENS, where it will automatically update the ENS contentHash record to the latest state of your website. No need to mess with IPNS or paying gas fees over and over; set once and forget it. Powered by @base , @ipfs , and ipcm.dev. Check it out today at orbiter.host!

For those interested I've just published the contract used resolving the ENS records through Obiter! 

https://github.com/orbiterhost/orbiter-resolver

Personally nerded out quite a bit over this thing. It checks the records on the Public Resolver and Legacy Public Resolver first before falling back to offchain gateway. With this approach all of the records a user recorded on the Public Resolver will essentially carry over and be unaffected when switching to Orbiter's resolver. 

ENS is some cool shit

DIST

is there an option to deploy with one command without having to install the dep globally?

maybe something like

```
GITHUB_TOKEN="..." npm x create -d my-site ./dist
```

DX Engineer | Head of Developer Relations at /pinata | Building orbiter.host | stevedylan.dev/links

Oooo I dig that idea! I think it's possible, I'll have to experiment

Confirmed; you can just use npx for everything! 

npx orbiter-cli auth -k <API_KEY>

npx orbiter-cli create -d my-site ./dist

That’s a good point; I can definitely add that in!

the killer feature would be to make it work with 1 command

usually clis do this by letting you auth automatically if you pass auth token (ie the cli checks for a specific environment variable like ORBIT_AUTH_TOKEN). npm, bun, wrangler and a bunch of other tools do this