Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrading help when installing from Softaculous #1962

Closed
TobiasDev opened this issue Jan 2, 2019 · 8 comments
Closed

Upgrading help when installing from Softaculous #1962

TobiasDev opened this issue Jan 2, 2019 · 8 comments

Comments

@TobiasDev
Copy link

I am running Firefly III version 4.7.7

Description
I'm hosting my Firefly Instance through a provider that uses Softaculous, however, they don't have a "upgrade" script for Firefly which means it can't be done automatically (sadly). Is there any way I can upgrade my Firefly instance through Firefly itself? Or that I can grab the files here from Github and upload them into my Firefly folder?

The biggest problem for me is that I'm not sure which files I should not upgrade so my database connection and everything stays the same.

@JC5
Copy link
Member

JC5 commented Jan 2, 2019

I'm sorry, I have no idea what would be the best way to upgrade a softaculous installation. What you can try is to backup your data and install Firefly III (v4.7.9) again, and then point it to the old database. In the .env file, you must replace the APP_KEY with the old one and then the web interface should upgrade itself.

@JC5 JC5 added the question label Jan 2, 2019
@lucavallerini
Copy link
Contributor

I had the same problem and I did what @JC5 said, with an addition: I had to update the database myself since a table changed between version 4.7.8 and 4.7.9.

@TobiasDev
Copy link
Author

I had the same problem and I did what @JC5 said, with an addition: I had to update the database myself since a table changed between version 4.7.8 and 4.7.9.

Sorry, what did you have to do? Because I did get an error when trying to open Firefly after changing the .env file.

@BoGnY
Copy link
Contributor

BoGnY commented Jan 4, 2019

Sorry, what did you have to do? Because I did get an error when trying to open Firefly after changing the .env file.

If you have SSH access to server, you have to run the following commands (from firefly installation directory) to update your database with the latest changes:

php artisan migrate --seed
php artisan firefly:upgrade-database

If you don't have it, you have to go to /database/migrations and open all new file that wasn't be on previous version, then manual apply all changes in your database..
Make this with CAUTION as you have to understand PHP instructions and how this instructions must be applied on database... MAKE A BACKUP FIRST!!!

@TobiasDev
Copy link
Author

It looks like I have Shell, access, so I'm considering just re-installing Firefly myself, through the shell access, because maybe that way it also doesn't get the weird "Public" folder, that it get's when using Softculous. @JC5 Do you think that is possible to do?

@TobiasDev
Copy link
Author

TobiasDev commented Jan 8, 2019

Hello again!

I've been trying to run the two commands @BoGnY wrote, and it only partially works. I can do the first one:

php artisan migrate --seed

However, as soon as I get too the second one I get an error:

In Preference.php line 100:
Could not decrypt preference #5. If this error persists, please run "php artisan cache:clear" on the command line.

I tried running the cache:clear but it didn't help.

Any ideas?

@lucavallerini
Copy link
Contributor

lucavallerini commented Jan 8, 2019

Is the APP_KEY in the .env file correct (the same of your previous installation)?

@TobiasDev
Copy link
Author

Aha... That was what I missed! Sorry, I see that it also says earlier, but for some reason I missed it. Thanks for the help!

@lock lock bot locked as resolved and limited conversation to collaborators Jan 23, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants