4 ms·

> I think it's odd to get hung up on prefixing your commands with "docker-compose exec" or ... We're already doing "bundle exec rails s" or "bundle exec capist

by ClikeX 7y ago

> I think it's odd to get hung up on prefixing your commands with "docker-compose exec" or ... We're already doing "bundle exec rails s" or "bundle exec capistrano production deploy" commands. So a "docker-compose up" shouldn't matter at all. To be fair, I've had frontenders complain that it was hard for them to remember the capistrano deploy commands. And that they'd love a GUI butten for deployments. Rather than just look at our wiki or write it down.

pas 7y ago
It's not like providing a GUI is impossible, a single file python server outputting HTML with buttons would do it. :)
- ClikeX 7y ago
  It's not impossible. But we're a small dev team with several active clients. So most of us are swamped with client work. For the few frontend devs that need to deploy the applications it's way easier for them to just save the command to their notes.
  - pas 7y ago
    Hm. Actual deploys? How about a GitLab CI pipeline with "when: manual" tasks for PROD/LIVE deploy? But, yes, putting the how to deploy into the README.md can be done in 5 seconds whereas setting up a CI/CD pipeline is a lot more effort. So I guess frontend devs just have to be tamed :)