Mercurial > p > roundup > code

comparison website/README.txt @ 5941:29d428927362

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
prep for 2.0.0alpha0 release. Initial set of changes for the release. Still a few files to change.
author John Rouillard <rouilj@ieee.org>
date Tue, 22 Oct 2019 14:30:52 -0400
parents e338969b1d23
children 728a8a25dd70
comparison
equal deleted inserted replaced
5940:459426a8c61e 5941:29d428927362
1 Roundup has three web sites: 1 Roundup has three web sites:
2 2
3 * http://www.roundup-tracker.org/ 3 * http://www.roundup-tracker.org/
4 * http://wiki.roundup-tracker.org/ 4 * https://wiki.roundup-tracker.org/
5 * https://issues.roundup-tracker.org/ 5 * https://issues.roundup-tracker.org/
6 6
7 www and wiki are hosted on SourceForge. 7 www and wiki are hosted on SourceForge.
8 8
9 9
10 updating issues.roundup-tracker.org 10 updating issues.roundup-tracker.org
11 =================================== 11 ===================================
12 If you don't have access, ask to update on mailing list. You may try to 12 See doc/developers.txt for details on accessing the new location.
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 13
31 14
32 updating services hosted on sf.net (www and wiki) 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)
33 ================================================= 42 =================================================
34 Generic SF instructions for web service recommend 43 Generic SF instructions for web service recommend
35 uploading files through SFTP, described here: 44 uploading files through SFTP, described here:
36 http://sourceforge.net/p/forge/documentation/Project%20Web%20Services/ 45 http://sourceforge.net/p/forge/documentation/Project%20Web%20Services/
37 46
77 When done working in the sf shell, you can destroy it early 86 When done working in the sf shell, you can destroy it early
78 to free resources: 87 to free resources:
79 88
80 shutdown 89 shutdown
81 90
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
98 updating www.roundup-tracker.org 91 updating www.roundup-tracker.org
99 --------------------------------- 92 ---------------------------------
100 Site update requires rebuilding HTML files. For that 93 Site update requires rebuilding HTML files. For that
101 you `sphinx` and `sphinxcontrib-cheeseshop` are required/ 94 you `sphinx` and `sphinxcontrib-cheeseshop` are required/
102 Hopefully, they are already installed into virtualenv, so 95 Hopefully, they are already installed into virtualenv, so
116 # copy legacy html doc to website docs/ dir 109 # copy legacy html doc to website docs/ dir
117 # (in main doc/conf.py this is done automatically) 110 # (in main doc/conf.py this is done automatically)
118 cp -r -p ../../doc/html_extra/* ${project_home}/htdocs/docs/ 111 cp -r -p ../../doc/html_extra/* ${project_home}/htdocs/docs/
119 # or try it with rsync (skip --dry-run when ready) 112 # or try it with rsync (skip --dry-run when ready)
120 #rsync --dry-run -v --checksum --recursive ./html/* ${project_home}/htdocs/ 113 #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.
Roundup Issue Tracker: http://roundup-tracker.org/