Hey 👋

[compact fulcrum]

THANK YOU @spiral meteor

I can try to Go version

looking good

[spiral meteor]

No problem, yarn deploy seems to be working for me.
Can you try updating cloak to the latest version and updating this branch of the todoapp to the latest version?

[compact fulcrum]

yeah, both latest

also I run the cloak from the latest version

alias cloak="go run /absolute/path/to/the/cloak/repo/cmd/cloak"

it's working for the Go version /api

The Go version works! https://tuongaz-dagger-todoapp.netlify.app/ I'll looking at the code now 😄

[spiral meteor]

Hmmm, should be working though

[compact fulcrum]

let me give it another try

[spiral meteor]

Here's what I did:
On dagger/cloak repo
git pull upstream main ; go build ./cmd/cloak
It's not necessary to re-run the alias command.

On dagger/todoapp repo
git checkout cloak-demo-v2-extension ; git pull upstream cloak-demo-v2-extension ; yarn deploy

[compact fulcrum]

I mean I have the alias setup, so it always run with the latest code in the dagger/cloak

They are commits from the cloak and cloak-demo

anyway, i got the Go version working, good enough for me to start digging the code 😄

[spiral meteor]

Yep, have the same git log

[spiral meteor]

Ok! Let me know if you are stuck with something else.

[visual schooner]

I suspect the alias doesn't work when executing the script. The alias relies on your shell, but when you invoke the script and it tries to invoke cloak, it doesn't know about your shell.

I think you may need to just build cloak normally to somewhere in your $PATH, e.g. go build -o /usr/local/bin/cloak /absolute/path/to/the/cloak/repo/cmd/cloak. Sorry about that, I know the docs suggest that alias, but I think it may no longer be a good solution with the way the scripts work now, I'll update it.

[spiral meteor]

I only had the "just works" argument when building with go build ./cmd/cloak 😆 .
Thx for the context