11Roundup has three web sites:
22
33 * http://www.roundup-tracker.org/
4- * http ://wiki.roundup-tracker.org/
4+ * https ://wiki.roundup-tracker.org/
55 * https://issues.roundup-tracker.org/
66
77www and wiki are hosted on SourceForge.
88
99
1010updating issues.roundup-tracker.org
1111===================================
12- If you don't have access, ask to update on mailing list. You may try to
13- ping Ralf, Bernhard or Ezio directly.
14-
15- * log into issues.roundup-tracker.org
16- * get a working copy of roundup/website/issues from the SCM, either via
17- hg clone http://hg.code.sf.net/p/roundup/code
18- or download a snapshot:
19- http://sourceforge.net/p/roundup/code/ci/default/tarball
20-
21- * check the differences
22- diff -ur /home/roundup/trackers/roundup/ /home/YOURUSERID/roundup/website/issues/
23- * copy the files into the tracker instance, using sudo:
24- sudo -u roundup cp <file> /home/roundup/trackers/roundup/...
25- or use rsync to check and only copy the changed files as user roundup like
26- rsync -rvc /home/YOURUSERID/roundup/website/issues/ trackers/roundup/
27- HINT: old files will not be deleted by this rsync command
28- * restart the roundup server:
29- sudo /etc/init.d/roundup restart
30-
31-
32- updating services hosted on sf.net (www and wiki)
12+ See doc/developers.txt for details on accessing the new location.
13+
14+
15+ updating wiki.roundup-tracker.org
16+ =================================
17+ Wiki isn't hosted on sourceforge anymore. See:
18+
19+ https://issues.roundup-tracker.org/issue2551045
20+
21+ for details on Implementing wiki move to Waldmann-EDV.
22+
23+ Bern Reiter will be adding new docs on how to update files (if
24+ possible). Old directions are:
25+
26+ =============
27+
28+ copy new files over to new directories:
29+
30+ cd ${project_home}/src/roundup/website/wiki
31+ cp -r -p static/roundup ${project_home}/htdocs/_wiki/
32+ cp -p wiki/data/plugin/theme/roundup.py ${project_home}/persistent/wiki/data/plugin/theme/
33+ cd -
34+
35+ If you need to adjust wiki configuration, it is here:
36+
37+ vim persistent/wiki/wikiconfig.py
38+
39+ ==============
40+
41+ updating services hosted on sf.net (www)
3342=================================================
3443Generic SF instructions for web service recommend
3544uploading files through SFTP, described here:
@@ -79,22 +88,6 @@ to free resources:
7988
8089 shutdown
8190
82- updating wiki.roundup-tracker.org
83- ---------------------------------
84- wiki doesn't require building anything, so if you're
85- logged in to SF (see above), just copy new files over
86- to new directories:
87-
88- cd ${project_home}/src/roundup/website/wiki
89- cp -r -p static/roundup ${project_home}/htdocs/_wiki/
90- cp -p wiki/data/plugin/theme/roundup.py ${project_home}/persistent/wiki/data/plugin/theme/
91- cd -
92-
93- If you need to adjust wiki configuration, it is here:
94-
95- vim persistent/wiki/wikiconfig.py
96-
97-
9891updating www.roundup-tracker.org
9992---------------------------------
10093Site update requires rebuilding HTML files. For that
@@ -118,3 +111,21 @@ the whole procedure looks like so:
118111 cp -r -p ../../doc/html_extra/* ${project_home}/htdocs/docs/
119112 # or try it with rsync (skip --dry-run when ready)
120113 #rsync --dry-run -v --checksum --recursive ./html/* ${project_home}/htdocs/
114+
115+
116+ If you are relasing an alpha/beta arelease, don't update:
117+
118+ ${project_home}/htdocs/docs/
119+
120+ instead update:
121+
122+ ${project_home}/htdocs/dev-docs/
123+
124+ and the URL will be: http://www.roundup-tracker.org/dev-docs/docs.html
125+
126+ Note there appears to be a cache somewhere in the path, so you may
127+ need to use:
128+
129+ http://www.roundup-tracker.org/dev-docs/docs.html?foo=1
130+
131+ to cache bust.
0 commit comments