From: Alex K <spaceoutlet@gmail.com>
To: git@vger.kernel.org
Subject: git use pattern questions
Date: Mon, 8 Jun 2009 10:06:50 +0100 [thread overview]
Message-ID: <e4a904790906080206t51ee260ve64304d8c1147ebc@mail.gmail.com> (raw)
Hello
I would like to publish a repository on say github but I would still
like to hide sensitive information from a config file which
nevertheless needs to be part of the repo. If it was possible to
publish a single branch then I'd make one especially for github and
publish the config file with something like "your password here"...
Would you know what's the best pattern to publish a repository but
still hide sensitive information such as values of passwords, mysq
port etc..?
Also I have a developpement version of the site and a production
version on another server. Is making a branch for the production
version a good choice? I used to simply rsync the changes from dev to
prod and make the changes in the config file for the production
version. This makes sense because in order for the site to run a mysql
dump and some other data not part of the repo needs to be synced.
Thank you,
Alex
next reply other threads:[~2009-06-08 9:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-08 9:06 Alex K [this message]
2009-06-08 12:29 ` git use pattern questions Jeff King
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e4a904790906080206t51ee260ve64304d8c1147ebc@mail.gmail.com \
--to=spaceoutlet@gmail.com \
--cc=git@vger.kernel.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).