Content
@
https://warpcast.com/~/channel/fc-devs
0 reply
0 recast
0 reaction
vrypan |--o--|
@vrypan.eth
What is the expected relationship between a domain and a miniapp? - Right now, one domain can only host a single miniapp, right? - Can multiple miniapps be hosted on the same domain? - How are subdomains treated? - Will any one the answers to the above change in the near future?
5 replies
2 recasts
9 reactions
Steve
@stevedylandev
In my experience each sub domain is treated as a separate app, and I don’t see why that would change. That’s kinda how the web works. In theory you could even have an app hosted on a path if you designate / set it up correctly (sounds painful though)
1 reply
0 recast
3 reactions
horsefacts
@horsefacts.eth
one app per unique subdomain. so example.com, app.example.com, www.example.com, and app.examples.example.com would all be different apps. you can host multiple as subdomains of a root domain but they are all considered different apps. no special treatment of the subdomain/parent domain relationship right now. it’s possible this could change if there’s a really good reason, but unlikely. message bridge communication is restricted by frame origin, which is important to the security model. we’d need something like CORS. The biggest place I see this surface right now is apps that redirect their bare domain to a www subdomain. These are considered two separate mini apps and mixing them causes trouble.
1 reply
0 recast
1 reaction
Andrei O.
@andrei0x309
From what I saw generally 1 DNS address maps well to one mini app. Having multiple mini apps tied to the same DNS address is possible but creates a lot of issues, like not being able to have metadata config for all mini apps, or a good shareable link for each individual app. This is mostly the standard that Warpcast adopted, with the .well-known pattern but it could have been implemented at folder level where farcaster.json would have been searched for each folder, albeit this would have been a messier implementation. Is it advisable to use a domain or subdomain as DNS address but not a sub-sub domain due to how SSL certs are implemented many large providers(eg. Cloudflare) don't support well sub-sub...-sub domains(especially shared certs), so it's best to use domain.extension or prefix.domain.extension.
1 reply
0 recast
0 reaction
Tony D’Addeo
@deodad
each fqdn as well as the root domain can specify one mini app the fqdn / root domain serves as a unique identifier a somewhat common ask is to change the domain but make the app stay the same we don’t have a way to support this but could imagine something like an onchain registry to get a stable unique id but would at another layer of complication so hasn’t been a priority open to ideas
1 reply
0 recast
0 reaction
cashlessman 🎩
@cashlessman.eth
many subdomains = many mini apps
1 reply
0 recast
0 reaction
