3 ms·
Here's the one question/problem I see- How often do you really want to show someone something badly enough that you are willing to block your local dev environ
by seats 15y ago
Here's the one question/problem I see-
How often do you really want to show someone something badly enough that you are willing to block your local dev environment to do so?
I could see it working if you are interactively talking to someone in chat, but over email, often times you could be waiting hours for someone to actually try out what you want them to see. You could certainly get around this by setting up a separate local 'dev-show' environment, but if you are going to all that effort you really could/should just set up a dev version on a vps/cloud server.
If you are talking to someone interactively, chances are they are another dev, which means they really don't need to see your environment running, they should be capable of using their own.
Also, in this thread I really feel people are exaggerating the level of effort to set up a 'showable' environment on a cloud instance. For rails as an example, I can go from server launch to a running app with db in less than 15 minutes (easily) with manual config and I really doubt I'm the exception here. Remember, this is a 'dev' environment still, your apache/nginx config doesn't have to be airtight, it just has to work for the single user you are showing it to (all defaults on everything is going to work at least as well as the built in rails server).
Not to mention the fact that if you aren't thinking about automating deployments yet, it's a really good investment of time and would work just as well for this case.
- bobwaycott 15y agoThe thought of helping a dev run my code in his/her environment, or moving it out via git push/pull to one of my dev servers (a process that takes but a minute or so when I'm being really slow) decreases in attractiveness the longer I have been working on feature/fix X is. Even within our organization, few devs work on the same project, but sometimes I want someone's thoughts/opinions/suggestions. Some of the devs are in the office, some aren't. Whether they are or not, the fact that I am the only one who has been working on feature/fix X for the last couple weeks means another dev is nowhere close to being able to just run my project as quickly as I can show it off. Sometimes I want to be able to help a client see a quick implementation of something in a local clone of their live site to show them that their suggestion for feature/fix X isn't such a great idea (like I tried to tell them when they asked for it). I want to block my development when needing to show something off for as short a period as possible. The time & friction of firing off `show` (or whatever local variant I might be using, like any of the others mentioned in these comments (e.g., localtunnel)), is close to zero. This is time & friction to me, not them. No matter what process I follow, all they have to do is click a URL. Showoff offers me the shortest path from A to B.