It should be relatively simple, until issue f3ecce1e is fixed, to have a static copy of the Nitpick issue web UI put on the web for people to see what it looks like. It won't be dynamic, but most of the information is static anyways.
I produce this static copy with two scripts. The first does the mirroring, the second does some sanitation.
sync_issues.sh:
#!/bin/bash
rm -rf issues/*
cd issues
wget -rkE -nH --restrict-file-names=windows http://localhost:18080
find . -name .svn -prune -o -type f -exec ../sync_helper.sh \{\} \;
sync_helper.sh:
#!/bin/bash
cat ${1} | sed 's///g' > ${1}.tmp
mv ${1}.tmp $1
It should be relatively simple, until issue
f3ecce1eis fixed, to have a static copy of the Nitpick issue web UI put on the web for people to see what it looks like. It won't be dynamic, but most of the information is static anyways.Date: 2012-08-22 05:08:50
User: travisb
I've put a slightly sanitized copy at http://travisbrown.ca/projects/nitpick/issues/index.html
Date: 2012-08-30 05:47:05
User: travisb
I produce this static copy with two scripts. The first does the mirroring, the second does some sanitation. sync_issues.sh: #!/bin/bash rm -rf issues/* cd issues wget -rkE -nH --restrict-file-names=windows http://localhost:18080 find . -name .svn -prune -o -type f -exec ../sync_helper.sh \{\} \; sync_helper.sh: #!/bin/bash cat ${1} | sed 's///g' > ${1}.tmp mv ${1}.tmp $1