Welcome to the Treehouse Community

The Treehouse Community is a meeting place for developers, designers, and programmers of all backgrounds and skill levels to get support. Collaborate here on code errors or bugs that you need feedback on, or asking for an extra set of eyes on your latest project. Join thousands of Treehouse students and alumni in the community today. (Note: Only Treehouse students can comment or ask questions, but non-students are welcome to browse our conversations.)

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and a supportive community. Start your free trial today.

General Discussion

Darren Healy
seal-mask
.a{fill-rule:evenodd;}techdegree
Darren Healy
Front End Web Development Techdegree Student 23,565 Points

Help setting up means for client to view website in progress

Hi there,

I have started working on a couple of website projects and it would be great to have the option to allow clients to be able to see the work in progress if I share I link. I know this can be done, but since I'm relatively new to the world of local development I'm not sure how I go about it.

I'm sure there's someway of setting it up given what I have:

  • hosting package
  • mamp (basic version)
  • codekit (novice user)

What options do I have to set something up?

1 Answer

Kevin Korte
Kevin Korte
28,109 Points

I think the free way would be to give each project a subdomain on your website, and than upload it there. With the subdomain, you can have multiple projects under one hosting account, and one price...which is nice. This works okay when you're really small, but doesn't scale well. But that that point you'd know what your options are for better scaling. :)

Kevin Korte
Kevin Korte
28,109 Points

How I would do it at a larger scale is just git push to spin up a new instance of a server, with a temporary domain that get's auto-generated, so as you work on the project with git, you could have a branch that is the staging code to show the client. Any changes you just push to the branch, and it would push to the server, possibly even using a continuous integration tool to help. That obviously adds a layer of complexity, and cost, that is probably not necessary at first.

But at least this way it's automated to the max. The push to server, the new server instance creation, the temp domain name....than when you are done, just destroy the server instance.