How do you self-host Phanpy and keep it updated?
-
How do you self-host Phanpy and keep it updated?
-
How do you self-host Phanpy and keep it updated?
-
How do you self-host Phanpy and keep it updated?
@cheeaun I'm closest to option 2, I guess.
I have a fork with my config and CI stuff in Forgejo. Locally I track that and your upstream. When there's a new tagged release I check it out locally and merge it in to my fork, at which point CI builds and redeploys to Bunny storage where its served through their CDN.
-
@cheeaun I'm closest to option 2, I guess.
I have a fork with my config and CI stuff in Forgejo. Locally I track that and your upstream. When there's a new tagged release I check it out locally and merge it in to my fork, at which point CI builds and redeploys to Bunny storage where its served through their CDN.
@wq oh that's a nice workflow. I was wondering how is everyone managing their configs. Your workflow also keeps track of config changes which is a plus.
-
@wq oh that's a nice workflow. I was wondering how is everyone managing their configs. Your workflow also keeps track of config changes which is a plus.
@cheeaun though I guess now that I look at it "my config" is really just setting the envvars.
Repo is here in case you'd like you see the Forgejo CI setup.
https://git.vim.wtf/wq/phanpy -
@cheeaun I'm closest to option 2, I guess.
I have a fork with my config and CI stuff in Forgejo. Locally I track that and your upstream. When there's a new tagged release I check it out locally and merge it in to my fork, at which point CI builds and redeploys to Bunny storage where its served through their CDN.
-
How do you self-host Phanpy and keep it updated?
@cheeaun I get it from releases automatically via the github CLI
-
A alsternerd@akkoma.alster.space shared this topic
