3 ms·
> Ever asked yourself why deploying your projects to your servers is such a pain? Personally, no. I haven't heard it from my peers either. I just use rsync and
by frozenkill 12y ago
> Ever asked yourself why deploying your projects to your servers is such a pain?
Personally, no. I haven't heard it from my peers either. I just use rsync and quick scripts; others use PaaS (self-hosted or managed) that generally handles deployment pretty neatly.
The only place I've heard complaints about deployment is inside of large multi-tier organizations, where the problem boiled down to communication issues between dev and ops, not tooling.
I suspect I'm supposed to be the target audience here, but I'm not sure what problem this solves for me. On a first impression this looks mostly like a way to lock myself into a workflow that leaves a lot of unanswered questions (re: server security, platforms/frameworks supported, etc), with very marginal benefits.
- _query 12y ago> I just use rsync and quick scripts How do you handle zero-downtime deployments with rsync? Also what about rollbacks, how do you handle these? In case you have team of a few people, how do you know what already got deployed? How do you know if anyone is deploying just at the moment when you are deploying something? We wanted to solve these questions with our tool. In case you haven't had these problems yourself, I think you aren't our target audience as you pointed out :)