Development

I'm looking to get in place a tool chain for development in conjunction with my move to AWS.

Connection

I'm looking at connecting to a file system over ssh. There is this for Windows and sshfs for Linux. This seems more secure than ftp. By mounting it as a file system, I won't have to look for ftp plugins - which I've had trouble finding.

I will have to investigate how to attach the drives. I would like it to be as automated as possible. Setting up a cron on my Linux systems may be best as I'm hesitant to add it to fstab and compromise the boot.

IDE

I like the idea of an IDE. Particularly because I would like to move in the direction of more testing and refactoring. The two big contenders seem to be NetBeans and Eclipse. I think the best thing to do from here is try both of them and see which one works better.

Update: I think I am pretty set against an IDE at this point. I would prefer a toolchain.

BASH Toolchain

Standing in opposition to an IDE would be a more traditional toolchain. In this case, I would connect over SSH, and use Vim as my editor. This would probably give me much tighter control, but I'm afraid I would miss out on things like automated test tools.

Source Control

I'm setup on GitHub but I'm finding that I have a lot of projects I do not want to share and the cost of private account is prohibitive.

I think I'm going to setup a dev server.

Dev Servers

• Git
• Continuous integration

There will not be one dev server - there will be many. Each Dev server has a parent (except the origin). Any check-in to a dev server kicks off the continuous integration. Each dev server can also publish a live build. A publish will always produce a new instance.

For CI I should look at BuildBot and Apache Ant.

http://en.wikipedia.org/wiki/Comparison_of_continuous_integration_software