MacOS development: workplace organization?

Question

macOS

Greetings!
Out of the corner of my ear I heard that when people develop on poppies, they try not to litter the system with tools for development, but spread the tools across virtual machines.
I would like to draw some wisdom about such an organization.
In particular,
- where do you put the IDE,
- the environment (I work on java, but there is no difference from other environments from this point of view),
- VCS working copy (where you download the sources)
- Databases, web servers,
UPD logs This is what I mean I ask. On *niks, when you start to install something from packages, then all this starts to be stuffed into all sorts of /usr/bin, /var/lib, /var/log, /etc/*, etc. I don't want it all to grow

Answer 1

I have virtual machines (VirtualBox), where I have the main deployment.
“Do not clog the system” - completely does not work.
I use homebrew, for perl - perlbrew python through virtualenv
from VCS - git, also delivered through homebrew.
but all the server bases are on virtual machines.
the main rule is this - everything that can be kept on a virtual machine lives there, what cannot be taken out on a virtual machine - we try to put it in home, and minimize the impact on the system (that's why homebrew and not macports)
and native applications for poppy - of course in / applications

Answer 2

IDE and other tools - in Macos, in default places, I don’t see any reason to be smart here (applications in Applications, git from package, documents and projects - in the corresponding sections of the user directory). Server environments for tests, with servers, databases and logs - on the corresponding virtual machines. Deploy to a virtual machine either by autoload from the IDE or by git.

Answer 3

glean? well draw

Answer 4

On a Mac, git, vim, tmux, node, mongodb, erlang, python, etc via homebrew , ruby ​​via rbenv and a couple of mission-critical gems like heroku, pry.
Almost all projects work in virtual machines. Here everything is very simply done through Vagrant . The machines themselves work under VirtualBox, vagrant is just convenient for: quick installation and configuration of ubunta (or another OS), folder sharing settings, provisioning via puppet/chef, easy ssh access to the virtual machine, port forwarding to the host. In addition, it is convenient to use when working in a team. All team members will have enough Vagarntfile to deploy the same virtual machines on their machines.

Answer 5

We deployed a shared Vagrant image for our vagrant.rithis.com team,
but git comes to me with XCode.

Answer 6

nothing on a mac other than XCode and an IDE. Everything else is on a virtual machine with a shared folder.

Answer 7

I don't use IDE, but development is not my main task. And so the working environment on virtual or real servers. On the poppy Coda / CodeRunner and Sequel Pro / Base, well + Transmit and GitHub for uploading junk.

Answer 8

On the Mac, all the tools are vim, Sublime Text 2, Git. I don't use XCode for iOS / Mac OS X development. I use 2 virtual machines (1 Mac OS X and 1 CentOS in Parallels) + one remote (Fedora). On the VM, it's just Git everywhere.