3 | | 1. The paths from where I'll be pulling and where I should push: |
4 | | * the `mprsyncup` script uses an svn checkout that goes into the `/var/tmp/macports` path of some Mac OS Forge server to operate; given that we need to host about four services that operate off svn checkouts, maybe we should look into some way of unifying them if possible. If we can't use the same server+path for whatever reason, I need to know where to place the appropriate checkout for "webpush" to operate (akin to mprsyncup's `SVNROOT` variable). |
5 | | * Once `trunk/www` is checked out, we need to sync it's contents with our home within the web server's DocumentRoot directory. I need to know the appropriate server+path of that "home" to also know what tool to use (rsync, rsync over ssh, tar, whatever). |
| 3 | 1. The paths from where I'll be pulling data out of svn and where I should push it: |
| 4 | * the `mprsyncup` script uses an svn checkout that goes into the `/var/tmp/macports` path of some Mac OS Forge server to operate; given that we need to host about four services that operate off svn checkouts, maybe we should look into some way of unifying them if possible. If we can't use the same server+path as `mprsyncup` for whatever reason, I would need to know where to place the appropriate checkout for "webpush" to operate (akin to mprsyncup's `SVNROOT` variable). |
| 5 | * Once `trunk/www` is checked out, we need to sync its contents with our home within the web server's DocumentRoot directory. I need to know the appropriate server+path of that "home" to also know what tool to use (rsync, rsync over ssh, tar, whatever). |