TortoiseSVN for Windows has a nice feature where you can put files on an
ignore-list. Those files are still under version control (and can be
removed from the ignore-list any time) but as long as they are on the
ignore-list they'll not be part of a commit.
Something similar would be awesome. Or simply checkboxes in front of
each changed file that let you decide if the file should be part of the
commit or not.
David
Am 23.09.2011 18:51, schrieb Mike Combs:
I'm building sites in ExppressionEngine and had the same problem. I
find making my config file detect whether it's running locally or on
the live site, and make the necessary username and other adjustments
has worked really well.
I exclude the db from version control, but periodically I dump the
live db to my local/dev site and import it so I'm testing against
current data. I have the db dump under version control.
It depends on how your situation, of course.
--
Sent from my smartphone with really tiny keys. Please excuse my
brevity and typos.
----- Reply message -----
From: "Dan Bryant" <[email protected]>
To: <[email protected]>
Subject: Remove from version control
Date: Fri, Sep 23, 2011 12:52 am
Alexa,
database.php => I fought with this one for awhile before I gave up and
decided to mirror the remote site database configuration on my
workstation; uname and pass are identical for all environments.
As for config.php you could use getcwd() and a switch statement. Like:
switch (getcwd()) {
// Running on Dan's workstation.
case '/path/to/docroot/on/dans/workstation':
$config['Tasks.siteBasePath'] = 'http://localhost/';
Configure::load('setting/main.dev');
break;
// Running on an unknown system. assume live site
default:
$config['Tasks.siteBasePath'] = 'http://example.com/';
Configure::load('setting/main_live');
break;
}
OR ... if you still want to fight with the config files you can do this:
1) make a copy of the database.php and config.php files (which will
not be tracked by svn)
2) using Versions.app delete the originals (right click the file ->
delete)
3) do this: http://cl.ly/2Q252Y0Q072o1P2T2r3D
4) rename the files to their original filenames: database.php and
config.php ... at which point svn/versions will pretend that the files
don't exist.
I know this seems like a lot of trouble but if you don't do #1 and #2
then Versions.app/svn will completely ignore your svn:ignore (#3)
Good Luck.
-Dan
On Sep 18, 2011, at 2:43 PM, Alexa Dagostino wrote:
I have two files that I want to remove from version control. (the
database.php and config.php file will be different from the local to
my repository). Is this possible?
--
You received this message because you are subscribed to the Google
Groups "Versions" group.
To post to this group, send email to [email protected]
<mailto:[email protected]>.
To unsubscribe from this group, send email to
[email protected]
<mailto:[email protected]>.
For more options, visit this group at
http://groups.google.com/group/versions?hl=en.
--
You received this message because you are subscribed to the Google
Groups "Versions" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/versions?hl=en.
--
You received this message because you are subscribed to the Google
Groups "Versions" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/versions?hl=en.
--
You received this message because you are subscribed to the Google Groups
"Versions" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/versions?hl=en.
