Transcript Shared Document Management using TortoiseSVN

Dedi Rahmawan Putra
97599007
 Shared
Document
 Conventional Ways
 Common Problems
 What is TortoiseSVN
 Advantages over another tools
 Basic Concepts
 Repository
 Checkout
 Daily Uses
 References
 Do
you work in team and share the same
documents?
 Do you work on the same working copy
of documents on different place?
 Removable
Storage
 Remote Desktop
 Folder sharing
 File Server (FTP)
 The
latest update is in removable
storage.
 Only good for individual usage.
 Losing it might lose recently updated
files.
 Hard to synchronize back-up working
copy between clients or users.
• Duplication may exist.
• Newer version may replace older version even
the older one has better contents.
 Latest
working copy is in the target
PC/NB of Remote Desktop.
 Only good for personal usage.
 Cannot continue working when the target
is down.
 Back up working copy might not be the
latest update.
 The
latest working copy is in file server.
 Applicable for many clients or users.
 Stop working while the server is down.
 It is possible to work on back up copy.
However any change you made might be
lost if you don’t notice others.
 For
local network:
• Small coverage area.
 For
Internet:
• The same problem as in FTP server.
 Someone
else was working on the same
file at the same time you worked on it.
Would he/she or you lose the change?
 You want to revert the changes one has
made.
 Can you track down when and who put
any changes to the file?
A
free open-source client for Subversion
version control system.
 Manages files and directories over time.
Files are stored in a central repository.
 Remembers every change ever made to
the files and directories and can recover
older versions.
 Examines the history of how and when
your data changed, and who changed it.
Client
Client
PC Server
Working
Copy
Working
Copy
Working
Copy
Working Copy
R/WR
Working
Copy
Client
Working
Copy
REPOSITORY
R/WR
Working
Copy
Server
R/WR
R/WR
Working
Copy
Client
 The
latest working copy is in the repository
and clients (using update command).
 Allows offline work even when repository
server is down.
 Confirm conflicted documents and can
merge them (text files only).
 Can revert back any files into their older
version.
 Integrated with Windows Explorer.
 Accessible repository with URLs.
Schema
Access Method
file://
Direct repository access on local or network drive.
http://
Access via WebDAV protocol to Subversion-aware
Apache server.
https://
Same as http://, but with SSL encryption.
svn://
Unauthenticated TCP/IP access via custom
protocol to a svnserve server.
svn+ssh://
authenticated, encrypted TCP/IP access via
custom protocol to a svnserve server.
 A central store of data
 Stores information in the
form of a file
system tree - a typical hierarchy of files and
directories.
 Any number of clients connect to the
repository, and then read or write to the
files.
 A kind of file server, but remembers every
change ever written to it: addition, deletion,
and rearrangement of files /directories.
 The client has the ability to view previous
states of the file system.
 May
cause administrative problems.
 May cause unnecessary serialization.
 May create a false sense of security.

Subversion, CVS, and some others use a copy-modify-merge model.
 Prerequisite:
• A PC server to maintain the repository
 Installation Files:
• TortoiseSVN:
http://tortoisesvn.net/downloads
• Subversion:
http://www.collab.net/downloads/subversion
(user: netlab, password: s3cret)
• Apache web server:
http://www.apache.org/dyn/closer.cgi
 Install TortoiseSVN
on a server.
 Create a repository on a server.
 Install Server:
• SVNServer and/or
• ApacheServer
 Install TortoiseSVN
on client(s).
 Do Checkout on an empty folder in client
or server.
 Shared Document Management is ready.
 Creates
folder.
a working copy on a client
 It is vitally important.
 Without the repository
all history is lost
forever.
 The simplest (but not recommended) way is
just to copy the repository folder onto the
backup medium.
 The recommended method is to run:
svnadmin hotcopy path/to/repository
path/to/backup --clean-logs to create a
copy of your repository in a safe manner.
Then backup the copy.
 Lock
file(s)
 Differences with previous version
 Repository Password and Authorization
 Check for Modification
 Revision Graph
 Update to Revision
 Import
 Export
 Relocate Repository
 http://www.tortoisesvn.net
 http://www.collab.net