kenmirrors/firefly-iii
1
0
Fork 0
mirror of https://github.com/firefly-iii/firefly-iii.git synced 2025-10-15 08:35:00 +00:00
Code Issues Projects Releases Wiki Activity

Updated Upgrade instructions (markdown)

James Cole
2015-07-31 07:00:03 +02:00
parent 05c5df84e8
commit d6cc3f5bdf
1 changed files with 8 additions and 31 deletions
Download Patch File Download Diff File Expand all files Collapse all files

39
Upgrade-instructions.md

@@ -1,36 +1,13 @@
## Upgrade 3.3 and higher
Firefly III has had a long and stormy history. Upgrading may prove to be difficult.
1. Run ``composer update --no-dev`` in the root of your project.
So far the most fool-proof way of upgrading I have found is installing Firefly III using a git checkout / composer update routine (see the installation page).
## Upgrade from < 3.3 to 3.3 and higher.
Other methods (recommended by me in the past, mea culpa) will not allow you to update easily.
1. Run ``git pull`` on the root of your Firefly III directory.
2. Run ``composer update``.
3. Run ``php artisan env`` and remember your environment.
4. Run ``php artisan migrate --env=xxxx`` where xxxx is your environment.
5. copy ``.env.example`` to ``.env`` and fill in the details you had in ``app/config/(environment)/*.php``.
## Upgrading
This should successfully upgrade your Firefly III installation from < 3.3 to 3.3. Since this is a framework upgrade this can be pretty intensive. The database remains the same though, so it should be relatively easy.
* Go to the ``firefly-iii`` folder.
* Run ``git pull``
* Run ``php artisan migrate --env=production``
## Upgrade under 3.3
Upgrading Firefly consists of the following:
1. Run ``git pull`` on the root of your Firefly III directory.
2. Run ``composer update``.
3. Run ``php artisan env`` and remember your environment.
4. Run ``php artisan migrate --env=xxxx`` where xxxx is your environment.
Nine times out of ten this will successfully upgrade your installation to the latest version. Common problems include:
### White screen
Check if ``app/storage/logs`` is writeable. If so, follow the errors in the latest log files and open an issue.
### Some migration error
Some queries are pretty complex, and they're built to both change the database and unchange it. Bugs are a common occurrence.
If you run into large red errors when migrating, [create a new issue](https://github.com/JC5/firefly-iii/issues/new).
The easiest fix, sadly, is changing your database manually. Open your favorite SQL editor (phpMyAdmin or something similar) and
That should do it!