Took 2 hours of reading through examples just to deploy the site.
Turns out, it is hard to do even just the bash stuff when you can't see the container.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 4 points 5 days ago* (last edited 5 days ago) (2 children)

Act works out pretty good but you need to pass it a token and stuff so the actual github CLI bits can work which is kind of a hassle. It took me much too long to discover you need a classic token, the one from the github CLI app gh auth token won't work.

Edit: Ah! Also getting act setup involved getting docker setup which involved me enabling virtualization in my bios for what I swear is like the 4th time I've done so. Also because I'm on Windows (iirc at least) I had to setup WSL or just make a windows container ಠ_ಠ

[–] tyler 3 points 4 days ago

You also need to know what the internal GitHub event json looks like. Using act was such a pain I just gave up. Have tried several times now and it’s just easier to create a second repo just for testing and overwrite it with your current repo anytime you need to do major workflow changes.

[–] [email protected] 3 points 5 days ago

Docker issues are always fun. I've repeatedly ran into docker kubernetes ssl certs being blocked by my ISP because they are dumb. Recently switched ISPs that let let's me actually have that control.