| 1 |
On Monday 26 Sep 2011 22:37:10 Michael Orlitzky wrote: |
| 2 |
> On 09/26/11 16:01, Grant wrote: |
| 3 |
> > I'd like to hire a freelancer to work on my website. I don't want to |
| 4 |
> > provide access to all of my code, but instead only the particular file |
| 5 |
> > or files being worked on. Does anyone know of a development framework |
| 6 |
> > that would help facilitate that sort of thing? Would no shell access |
| 7 |
> > along with restricted SFTP access be the simplest, safest, most |
| 8 |
> > effective way to go? |
| 9 |
> |
| 10 |
> Why not just send him the stuff he should be working on? He can run his |
| 11 |
> own Apache/PHP/whatever on his development machine. When he's done, he |
| 12 |
> can send you a tarball of the site files and maybe a SQL dump if you're |
| 13 |
> using a database. |
| 14 |
> |
| 15 |
> That's the easiest one-off solution. If you're looking for something |
| 16 |
> more permanent, another idea is to have a "public" git repo somewhere |
| 17 |
> while the developers all work on their own workstations. SQL changes can |
| 18 |
> be made via numbered migrations, e.g., |
| 19 |
> |
| 20 |
> 001-create_users_table.sql |
| 21 |
> 002-create_nodes_table.sql |
| 22 |
> 003-disregard_that_drop_users_table.sql |
| 23 |
> |
| 24 |
> and devs can push everything to the git repo, as long as it's a |
| 25 |
> fast-forward (so they can't trash the repo history). |
| 26 |
> |
| 27 |
> Once you're ready to move something live, an admin logs in to the |
| 28 |
> production box, does a `git pull`, and then runs the migrations or |
| 29 |
> makefile. |
| 30 |
|
| 31 |
Or, create a demo-site (in a subdomain blocked by robots.txt so that your |
| 32 |
google rankings are not messed up) and let him rip. Then diff the live and |
| 33 |
demo files to see what's been changed? The demo can have different passwds |
| 34 |
and what not to ensure access controls as necessary. |
| 35 |
-- |
| 36 |
Regards, |
| 37 |
Mick |
Archives