Difference between revisions of "Service/blacklist"
< Service
Jump to navigation
Jump to search
m (→Notes) |
|||
| (One intermediate revision by one other user not shown) | |||
| Line 5: | Line 5: | ||
== Hosted on == | == Hosted on == | ||
| − | [[Machine | + | [[Machine/jita]] |
== Administrative contact == | == Administrative contact == | ||
| 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}} |
|- | |- | ||
|} | |} | ||
Latest revision as of 14:18, 31 January 2012
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
|
|---|