Make sure the spec, if deployed to a subdir, still works. This means no absolute paths. Is this easy enough to fix? (worst case, switch to using a dev subdomain)
Update deploy.sh script to upload to /dev
Have links in the spec to the dev version and to release version
Perhaps have a release.sh script? It git checkouts (or git pulls in a temp dir) a specified git tag, runs build.sh and deploys to the top-level (but without touching/dev ! Make sure to set rsync to ignore that dir and never write or delete it)
- Make sure the spec, if deployed to a subdir, still works. This means no absolute paths. Is this easy enough to fix? (worst case, switch to using a dev subdomain)
- Update `deploy.sh` script to upload to `/dev`
- Have links in the spec to the dev version and to release version
- Perhaps have a `release.sh` script? It `git checkout`s (or `git pull`s in a temp dir) a specified git tag, runs `build.sh` and deploys to the top-level (but *without touching* `/dev` ! Make sure to set `rsync` to ignore that dir and never write or delete it)
For more details, See #71.
deploy.shscript to upload to/devrelease.shscript? Itgit checkouts (orgit pulls in a temp dir) a specified git tag, runsbuild.shand deploys to the top-level (but without touching/dev! Make sure to setrsyncto ignore that dir and never write or delete it)For more details, See #71.