Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.
Start your free trialAndrew McCormick
17,730 PointsDeployHQ vs FTP
So we've been working with BitBucket and loving it. Great. Version control and remote repository decision made, we can check that off the workflow list.
Next step is obviously deploying the code. Initially I think, open FIlezilla, upload, BAM. However I see flashy things like DeployHQ and Beanstalk. Which leads me to the question, why use a service like this, instead of straight up FTP?
1 Answer
Chris Malcolm
2,909 Pointsif you deploy from a service, its usually combined with your remote repo, meaning it will check for changes and only sync those up. SO if you make quite a bit of changes to your web app, you don't have to manually pick and upload your changed files--its synonymous with your version control.
Andrew McCormick
17,730 PointsAndrew McCormick
17,730 Pointsso it really is just a shortcut for doing FTP?
Chris Malcolm
2,909 PointsChris Malcolm
2,909 Pointsits more than a shortcut, there's also a lot of different features that you can also utilize. Multiple ftp deployments are one, another is deploying from a specific branch in your repository.
Andrew McCormick
17,730 PointsAndrew McCormick
17,730 Pointsok. I can see the advantage in that. I especially like the idea of being able to deploy from a branch. thanks.