en:doc:basic:backup
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
en:doc:basic:backup [2020/10/04 13:08] – arvid | en:doc:basic:backup [2020/10/04 13:34] (current) – arvid | ||
---|---|---|---|
Line 10: | Line 10: | ||
===== Full Backup ===== | ===== Full Backup ===== | ||
- | This is the easiest way to backup your FlatPress blog: Just copy the whole FlatPress directory from your server. | + | This is the easiest |
- | + | {| | |
- | The big pro of this method is that really | + | |- |
- | Restore can be done without running setup again, and you do not have to consider any changes. | + | ! Scope || Just everything: FlatPress core, themes, plugins, contents. |
- | + | |- | |
- | The disadvantage of this method is expenditure of time. Also, you cannot change installation directory or the author' | + | ! Pro || Restore can be done without running setup again, and you do not have to consider any changes. |
+ | |- | ||
+ | ! Con || Takes the longest | ||
+ | |- | ||
+ | ! Restore || Just copy back to your server, and you're fine. | ||
+ | |} | ||
===== Backing-up user-created contents ===== | ===== Backing-up user-created contents ===== | ||
+ | You may want to backup just the contents of your blog: Entries, static pages, uploaded files, comments, settings. This is useful if you plan to move your blog contents to a freshly installed FlatPress instance, e.g. during an update from really old versions. | ||
- | This method is quite fast, as only the " | + | {| |
- | + | |- | |
- | A disadvantage of this method is that it comprises the " | + | ! Scope || Contents |
+ | |- | ||
+ | ! Pro || Quite fast. | ||
+ | |- | ||
+ | ! Con || Also contains caches which might cause trouble after restore. Does not backup themes or plugins (which you may have edited). It is not possible to change Flatpress installation directory or author name. | ||
+ | |- | ||
+ | ! Restore || Install | ||
+ | |} | ||
===== Individual Backup ===== | ===== Individual Backup ===== | ||
- | |||
This method can only be done manually and is extensive, as a lot of single transfers have to be initiated. Only directories and files that differ from a standard Flatpress installation (i.e. you changed them...) are backed up. | This method can only be done manually and is extensive, as a lot of single transfers have to be initiated. Only directories and files that differ from a standard Flatpress installation (i.e. you changed them...) are backed up. | ||
+ | Use this method if you are an experienced user. Best way is to build an individual backup script doing the work. | ||
- | Main advantage of this method | + | {| |
- | + | |- | |
- | At the price of expenditure of time, you will receive benefits from flexibility. | + | ! Scope || Exactly what you need. |
- | + | |- | |
- | Only the following directories are downloaded: | + | ! Pro || Flexibility in storage and time consumption. Can rebuild your FlatPress contents and settings in any other environment. Following |
+ | |- | ||
+ | ! Con || Experienced users only. An individual backup script doesn' | ||
+ | |- | ||
+ | ! Restore || Install a new FlatPress in your target environment. Copy back all folders from the backup. | ||
+ | |} | ||
+ | Backup what you want to be backed up: | ||
- fp-content/ | - fp-content/ | ||
- fp-content/ | - fp-content/ | ||
Line 41: | Line 59: | ||
- fp-plugins/ | - fp-plugins/ | ||
- | It is very important to include all files, directories and plugins that are not part of the Flatpress standard installation. Following this methot, you can move your blog into different directories, | + | It is very important to include all files, directories and plugins that are not part of the Flatpress standard installation. |
en/doc/basic/backup.1601809706.txt.gz · Last modified: 2020/10/04 13:08 by arvid