Changes

From SME Server
Jump to navigationJump to search
27 bytes added ,  19:08, 13 July 2011
m
Minor fixes
Line 78: Line 78:  
=====Configuring for push=====
 
=====Configuring for push=====
 
The push system uses private public key pairs for communication, for this you will need to execute some additional configuration steps:
 
The push system uses private public key pairs for communication, for this you will need to execute some additional configuration steps:
<ol><li>First and foremost you will need SSH to be configured and running on your server. If you are using SME Server for your mirror you will have to enable remote access on your server through the server-manager.</li><li>You will also need to enable bash as the shell for this user.</br>If you are running SME Server you can do that like this:
+
<ol><li>First and foremost you will need SSH to be configured and running on your server. If you are using SME Server for your mirror you will have to enable remote access on your server through the server-manager.</li><li>You will also need to enable bash as the shell for this user.<br />If you are running SME Server you can do that like this:
 
  db accounts setprop {user} Shell /bin/bash
 
  db accounts setprop {user} Shell /bin/bash
 
  signal-event user-modify {user}
 
  signal-event user-modify {user}
 
</li><li>You will also have to append the keys to the authorized_keys file of the user
 
</li><li>You will also have to append the keys to the authorized_keys file of the user
 +
su - {user} -s /bin/bash
 
  cat .ssh/pushmirror-*.pub >> .ssh/authorized_keys
 
  cat .ssh/pushmirror-*.pub >> .ssh/authorized_keys
 
</li></ol>
 
</li></ol>

Navigation menu