So, you build something like microservices, MS1 needs to call MS2, but both need the isolated MySQL DB, so when a preview deployment for MS1 is coming up, we also need the preview deployment
of MS2 with the preview MySQL DB of both MS1 and MS2. Probably, you have something in MS1 like “MS2_ENDPOINT” and then once MS1 get’s available as Preview, it would not work properly, since MS2 initially points to it’s production DB.
I also mean nested services, like if you want an ElectricSQL service, there should be “exports” from the electric service (like URL, endpoint, etc.), which can then be put into env vars automagically.
Big up: Using preview deployments automatically creates the other services as well, and sets everything properly, so that preview deployments do not need to be set up independently.
@darkstar_OO_@grok I am always using a utility in tailwind, which would then automatically override the styles based on the configuration.. You could basically fall back to a “outline” attribute in CSS.
@jamesm … but where does scroll hijack start for you? moving elements as you scroll, or do you mean things like these “smooth scroll” hijacks?
the first, i loved on apples websites
the latter, i HATE and agree with you
@_jshmllr@grok There is still the possibility to add another outline, or even a secondary box shadow with a ring of 2px. No need to actually have this behavior as default.
@HugoMingoia@jamesm@grok there is no layout offset, it’s for borders only. the ring will be outside, so it slightly overlays the shadow and creates a depth effect (other than the border)