Skip to content

Commit c64f687

Browse files
rouiljrouilj
committed
Moved roundup-tracker.org infrastructure docs to website/README.txt
This change makes developers.txt as the place for people contributing to the code base and README.txt to those maintaining the infrastructure. The old state was website/README.txt had reference to doc/developers.txt for updating issues.roundup-tracker.org. Removed reference and move docs to website/README.txt. doc/developers.txt had a section on updating website and wiki that referenced website/README.txt. Removed section, replaced with sentence that references website/README.txt for all infrastructure.
1 parent ecdc9a6 commit c64f687

File tree

2 files changed

+81
-92
lines changed

2 files changed

+81
-92
lines changed

‎doc/developers.txt‎

Lines changed: 4 additions & 61 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,10 @@ Contents
1212
.. contents::
1313
:local:
1414

15+
If you are looking for info on managing the roundup-tracker.org
16+
infrastructure, that information has migrated to website/README.txt
17+
in the roundup repo.
18+
1519
Getting Started
1620
---------------
1721

@@ -25,67 +29,6 @@ All development is coordinated through two resources:
2529
- The issue tracker running at
2630
https://issues.roundup-tracker.org/
2731

28-
Website, wiki
29-
-------------
30-
31-
The website is in our repository, so is the configuration of the wiki.
32-
Please check the README.txt in the "website" subdirectory
33-
of a current checkout.
34-
35-
Issue Tracker
36-
-------------
37-
38-
The tracker resides on bugs.ams1.psf.io (188.166.48.69). You can also
39-
ssh to issues.roundup-tracker.org. They have the same fingerprint:
40-
41-
ED25519 key fingerprint is f1:f7:3d:bf:3b:01:8d:e1:4e:30:b3:0f:6e:98:b8:9b.
42-
43-
The roundup installation belongs to the user roundup.
44-
The setup uses virtualenv. Use the python version:
45-
46-
/srv/roundup/env/bin/python2.7
47-
48-
to get a python with roundup on the PYTHONPATH.
49-
50-
The Roundup tracker https://issues.roundup-tracker.org/ is in
51-
/srv/roundup/trackers/roundup/ with the database set to
52-
/srv/roundup/data/roundup/. Note that postgres is used for the
53-
backend, so the database directory above is used for msgs and files.
54-
55-
Source is in: /srv/roundup/src/
56-
57-
Roundup is run using gunicorn and wsgi.
58-
59-
You have 'sudo -u roundup' access if you need to run things as the
60-
roundup user.
61-
62-
The configuration is in the "website/issues" section of Roundup's
63-
Mercurical SCM repository and copied manually to the live tracker.
64-
65-
* get a working copy of roundup/website/issues from the SCM, either via
66-
hg clone https://hg.code.sf.net/p/roundup/code
67-
or download a snapshot:
68-
https://sourceforge.net/p/roundup/code/ci/default/tarball
69-
70-
* check the differences
71-
diff -ur /srv/roundup/trackers/roundup/ roundup/website/issues/
72-
73-
Copy differences using 'sudo -u roundup ...'.
74-
75-
Getting a user account
76-
~~~~~~~~~~~~~~~~~~~~~~
77-
78-
To get access to the host, submit a pull request for:
79-
80-
https://github.com/python/psf-salt
81-
82-
by forking the repo, make a change similar to:
83-
84-
https://github.com/rouilj/psf-salt/commit/2aa55d0fc5a343f45f5507437d3fba077cbaf852
85-
86-
and submit it as a pull request. Contact ewdurbin via #roundup IRC or by
87-
adding an issue to the master psf-salt repo.
88-
8932

9033
Small Changes
9134
-------------

‎website/README.txt‎

Lines changed: 77 additions & 31 deletions
Original file line numberDiff line numberDiff line change
@@ -1,37 +1,11 @@
11
Roundup has three web sites:
22

33
* https://www.roundup-tracker.org/
4-
* https://wiki.roundup-tracker.org/
54
* https://issues.roundup-tracker.org/
5+
* https://wiki.roundup-tracker.org/
66

