I've been a professional C, Perl, PHP and Python developer.
I'm an ex-sysadmin from the late 20th century.
These days I do more Javascript and CSS and whatnot, and promote UX and accessibility.
A (long) while ago I made burdock which is in my own words, "a cheap python knock-off of dandelion" because I wanted features but didn't know ruby.
I never really used it past the one company where I only had FTP access to their servers, but it's designed to be git-aware and offered a couple of features you might consider in your (much newer and better) app:
dry runs
fake first deployment (only upload metadata file and assume everything's already in place)
Actually, most of the features you mentioned are already supported. Because I just combined existing tools, FTP Deployment and LFTP, it's more like the setting of those tools.
FTP Deployment and LFTP, both support dry runs. Also, fake first deployment is possible with FTP Deployment. But as I mostly want to use it in CI, profiles can be handled via environment variables, which is also safer way than hardcoding credentials into the pipeline config file.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Nice!
A (long) while ago I made burdock which is in my own words, "a cheap python knock-off of dandelion" because I wanted features but didn't know ruby.
I never really used it past the one company where I only had FTP access to their servers, but it's designed to be git-aware and offered a couple of features you might consider in your (much newer and better) app:
Hi, thank you for the comment!
Actually, most of the features you mentioned are already supported. Because I just combined existing tools, FTP Deployment and LFTP, it's more like the setting of those tools.
FTP Deployment and LFTP, both support dry runs. Also, fake first deployment is possible with FTP Deployment. But as I mostly want to use it in CI, profiles can be handled via environment variables, which is also safer way than hardcoding credentials into the pipeline config file.