Hi guys, has anyone managed to successfully update using the Bitnami 2.5 VM to 2.6? - I’ve raised a case with Bitnami directly as their update instructions were dated - still waiting on an update from them.
Chris
Bitnami automatically supports our latest version a few days after we release it, however we’ve created some patch releases which has delayed it. It should hopefully be available this week.
Yep - However looking at their upgrade instructions Here they no longer work.
Since I’m still waiting for them to rectify their upgrade procedure, I just wondered if anyone had managed to figure out an error free upgrade when using the Bitnami 2.5 appliance.
It still puzzles me how they don’t have a working upgrade procedure, barring backing up the site and spinning up a new VM to restore to 
I’ve got a response back from Bitnami stating that they do not have an upgrade procedure. Instead they recommend installing a new instance of Invoice Ninja 2.6.5 and then migrating the data.
I’ve performed a MySQL dump and have backed up the bitnami directory to gzip. Is a DB restore enough or are there other directories that I should also copy across from my old instance?
Many thanks
It’s important to keep the .env file as it has the APP_KEY value.
If you’re using the documents feature you’ll also need to move them.
Thanks Hilel - I’m performing the following commands for a MySQL dump and restore
mysqldump -u root -p bitnami_invoiceninja > backup.sql
mysql -u root -p bitnami_invoiceninja < backup.sql
I’ll be copying across my signed certificates as well as I enabled SSL and ReWrite. Barring the .env, is there anything else I should be copying?
Gonna get there in the end!
OK - So I span up the Bitnami 2.6.5 on a separate VM. I then performed a MySQL dump on the 2.5.5 VM and performed a restore on the 2.6.5 VM.
I copied across the .env and ensured the permissions were set correctly - All good.
Now If I browse to the new appliance it redirects me to the setup page and I can see all of my previous application settings and the database connection succeeds, however it is prompting me to create a new database as per:-
Invoice Ninja Setup
If you need help you can either post to our support forum with the design you’re using or email us at [email protected].
– Commands to create a MySQL database and user
CREATE SCHEMA ninja DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci;
CREATE USER ‘ninja’@‘localhost’ IDENTIFIED BY ‘ninja’;
GRANT ALL PRIVILEGES ON ninja.* TO ‘ninja’@‘localhost’;
FLUSH PRIVILEGES;
How can I ensure Invoice Ninja uses my restored database? (In the case of Bitnami the DB is called bitnami_invoiceninja)
Thanks
I’m not sure, is it possible the database name has changed?
Finally got everything working. To recap:-
Spin up new Bitnami 2.6.5 VM and configure all the basic settings (IP Addressing etc) - Recommend expanding virtual disk before rollout in ESXi as the disk size is thick provisioned at 17GB.
Perform a MySQL dump mysqldump -u root -p bitnami_invoiceninja > backup.sql
Backup .env file on old VM including any signed SSL certificates (if in use)
Perform a MySQL restore mysql -u root -p bitnami_invoiceninja < backup.sql
Restart Bitnami stack /opt/bitnami/ctlscript.sh restart
Head over to the new URL and it should use the existing database and .env settings. At this point it’ll probably error after logging in with ‘whoops something went wrong’.
Follow the self-host upgrade instructions, ensuring you are running from /opt/bitnami/apps/invoiceninja/htdocs
composer dump-autoload --optimize
php artisan optimize --force
php artisan migrate
php artisan db:seed --class=UpdateSeeder
and finally set APP_CIPHER=rijndael-128 in your .env file.
You should now be able to login and use the upgraded stack.
Thanks for sharing the steps with us!