Mercurial > p > roundup > code
comparison website/README.txt @ 8166:53da2c697fab
update instruction on care and feeding for tracker.
| author | John Rouillard <rouilj@ieee.org> |
|---|---|
| date | Wed, 20 Nov 2024 16:09:17 -0500 |
| parents | bea4a6956c89 |
| children | 9489ea677a61 |
comparison
equal
deleted
inserted
replaced
| 8158:9fe279eef724 | 8166:53da2c697fab |
|---|---|
| 122 Roundup is run using gunicorn and wsgi. | 122 Roundup is run using gunicorn and wsgi. |
| 123 | 123 |
| 124 You have 'sudo -u roundup' access if you need to run things as the | 124 You have 'sudo -u roundup' access if you need to run things as the |
| 125 roundup user. | 125 roundup user. |
| 126 | 126 |
| 127 The configuration is in the "website/issues" section of Roundup's | 127 The configuration is tracked in multiple places. |
| 128 Mercurical SCM repository and copied manually to the live tracker. | 128 The one used by PSF infrastrcuture is: |
| 129 | |
| 130 https://github.com/psf/bpo-tracker-roundup | |
| 131 | |
| 132 Contact ee-durbin (or psf infra) for an invite to their repo. | |
| 133 | |
| 134 Usually testing is done with: the "website/issues" section | |
| 135 of Roundup's Mercurical SCM repository and copied manually to the live | |
| 136 tracker. | |
| 129 | 137 |
| 130 * get a working copy of roundup/website/issues from the SCM, either via | 138 * get a working copy of roundup/website/issues from the SCM, either via |
| 131 hg clone https://hg.code.sf.net/p/roundup/code | 139 hg clone https://hg.code.sf.net/p/roundup/code |
| 132 or download a snapshot: | 140 or download a snapshot: |
| 133 https://sourceforge.net/p/roundup/code/ci/default/tarball | 141 https://sourceforge.net/p/roundup/code/ci/default/tarball |
| 134 | 142 |
| 135 * check the differences | 143 * check the differences |
| 136 diff -ur /srv/roundup/trackers/roundup/ roundup/website/issues/ | 144 diff -ur /srv/roundup/trackers/roundup/ roundup/website/issues/ |
| 137 | 145 |
| 138 Copy differences using 'sudo -u roundup ...'. | 146 Copy differences using 'sudo -u roundup ...' into production for testing. |
| 147 | |
| 148 Restart the server with: | |
| 149 | |
| 150 sudo service roundup-roundup restart | |
| 151 | |
| 152 The git version is what PSF uses if they have to rebuild/move our | |
| 153 tracker. So it's important to keep it up to date. | |
| 154 | |
| 155 They also generate the config.ini from an ansible script. So if you | |
| 156 need to change settings in config.ini (e.g. logging from ERROR to | |
| 157 WARNING) and have it persist across (daily+) ansible runs you need to | |
| 158 update: | |
| 159 | |
| 160 pillar/base/bugs.sls | |
| 161 | |
| 162 in the https://github.com/python/psf-salt repo and then push it. | |
| 139 | 163 |
| 140 Getting a user account | 164 Getting a user account |
| 141 ~~~~~~~~~~~~~~~~~~~~~~ | 165 ~~~~~~~~~~~~~~~~~~~~~~ |
| 142 | 166 |
| 143 To get access to the host, submit a pull request for: | 167 To get access to the host, submit a pull request for: |