Setting up an SVN server on my EC2 instance (on AWS), is a major
problem whenever we connect svn using key-file(key.pem for AWS).
Here’s my situation:
Here’s my situation:
- I have a micro EC2 instance hosted with Amazon.
- I used a non-standard port for
ssh
access - I have a
pem
file provided by Amazon for access through ssh - I run Ubuntu 14.04 Server on my EC2 instance
- On the client side, I’m running Ububtu 14.04 Desktop
sudo apt-get install -y subversion
Then, on my EC2 instance, I want to create both the directory where
I’ll store repositories, and the subsequently, create the repository
itself. Permissions and ownership are of the utmost importance. This
worked for me:sudo mkdir -p /srv/svn/
sudo chown ubuntu:ubuntu /srv/svn/
svnadmin create /srv/svn/{repo_name}
Mind the {rep_name}
placeholder above
vim /svnrepos/conf/svnserve.confIn that file add these three lines:
anon-access = none auth-access = write password-db = passwdCreate a password file:
vi /svnrepos/conf/passwdIn that file add a line for your user:
# add users in the format : user = password tony = mypassword