sledge
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
Bun installer appears to fail during script launch.
There is an open issue for other folks experiencing other strange symptoms tied to what seems to be the same core issue - CPU emulation. https://github.com/oven-sh/bun/issues/3312
35 replies
Bun installer appears to fail during script launch.
@rubenf Turns out the problem is that bun requires minimum avx instruction set on processor - for simd operations. The virtual CPU provided by my hoster does not support avx - so basically its a does-not-meet-minimum-requirements issue for running bun.
35 replies