2,411
edits
Changes
From SME Server
Jump to navigationJump to searchInitial rewording and draft of push configuration steps
=====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:
<ol><li>, but you will need to enable bash as the shell for this user.
<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>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
cat .ssh/pushmirror-*.pub >> .ssh/authorized_keys
cat .ssh/pushmirror-*.pub >> .ssh/authorized_keys
</li></ol>
</li></ol>
=====Configuring for pull=====
=====Configuring for pull=====
We prefer you configure your mirror to be setup as a push mirror, but if you can not do so or have other ways for not doing so you can just schedule a cron job to run every 2 hours that does the exact same sync command you do to get the mirror in the first place, you can add a comment like in the example below:
We prefer you configure your mirror to be setup as a push mirror, but if you can not do so or have other ways for not doing so you can just schedule a cron job to run every 2 hours that does the exact same sync command you do to get the mirror in the first place, you can add a comment like in the example below:
