Issue 122794 - www seems to exist only on the live disk
Summary: www seems to exist only on the live disk
Status: CLOSED OBSOLETE
Alias: None
Product: Infrastructure
Classification: Infrastructure
Component: Forums (show other issues)
Version: current
Hardware: Other Linux, all
: P3 Normal (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-21 17:52 UTC by jan iversen
Modified: 2021-05-27 19:14 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description jan iversen 2013-07-21 17:52:40 UTC
I updated /var/www/index.php (seems to be a link) in response to a request from andrea.

I expected to be able to commit the change to svn but it seems the forum changes are not stored in svn. 

Looking in /x1/backups (where rsync collects data for the backup center) showed that only the database is being backed up daily.

The runbook for the vm, does not describe how to restore our changes to the forum www in case of a disk crash



I recommend that:

1) all files changed in www are added to svn:
https://svn.apache.org/repos/infra/infrastructure/trunk/machines/vms/ooo-forums.apache.org

/etc and /var/lib/phpBB is already there.

The advantage of using svn over backup, is 
a) files are static, only changes when the admin does it
b) there are no version history in the backup

2) update the runbook
https://svn.apache.org/repos/infra/infrastructure/trunk/docs/services/ooo-forums2.txt

so that others than the administrator can reestablish the system in case of a crash.

There might be another backup procedure in place (the administrator will know that), if thats the case the runbook should be updated, so new changes are done correctly.

rgds
jan I.
Comment 1 Andrea Pescetti 2013-07-21 19:38:32 UTC
Agreed. Note that for a full backup we need to backup also the images (screenshots) uploaded by users.

I don't know how this will work with versioning, since users can add and delete images.

We might think of a "cumulative versioning" that just adds the new files to SVN. Or we could put the files folder under .svnignore and backup them as we do for the database, so that only the application files (PHP, configuration and small auxiliary files) are versioned and the rest has a normal backup.
Comment 2 jan iversen 2013-07-21 20:25:07 UTC
how to make the file structure is of course something the admin decides.

When the images are dynamic, they belong in the backup, not svn.

But I advice against using .svnignore, it can have side effects (like a php script browsing the directory). It also makes it more difficult to understand the setup (mixture of backup and svn)

On mwiki, dynamic mediafiles are stored in a directory parallel to www and part of backup, while www is done static.
Comment 3 Marcus 2021-05-27 19:13:35 UTC
Outdated issue.