From: Michael Orlitzky <michael@orlitzky.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] {OT} Development framework with access restriction?
Date: Mon, 26 Sep 2011 17:37:10 -0400 [thread overview]
Message-ID: <4E80F086.9010804@orlitzky.com> (raw)
In-Reply-To: <CAN0CFw0fmoaCL4t1AR08S11QZqv5WeSZUhArW3jGAX+AkhfQLQ@mail.gmail.com>
On 09/26/11 16:01, Grant wrote:
> I'd like to hire a freelancer to work on my website. I don't want to
> provide access to all of my code, but instead only the particular file
> or files being worked on. Does anyone know of a development framework
> that would help facilitate that sort of thing? Would no shell access
> along with restricted SFTP access be the simplest, safest, most
> effective way to go?
Why not just send him the stuff he should be working on? He can run his
own Apache/PHP/whatever on his development machine. When he's done, he
can send you a tarball of the site files and maybe a SQL dump if you're
using a database.
That's the easiest one-off solution. If you're looking for something
more permanent, another idea is to have a "public" git repo somewhere
while the developers all work on their own workstations. SQL changes can
be made via numbered migrations, e.g.,
001-create_users_table.sql
002-create_nodes_table.sql
003-disregard_that_drop_users_table.sql
and devs can push everything to the git repo, as long as it's a
fast-forward (so they can't trash the repo history).
Once you're ready to move something live, an admin logs in to the
production box, does a `git pull`, and then runs the migrations or makefile.
next prev parent reply other threads:[~2011-09-26 21:38 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-26 20:01 [gentoo-user] {OT} Development framework with access restriction? Grant
2011-09-26 21:37 ` Michael Orlitzky [this message]
2011-09-27 11:27 ` Mick
2011-09-29 1:18 ` Grant
2011-09-29 2:23 ` Grant
2011-09-29 6:57 ` Jonas de Buhr
2011-09-29 7:32 ` Mick
2011-09-30 23:53 ` Grant
2011-10-01 11:07 ` Florian Philipp
2011-10-01 23:27 ` Grant
2011-10-02 22:41 ` Mick
2011-10-03 22:01 ` Grant
2011-10-03 22:12 ` Michael Mol
2011-09-29 8:13 ` Neil Bothwick
2011-09-29 17:23 ` Michael Orlitzky
2011-09-30 23:59 ` Grant
2011-10-01 0:23 ` Michael Orlitzky
2011-10-01 23:46 ` Grant
2011-10-02 19:04 ` Michael Orlitzky
2011-10-03 21:54 ` Grant
2011-10-03 22:00 ` Michael Mol
2011-10-04 4:25 ` Michael Orlitzky
2011-09-27 12:19 ` Jonas de Buhr
2011-09-29 1:23 ` Grant
2011-09-29 6:43 ` Jonas de Buhr
2011-09-30 23:50 ` Grant
-- strict thread matches above, loose matches on Subject: below --
2011-10-01 5:58 Pandu Poluan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E80F086.9010804@orlitzky.com \
--to=michael@orlitzky.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox