|
(Working on 'Filesystem' section)
|
(→Filesystem)
|
| Line 53: | |||
| == Filesystem == | == Filesystem == | ||
| - | '''KEEP IN MIND THAT ALL THE STEPS LISTED ABOVE ARE ONLY FOR CHANGING THE DATABASE STATES'''. In actuality, no other files are backed up, which leaves your previous build artifacts, codestation artifacts, job logs, test results, etc. at risk. To negate this, it is recommended to backup the entire anthillpro directory filesystem as well so that the filesystem can be restored to the same timeframe as the server. | + | <font size=3>'''KEEP IN MIND THAT ALL THE STEPS LISTED ABOVE ARE ONLY FOR CHANGING THE DATABASE STATES'''</font>. In actuality, no other files are backed up, which leaves your previous build artifacts, codestation artifacts, job logs, test results, etc. at risk. To negate this, it is recommended to backup the entire anthillpro directory filesystem as well so that the filesystem can be restored to the same timeframe as the server. |
| Unfortunately, there are some cases that warrant a server not being able to have its entire filesystem backed up. THe order of precedence on how to continue is thus: | Unfortunately, there are some cases that warrant a server not being able to have its entire filesystem backed up. THe order of precedence on how to continue is thus: | ||
| Line 63: | |||
| ## '''artifacts''' - Where your build artifacts live for each buildlife. | ## '''artifacts''' - Where your build artifacts live for each buildlife. | ||
| ## '''codestation''' - Where your codestation project artifacts live for each codestation buildlife. | ## '''codestation''' - Where your codestation project artifacts live for each codestation buildlife. | ||
| + | ## '''published''' - Where your published reports are stored. | ||
| + | ## '''logs''' - Where your server logs, in addition to job logs, lie. | ||
