if y'all confused about chute: its basically a git-to-production-ease-of-use-whatever manager to make your job to setup all of your python projects as easy as:

chute add <name> <git url> -b master
chute start

which will clone/fetch the requested repo (if it hasnt done so already), check it out to an internal directory, and then start it according to .chute.yml which specifies some setup commands and then an entrypoint command

its meant to be containers lite, basically "i dont give a shit how this is supposed to be set up, just do it" kinda deal without the whole infrastructure of images in place, its kinda jank as fuck, but its mostly meant as a "i dont care, just do it" attitude i often have to running my stuff on servers

oh yeah, and when pulling (cuz it does that automatically), it stops the container/process, then swaps out the layers (the git "root" layer when an additional "data" layer) to the new commit, and restarts it

Follow

im basically just making it cuz i want to yeet my shitty bots at servers and then never really care about them ever again after that, so i can keep pushing stuff to repositories and the changes will land nicely and automatically in the respective places

in-place CI/CD bois

· · Web · 2 · 0 · 1

@jboi i just do that by using scp and ssh in the CI pipeline

Sign in to participate in the conversation
Fuzzy Systems Masto

Instance run by a non-profit association, with a mission to encourage an open internet, welcoming to everyone.