I have a trac repository available on a local network and need to take a dump of the trac data to be able to access it out of that network.
Can anyone suggest a way to do it ?
I don't think there is a unified command to dump both the trac project and a possible attached svn repo, but for separate dumping, Trac has a hotcopy command and svn a dump command.
Trac Backup - The Trac project
svn dump manual
Good set of answers on serverfault for this topic - https://serverfault.com/questions/6147/how-do-i-backup-my-trac-instalations
Related
I'm searching for the high-level approach. I understand that this questions can be explained platform specific, so that is not what I ask specificaly.
The highest level approach that you can get is this:
Put all the enterprise modules in a folder and put that folder in your addons_path before the community addons. That means addons-path=/path/to/enterprise/addons,/path/to/community/
Keep in mind:
1) Before doing anything absolutely backup your existing database.
2) When you have the enterprise modules in place and the addons-path correctly set up, kill all instances of the server and then run the server with -d your_database_name -u all, so that everything will be loaded properly.
I imported Apache Nutch source code into my local ubuntu installation. I have subversion installed on my eclipse kepler. The sourcecode has several branches and one main project in trunk. I was thinking of specifying this source-code location as my repo location to svn and check out & or commit changes based off of this. However SVN always seem to expect a remote repo location. Is there anyway I can make this dumping ground of apache nutch source code as my repo location for svn?
Thanks
DVCS systems may help, such as git, Hg, etc.
Subversion is a centerized version control system, all workspaces directly connect to center repository.
But DVCS have local repository, before you commit to remote repository, you need commit to local rep first.
I'm an iOS developer looking to better manage the projects I am creating. I've never touched SCM before so I'm not sure which system to use.
I'd like to keep track of changes to the different apps I'm making for my boss, but also have them in a centralised place, and be able to branch off and be working on features separate from the main app and then merge the changes back in when I'm finished. All of this will be done locally (stored on an external hard disk in my office), and once versions are complete I'd like to be able to export a copy without the SCM features to send to my boss.
I've just upgraded to Xcode 4 and noticed Git is built in. I played around with both Subversion and Git, but it sounds like Git is what would fit my needs better. However, it seems to be totally different to Subversion. The Xcode 4 documentation suggests Git is best for lone developers, but that doesn't seem the case. If the git repository is inside your working copy, how on earth do you make branches of it? Where do you send your changes to? Do you copy the entire working directory and use that as your branch?
Just looking for someone to explain in plain english which SCM system would be best for a lone developer to use and any tutorials people may know of to help me understand it.
Thanks for any help!
Go for git!
The repository actually resides in your working directory. There is .git folder which contains all the data about your branches and commits and whatsoever. You can create a bare repository(only the contents of the .git folder) if you like but having both in the same place is nice, especially if you are a single developer who doesn't need distribution.
Branching in git is very easy:
# create the branch
git branch mybranch
# switch to branch
git checkout mybranch
# show branches
git branch
Git does not depend on a server like svn does. You can have distributed development by using remotes but this is not necessary.
If you like to make a copy for your boss without the git files in it do a
git archive branchname --format=zip -o tree.zip
I suggest some reading on git
Git in five minutes
Git Community Book
The Thing About Git
Branching in git is very different from SVN. Branching happens in place, in stead of in another directory.
Read this book and other resources to get a better understanding about how git works
About the centralized server, Git is a decentralized SCM. That means that every clone contains the entire repository, not only the current working directory.
That doesn't mean you can't have a central repository. On the central server you create a bare repository, and on you're local machine you clone from that repository, push and pull from that repository, often through ssh.
can anyone give an detailed procedure on how to
migrate projects from gforge version(4.5) to teamforge version 5.2.0.
Migration includes source repository, bug tracking, wiki and discussions.
is it possible to shift all of them.
What's the best way to handle a situation like this?
Thank
You
Teamforge uses Subversion, so assuming you have commandline access to the server then you can use the svnadmin dump and svnadmin load commands.
You will need to run these commands for each repository.
Some (I don't know which) of the pages and wiki are also stored in subversion repositories, so you may be able to migrate that using the same method.
We have an existing Trac installation for an old bunch of source code, and I'm creating a new Trac installation to support a new bunch of source code. Most of the info we've built up over time in the old Trac installation's wiki is equally relevant for the new Trac wiki.
Is there a quick way to migrate the wiki data from the old Trac to the new Trac?
Trac version = 0.10.4
Use trac-admin <trac-env> wiki dump <some-directory> to dump the wiki pages to a directory, then use trac-admin <new-trac-env> wiki load <some-directory> to load the wiki pages into the new environment.
Note that I don't think this will preserve wiki page history. If you want that, you can copy the database to the new instance and do a resync to the new repository.
I would also recommend upgrading to 0.11 if you can. 0.10 is no longer supported, and 0.12 is due out "soonish".
Disclosure: I'm one of the Trac devs
You should be able to use trac-admin to backup the wikis and then restore them on the other instance.
It's all stored in the database, as far as I can remember. You should just be able to export the data from the old database and into the new one.