7-
www and wiki are hosted on SourceForge.
8-
9-
10-
updating issues.roundup-tracker.org
11-
===================================
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-
Contact Thomas Waldmann. Web site: https://www.waldmann-edv.de/
24-
email: info AT waldmann-edv DOT de.
25-
26-
The sites theme is under wiki/wiki/data/plugin/theme/roundup.py. Last
27-
updated by emailing Thomas 2/2021. Images/icons and css under
28-
wiki/_static.
29-
30-
Backups are assumed to be done by Waldmann-edv. There does not appear
31-
to be a way to get access to the underlying filesystem via ssh or to
32-
do a backup/tarball via with web.
33-
34-
==============
7+
www is hosted on SourceForge, issues is hosted on a python software
8+
foundation host and wiki is hosted at waldman-edv.
359

3610
updating services hosted on sf.net (www)
3711
=================================================
@@ -56,8 +30,6 @@ http://web.archive.org/web/20140618231150/http://sourceforge.net/apps/trac/sourc
5630
project_home=/home/project-web/roundup
5731

5832
# pull latest Roundup source with www and wiki
59-
# (the warning about "Not trusting file ... " can be ignored
60-
# for now https://sourceforge.net/p/forge/site-support/8217/)
6133
hg pull -u --cwd ${project_home}/src/roundup
6234
# see below if this fails with: not trusting file
6335
# /home/project-web/roundup/src/roundup/.hg/hgrc from untrusted
@@ -124,3 +96,77 @@ need to use:
12496
https://www.roundup-tracker.org/dev-docs/docs.html?foo=1
12597

12698
to cache bust.
99+
100+
Updating issues.roundup-tracker.org
101+
===================================
102+
103+
The tracker resides on bugs.ams1.psf.io (188.166.48.69). You can also
104+
ssh to issues.roundup-tracker.org. They have the same fingerprint:
105+
106+
ED25519 key fingerprint is f1:f7:3d:bf:3b:01:8d:e1:4e:30:b3:0f:6e:98:b8:9b.
107+
108+
The roundup installation belongs to the user roundup.
109+
The setup uses virtualenv. Use the python version:
110+
111+
/srv/roundup/env/bin/python2.7
112+
113+
to get a python with roundup on the PYTHONPATH.
114+
115+
The Roundup tracker https://issues.roundup-tracker.org/ is in
116+
/srv/roundup/trackers/roundup/ with the database set to
117+
/srv/roundup/data/roundup/. Note that postgres is used for the
118+
backend, so the database directory above is used for msgs and files.
119+
120+
Source is in: /srv/roundup/src/
121+
122+
Roundup is run using gunicorn and wsgi.
123+
124+
You have 'sudo -u roundup' access if you need to run things as the
125+
roundup user.
126+
127+
The configuration is in the "website/issues" section of Roundup's
128+
Mercurical SCM repository and copied manually to the live tracker.
129+
130+
* get a working copy of roundup/website/issues from the SCM, either via
131+
hg clone https://hg.code.sf.net/p/roundup/code
132+
or download a snapshot:
133+
https://sourceforge.net/p/roundup/code/ci/default/tarball
134+
135+
* check the differences
136+
diff -ur /srv/roundup/trackers/roundup/ roundup/website/issues/
137+
138+
Copy differences using 'sudo -u roundup ...'.
139+
140+
Getting a user account
141+
~~~~~~~~~~~~~~~~~~~~~~
142+
143+
To get access to the host, submit a pull request for:
144+
145+
https://github.com/python/psf-salt
146+
147+
by forking the repo, make a change similar to:
148+
149+
https://github.com/rouilj/psf-salt/commit/2aa55d0fc5a343f45f5507437d3fba077cbaf852
150+
151+
and submit it as a pull request. Contact ewdurbin via #roundup IRC or by
152+
adding an issue to the master psf-salt repo.
153+
154+
155+
updating wiki.roundup-tracker.org
156+
=================================
157+
Wiki isn't hosted on sourceforge anymore. See:
158+
159+
https://issues.roundup-tracker.org/issue2551045
160+
161+
for details on Implementing wiki move to Waldmann-EDV.
162+
163+
Contact Thomas Waldmann. Web site: https://www.waldmann-edv.de/
164+
email: info AT waldmann-edv DOT de.
165+
166+
The sites theme is under wiki/wiki/data/plugin/theme/roundup.py. Last
167+
updated by emailing Thomas 2/2021. Images/icons and css under
168+
wiki/_static.
169+
170+
Backups are assumed to be done by Waldmann-edv. There does not appear
171+
to be a way to get access to the underlying filesystem via ssh or to
172+
do a backup/tarball via with web.

0 commit comments

Comments
 (0)