comparison website/README.txt @ 5633:7a570b1f0d67

website: improve sf login instructions * Change the diff command to have the old version first. * Move the hint to shutdown the shell earler into the general sf section.
author Bernhard Reiter <bernhard@intevation.de>
date Thu, 07 Mar 2019 09:00:10 +0100
parents da2decb6d0c7
children e338969b1d23
comparison
equal deleted inserted replaced
5632:a29a8dae2095 5633:7a570b1f0d67
37 37
38 However, SFTP is ugly to script in non-interactive 38 However, SFTP is ugly to script in non-interactive
39 mode, so we use SSH access to fetch everything and 39 mode, so we use SSH access to fetch everything and
40 build from server side. 40 build from server side.
41 41
42 logging into sf.net 42 Working with sf.net
43 ------------------- 43 -------------------
44 Current docs are taken down with SourceForge Trac, 44 Current docs are taken down with SourceForge Trac,
45 so working instructions are available from here: 45 so working instructions are available from here:
46 http://web.archive.org/web/20140618231150/http://sourceforge.net/apps/trac/sourceforge/wiki/Shell%20service 46 http://web.archive.org/web/20140618231150/http://sourceforge.net/apps/trac/sourceforge/wiki/Shell%20service
47 47
72 users=110231 72 users=110231
73 73
74 if the uid/gid changes you may have to change the values. 74 if the uid/gid changes you may have to change the values.
75 See: https://www.mercurial-scm.org/wiki/Trust for details 75 See: https://www.mercurial-scm.org/wiki/Trust for details
76 76
77 When done working in the sf shell, you can destroy it early
78 to free resources:
79
80 shutdown
77 81
78 updating wiki.roundup-tracker.org 82 updating wiki.roundup-tracker.org
79 --------------------------------- 83 ---------------------------------
80 wiki doesn't require building anything, so if you're 84 wiki doesn't require building anything, so if you're
81 logged in to SF (see above), just copy new files over 85 logged in to SF (see above), just copy new files over
102 . ${project_home}/docbuilder/bin/activate 106 . ${project_home}/docbuilder/bin/activate
103 # cd to website source and build it 107 # cd to website source and build it
104 cd ${project_home}/src/roundup/website/www 108 cd ${project_home}/src/roundup/website/www
105 make clean 109 make clean
106 make html 110 make html
107 # you can check which files updated 111 # you can check which files updated (the date will change with many files)
108 #diff -qur ./html/ ${project_home}/htdocs/ 112 #diff -ur --brief ${project_home}/htdocs/ ./html/
109 # copy to website dir 113 # copy to website dir
110 cp -r -p ./html/* ${project_home}/htdocs/ 114 cp -r -p ./html/* ${project_home}/htdocs/
111 # copy legacy html doc to website docs/ dir 115 # copy legacy html doc to website docs/ dir
112 # (in main doc/conf.py this is done automatically) 116 # (in main doc/conf.py this is done automatically)
113 cp -r -p ../../doc/html_extra/* ${project_home}/htdocs/docs/ 117 cp -r -p ../../doc/html_extra/* ${project_home}/htdocs/docs/
114 # or try it with rsync (skip --dry-run when ready) 118 # or try it with rsync (skip --dry-run when ready)
115 #rsync --dry-run -v --checksum --recursive ./html/* ${project_home}/htdocs/ 119 #rsync --dry-run -v --checksum --recursive ./html/* ${project_home}/htdocs/
116
117 When done working in the shell, you can destroy it early
118 to free resources:
119
120 shutdown

Roundup Issue Tracker: http://roundup-tracker.org/