Service/blacklist: Difference between revisions
< Service
m →Notes |
m →Notes |
||
| Line 30: | Line 30: | ||
|{{Code|/etc/cron.daily/blacklist}} | |{{Code|/etc/cron.daily/blacklist}} | ||
|- | |- | ||
!scope="row" | | !scope="row" | Config | ||
|{{ | |{{Code|/srv/blacklist/.config/sweets/config}} | ||
|- | |- | ||
|} | |} | ||
Revision as of 11:58, 1 September 2011
Hostnames
- None
Hosted on
Administrative contact
See Sysadmins section.
Sysadmins
For non-emergency calls, preferably send email to the administrative contact.
Notes
| User | blacklist
|
|---|---|
| Home | /srv/blacklist
|
| Cron | /etc/cron.daily/blacklist
|
| Config | /srv/blacklist/.config/sweets/config
|
This is an infra to keep sugar-server-blacklist package up-to-date. The cron task will trigger checking if upstream blacklist was changed, and it it is, new package will be uploaded to https://obs.sugarlabs.org by calling sweets command. The sources of sweets is cloned to blacklist user's home directory.
Upgrade notes
| git | /srv/blacklist/site
|
|---|