-
Notifications
You must be signed in to change notification settings - Fork 254
Upgrade Instructions
As of FiercePhish v1.2.0, an update script is provided which will guide you through updating your FiercePhish installation.
To upgrade FiercePhish, simply run:
sudo ./update.sh
Changelog can be found here
FIERCEPHISH v1.2.0 IS INCOMPATIBLE WITH PRIOR VERSIONS
If you performed the manual installation method, you will have to update FiercePhish manually. FiercePhish is under constant development and, as such, as constant updates you can pull down to fix bugs or add new features. Below are some instructions to do that.
Back up your data before doing this if it is vital data
-
Be root and move to FiercePhish directory (by default: "/var/www/fiercephish")
sudo su cd /var/www/fiercephish/
-
Put FiercePhish into maintenance mode:
php artisan down
-
Update FiercePhish git repo:
git pull origin master
-
Update composer/bower packages (and install new ones if they exist)
composer install bower install --allow-root
-
Run database migration (if any)
php artisan migrate
-
Refresh workers
php artisan queue:restart
-
Take FiercePhish out of maintenance mode
php artisan up
-
Done!
Check for updates to the Supervisord configuration and its a good idea to check over the manual installation method for any changes you may have to add
If you are getting errors after upgrading, run (warning: this will clear all data in FiercePhish) php artisan migrate:reset
and then php artisan migrate
. Because all the data is cleared, you will have to run php artisan fp:createuser
again to create a new user.
If you are still getting more errors, try completely uninstalling and reinstalling (generally "uninstalling" means killing the VPS running FiercePhish, but you can also just delete "/var/www/fiercephish" and delete the database). If you are still stuck, open a GitHub Issue.
You are able to migrate data from one FiercePhish instance to an updated FiercePhish instance via the Fast Replacement Feature. However data imports are only allowed on patch version numbers, not minor version changes or major version changes. For example: 1.0.0 can be imported to 1.0.5, but 1.0.0 cannot be imported to 1.5.0 or 2.0.0.
-
Delete "/var/www/fiercephish"
-
Delete database "fiercephish"
-
Delete Supervisord configuration file: "/etc/supervisor/conf.d/fiercephish.conf"
-
Delete Apache configuration file: "/etc/apache2/sites-enabled/fiercephish.conf"
-
Restart all services