sledge
Worker caching weirdness
Well the response headers look pretty much the same from the deno requests as from curl:
Response Headers:
access-control-allow-origin: *
content-type: text/plain
date: Wed, 27 Nov 2024 15:21:36 GMT
expires: Fri Dec 27 13:33:55 2024 GMT
fly-request-id: 01JDQ3DAFZC30W8XJXY9HJGJ6D-sea
kvdb-cache-status: HIT
kvdb-edge-region: sjc
server: Fly/d42d3a7f1 (2024-11-25)
strict-transport-security: max-age=31536000; includeSubDomains; preload
vary: Origin
via: 2 fly.io
x-content-type-options: nosniff
x-frame-options: SAMEORIGIN
x-response-time: 0.490ms
x-xss-protection: 1; mode=block
Got 5 messages
10 replies
Worker caching weirdness
Maybe a bug in the response headers from the KV store?
HTTP/2 200
server: Fly/d42d3a7f1 (2024-11-25)
date: Wed, 27 Nov 2024 15:09:05 GMT
content-type: text/plain
kvdb-edge-region: iad
vary: Accept-Encoding
vary: Origin
access-control-allow-origin: *
expires: Fri Dec 27 14:01:15 2024 GMT
strict-transport-security: max-age=31536000; includeSubDomains; preload
x-content-type-options: nosniff
x-frame-options: SAMEORIGIN
x-response-time: 0.467ms
x-xss-protection: 1; mode=block
kvdb-cache-status: HIT
via: 2 fly.io
fly-request-id: 01JDQ2PCK6MXMMG9KAP8ZJAQJ2-iad
This is what I see from curl.
10 replies
Migrating content to another Windmill instance
Ok - problem was my app API URL was configurable and when I dropped in the URL for the new server I forgot to include the /api/w/workspace-name portion and Windmill was returning a different set of CORS headers therefore (for invalid routes). The confusing thing was that the browser dev tools said the server was "Caddy" - so I thought I had a caddy server problem. I suppose it says that because I'm using the Caddy reverse proxy.
8 replies
Migrating content to another Windmill instance
Yes, seems to have worked. Unfortunately this instance seems to have some other issues. On mine I did not have to do anything with CORS. I'm able to access it without issue by name - on my tailscale network, from my browser app. However, this new instance that my client setup is failing due to CORS issues. So I need to figure that out before I can confirm that the wmill sync pull / push worked.
8 replies
Migrating content to another Windmill instance
So @rubenf I have a bunch of scripts in my locally running WM instance that I also have synced to a local folder via wmill sync pull and pushed to a git repo (not using windmill git sync). My client now has their instance of WM up and running and I want to migrate all of the scripts. You mention that the cli sync is able to do 99% of that ... do I just need to create a new workspace on the new instance then do a wmill sync push from the git cloned folder after logging into the new workspace with cli?
8 replies
Staying in sync
Same way - you make your changes in the dev workspace, via UI or local and keep local synced via wmill cli. Once you're ready you git commit + push that local folder to branch in git, PR it, then merge into prod branch which would have a job that would wmill sync it to prod workspace.
18 replies