Home:FERP: Difference between revisions
Jump to navigation
Jump to search
Desheng Fu (talk | contribs) No edit summary |
Desheng Fu (talk | contribs) |
||
| Line 20: | Line 20: | ||
Depending on your requirements, maybe you also want to backup the global configuration file '''config.json'''. | Depending on your requirements, maybe you also want to backup the global configuration file '''config.json'''. | ||
Backup / Restore is a safe way to move a system from one to server to another server if and only if: | Backup / Restore is a safe way to move a system from one to server to another server if and only if the old and the new server are: | ||
# | # running exact the same FERP version (including all plugins). | ||
# | # running exact the same database version. | ||
# | # reachable under the same URL (domain name). | ||
'''WARNING''': | '''WARNING''': | ||
Revision as of 15:56, 11 June 2025
IM (Install & Maintain)
Install
Update
Please follow the following instruction to update . 1. Backup the database. 2. Stop the web server so that no transition. 2. Update the packages.json npm. 3. FERP provides Template:Code 5. Start the web server again.
It's notable that if your current version is too old, maybe you're not allowed to update to the newest version directly. may have to update to a certain version at first
Backup & Restore
FERP use a central database to store everything. You can use different tools to backup and restore the database.
Depending on your requirements, maybe you also want to backup the global configuration file config.json.
Backup / Restore is a safe way to move a system from one to server to another server if and only if the old and the new server are:
- running exact the same FERP version (including all plugins).
- running exact the same database version.
- reachable under the same URL (domain name).
WARNING:
- Both the database and the configuration file contain sensitive data. Never store or transmit them in an insecure way.
- Always verify the source of the data before restoring the system.