Best Free Repository

There are 5 Best  Free Repository

With so many available hosts offering so many different features, how do you ascertain the right one for your needs and projects? To help developers in their quest to archive and organize their source code, we have compiled a list of the source code repository hosts that we think are top notch. We have searched far and wide to bring you the best hosts; we looked for those that are tailored to the most common forms of code and offer code review, issue trackers, patches, bug reports, and other tools that developers find most useful and necessary when coding. Our top source code repository hosts are listed here, in no particular order:
 

1. Bit Bucket

 Key Features:

• Built with small teams in mind, so you can consolidate sure management, invite members, and share repositories
• Review changes on a fork or branch easily with pull requests
• In-line comments allow users to have discussions within the source code
• Track every commit to an issue in JIRA
• 5 users: FREE
•  

2.  Project Locker

Key Features:

• Fine-grained directory-based permissions (Subversion)
• Automatic backups of your data
• Web-based management console for managing users
• Remote deployments
• Automated import from external repositories or export files
• FREE – 1 user, 1 project, 50 MB storage
•  

3. Cloud Forge

Key Features:

• Instantly provision, integrate, and manage your development tools
• Elastically scale your teams, projects, and processes
• Create, rank, assign, and track issues with the TeamForge tracker
• Integrate your tools, including JIRA, Basecamp, Lighthouse, ZenDesk, and more
• Cost: FREE trials for 30 days

4. Github

Key Features:

• Review changes, comment on lines of code, report issues, and plan with discussion tools
• Use organization accounts to communicate easily with teams
• Integration with several applications and tools
• Field-tested tools for any project, public or private
• Integrated issue tracking
• Every GitHub repository is also a Subversion repository
• Use your go-to SVN tools to checkout, branch, and commit to GitHub repositories

5. Sourceforge

Key Features:

• Integrated issue tracking
• Threaded discussion forums
• Host code with git, Mercurial (hg), or Subversion (svn)
• Browser-based code browsing
• Forking and merge requests with git and hg
• View commit history as a graph
• cost = free

==>>

Repository Maintenance Administration Tools

Repository Maintenance

Maintaining a Subversion repository can be daunting, mostly due to the complexities inherent in systems which have a database backend. Doing the task well is all about knowing the tools—what they are, when to use them, and how to use them. This section will introduce you to the repository administration tools provided by Subversion, and how to wield them to accomplish tasks such as repository data migration, upgrades, backups and cleanups.

An Administrator's Toolkit

Subversion provides a handful of utilities useful for creating, inspecting, modifying and repairing your repository. Let's look more closely at each of those tools. Afterward, we'll briefly examine some of the utilities included in the Berkeley DB distribution that provide functionality specific to your repository's database backend not otherwise provided by Subversion's own tools.

svnadmin

The svnadmin program is the repository administrator's best friend. Besides providing the ability to create Subversion repositories, this program allows you to perform several maintenance operations on those repositories. The syntax of svnadmin is similar to that of other Subversion command-line programs:

We've already mentioned svnadmin's create subcommand (see the section called “Creating the Repository”). Most of the others we will cover later in this chapter. And you can consult the section called “svnadmin” for a full rundown of subcommands and what each of them offers.

svnlook

svnlook is a tool provided by Subversion for examining the various revisions and transactions (which are revisions in-the-making) in a repository. No part of this program attempts to change the repository. svnlook is typically used by the repository hooks for reporting the changes that are about to be committed (in the case of the pre-commit hook) or that were just committed (in the case of the post-commit hook) to the repository. A repository administrator may use this tool for diagnostic purposes.

svndumpfilter

While it won't be the most commonly used tool at the administrator's disposal, svndumpfilter provides a very particular brand of useful functionality—the ability to quickly and easily modify streams of Subversion repository history data by acting as a path-based filter.

svnsync

The svnsync program, which is new to the 1.4 release of Subversion, provides all the functionality required for maintaining a read-only mirror of a Subversion repository. The program really has one job—to transfer one repository's versioned history into another repository. And while there are few ways to do that, its primary strength is that it can operate remotely—the “source” and “sink” ^[32] repositories may be on different computers from each other and from svnsync itself.

Berkeley DB Utilities

If you're using a Berkeley DB repository, then all of your versioned filesystem's structure and data live in a set of database tables within the db/ subdirectory of your repository. This subdirectory is a regular Berkeley DB environment directory, and can therefore be used in conjunction with any of the Berkeley database tools, typically provided as part of the Berkeley DB distribution.
For day-to-day Subversion use, these tools are unnecessary. Most of the functionality typically needed for Subversion repositories has been duplicated in the svnadmin tool. For example, svnadmin list-unused-dblogs and svnadmin list-dblogs perform a subset of what is provided by the Berkeley db_archive command, and svnadmin recover reflects the common use cases of the db_recover utility.
However, there are still a few Berkeley DB utilities that you might find useful. The db_dump and db_load programs write and read, respectively, a custom file format which describes the keys and values in a Berkeley DB database. Since Berkeley databases are not portable across machine architectures, this format is a useful way to transfer those databases from machine to machine, irrespective of architecture or operating system. As we describe later in this chapter, you can also use svnadmin dump and svnadmin load for similar purposes, but db_dump and db_load can do certain jobs just as well and much faster. They can also be useful if the experienced Berkeley DB hacker needs to do in-place tweaking of the data in a BDB-backed repository for some reason, which is something Subversion's utilities won't allow. Also, the db_stat utility can provide useful information about the status of your Berkeley DB environment, including detailed statistics about the locking and storage subsystems

==>>

What Is Repository in Information Technology

In information technology, a repository (pronounced ree-PAHZ-ih-tor-i) is a central place in which an aggregation of data is kept and maintained in an organized way, usually in computer storage. The term is from the Latin repositorium, a vessel or chamber in which things can be placed, and it can mean a place where things are collected. Depending on how the term is used, a repository may be directly accessible to users or may be a place from which specific databases, files, or documents are obtained for further relocation or distribution in a network. A repository may be just the aggregation of data itself into some accessible place of storage or it may also imply some ability to selectively extract data. Related terms are data warehouse and data mining.

==>>