https://discord.cloudflare.com logo
Join Discord
Powered by
# durable-objects
  • k
    (of millions)
  • e
    😄
  • k
    how are you guys handling the routing within the DO?
  • e
    itty-router
  • k
    inside the fetch function, embedding a router in the object (E.g. constructor) or what?
  • v
    Hahaha just rhetorical reasoning, dont mind my blabber😂
  • k
    ignore the dirty GET for create
  • k
    like... that's kinda clean-ish for having a blasted router inside, but it still just feels dirty
  • k
    fetch call is abstracted away, as is initialize and persist functions (to/from storage)
  • g
  • e
    💯 thats very similar to mine 🙂
  • k
    anyone have a clean example of a nested DO like we've been talking about? where the parent keeps track of child instances?
  • i
    Do DO’s support expiring values? I love that about Redis, for temporarily persisting authorization challenges
  • g
  • j
    Are custom routes (using a domain) supported with Durable Objects? I haven’t been able to find anything online about this.
  • g
    Yes.
  • j
    Weird... I can’t seem to get that to work at all.
  • g
    Should work just as normal. 
    zone_id
    and `routes`/`route` in 
    wrangler.toml
    .
  • g
    (Not under the 
    durable_objects
    section.)
  • j
    Oh maybe the difference is I’m using environments. Is that supported?
  • j
    Something I’m doing is not right haha.
  • j
    Trying to get to the bottom of it 😅
  • g
    Should be! You using the custom builds RC?
  • j
    Yeah
  • j
    I can get it to work if I deploy to workers.dev.
  • j
    But it just flat out fails to add the DO namespace to the env object when I deploy using environments & custom routes.
  • j
    My understanding of environments is that they are exactly the same but have the environment name appended to the end.
  • g
    Can you dump your 
    wrangler.toml
    here?
  • j
    So in theory it's probably not environments screwing things up for me.
  • j
    Yeah sure
1...474849...567Latest