648
edits
Line 155: | Line 155: | ||
# use another server to pull the data, not the sourceforge master | # use another server to pull the data, not the sourceforge master | ||
terrasync.py --target=/home/joe/fg/scenery --url= http://someserver.org/otherscenery | terrasync.py --target=/home/joe/fg/scenery --url= http://someserver.org/otherscenery | ||
# restrict the area | # restrict the area | ||
terrasync.py --target=/home/joe/fg/scenery --top=49.75 left=18 bottom=49.625 right=18.25 | terrasync.py --target=/home/joe/fg/scenery --top=49.75 --left=18 --bottom=49.625 --right=18.25 | ||
</syntaxhighlight> | |||
Switching between SVN and HTTP terrasync is just a matter of setting a property on startup. Setting <code>--prop:string:/sim/terrasync/http-server=automatic</code> enables the HTTP repository, not setting the property will lead to using the SVN repository. The code seems to be robust enough that one may switch back and forth between the repositories without loosing data.<ref>{{cite web | Switching between SVN and HTTP terrasync is just a matter of setting a property on startup. Setting <code>--prop:string:/sim/terrasync/http-server=automatic</code> enables the HTTP repository, not setting the property will lead to using the SVN repository. The code seems to be robust enough that one may switch back and forth between the repositories without loosing data.<ref>{{cite web |
edits