Home:FERP: Difference between revisions
Jump to navigation
Jump to search
Desheng Fu (talk | contribs) |
Desheng Fu (talk | contribs) |
||
| (18 intermediate revisions by the same user not shown) | |||
| Line 3: | Line 3: | ||
=== Install === | === Install === | ||
=== Update === | === Update & Roll-Back === | ||
To update from an old version to a newer version, you need to | |||
# Backup the system. | |||
# Stop the web server. | |||
# Install the new packages.json. | |||
# Run '''npm run ferp-update''' and follow the instruction. If you're running a very old version, maybe you can't update to the newest version directly. You have to update to a certain version at first. | |||
# Start the web server. | |||
=== Backup & | FERP doesn't support roll-back. You may and should backup your system at first if you want to update to a newer version. In this way, you can restore to the old version if there's any issue. However, you can't roll-back to an old version with the new data. | ||
=== Backup, Restore & Move === | |||
FERP use a central database to store everything. You can use different tools to backup and restore the database. | FERP use a central database to store everything. You can use different tools to backup and restore the database. | ||
| Line 20: | Line 21: | ||
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 | Backup / Restore is a safe way to move a system from one server to another server if and only if the both server are: | ||
# running exact the same FERP version (including all plugins). | |||
# running exact the same database version. | |||
# reachable under the same URL (domain name). | |||
You may have to shutdown the old server before restoring to the new server. You can follow this [[FERP: Change Domain | instruction]] to change domain before or after the movement. | |||
'''WARNING''': | '''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. | |||
=== Cleanup === | === Cleanup === | ||
Latest revision as of 16:15, 11 June 2025
IM (Install & Maintain)
Install
Update & Roll-Back
To update from an old version to a newer version, you need to
- Backup the system.
- Stop the web server.
- Install the new packages.json.
- Run npm run ferp-update and follow the instruction. If you're running a very old version, maybe you can't update to the newest version directly. You have to update to a certain version at first.
- Start the web server.
FERP doesn't support roll-back. You may and should backup your system at first if you want to update to a newer version. In this way, you can restore to the old version if there's any issue. However, you can't roll-back to an old version with the new data.
Backup, Restore & Move
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 server to another server if and only if the both server are:
- running exact the same FERP version (including all plugins).
- running exact the same database version.
- reachable under the same URL (domain name).
You may have to shutdown the old server before restoring to the new server. You can follow this instruction to change domain before or after the movement.
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.