3 ms·

Why not pop out an integrated terminal and execute commands there? It's still within the editor and you could have a shell script that runs to deploy.

joshstrange 4y ago
It all comes back to that "development cycle" and wanting to make that as short as possible. What you suggest is absolutely fine, it's just my personal preference (and something that I've seen help other devs) to make the "write code"->"see results" as tight as possible. If you add any delays, any potential chance of forgetting a step, etc then it breaks my programming flow which can kill my productivity.
- mynameisvlad 4y ago
  But aren't you executing a task either way? Either running a script, or executing a command through Ctrl/Cmd+Shift+P, you have to do something to deploy. I mean, hell, just set up gulp/grunt/another task runner to watch your files and run scp if you want it continuously running? Why involve your IDE at all at that point?
  - joshstrange 4y ago
    Ahh, I see the disconnect. I set it up to deploy on save of the file or when the editor loses focus (when it auto-saves). So while you are correct I have to do “something” to make it deploy that “something” is either a hot key or me clicking out of my editor into the browser to refresh the page (talking about PHP here, all my frontend Vue work I do locally with a watch script to rebuild on changes).
    - mynameisvlad 4y ago
      Fair, that's more or less equivalent to a task runner watching the files. I'd recommend that approach only because it decouples the action from the editor. As long as the file changes, it executes.
      - mixmastamyk 4y ago
        I do the same with inotify tools and an alias or makefile. A simple editor like Geany can save on focus change.
- bbkane 4y ago
  I generally make a "run.sh" script or Makefile to build and deploy. Then it's just a few tappity taps in the terminal to run it again. Still not as good as a "play" button, but easier to set up in many cases.

joshstrange 4y ago

It all comes back to that "development cycle" and wanting to make that as short as possible. What you suggest is absolutely fine, it's just my personal preference (and something that I've seen help other devs) to make the "write code"->"see results" as tight as possible. If you add any delays, any potential chance of forgetting a step, etc then it breaks my programming flow which can kill my productivity.

mynameisvlad 4y ago
But aren't you executing a task either way? Either running a script, or executing a command through Ctrl/Cmd+Shift+P, you have to do something to deploy. I mean, hell, just set up gulp/grunt/another task runner to watch your files and run scp if you want it continuously running? Why involve your IDE at all at that point?
- joshstrange 4y ago
  Ahh, I see the disconnect. I set it up to deploy on save of the file or when the editor loses focus (when it auto-saves). So while you are correct I have to do “something” to make it deploy that “something” is either a hot key or me clicking out of my editor into the browser to refresh the page (talking about PHP here, all my frontend Vue work I do locally with a watch script to rebuild on changes).
  - mynameisvlad 4y ago
    Fair, that's more or less equivalent to a task runner watching the files. I'd recommend that approach only because it decouples the action from the editor. As long as the file changes, it executes.
    - mixmastamyk 4y ago
      I do the same with inotify tools and an alias or makefile. A simple editor like Geany can save on focus change.
bbkane 4y ago
I generally make a "run.sh" script or Makefile to build and deploy. Then it's just a few tappity taps in the terminal to run it again. Still not as good as a "play" button, but easier to set up in many cases.