How to upgrade the AWS Marketplace AMI #2937

New Issue

OVERLORD · 2026-02-05T05:47:24+03:00

OVERLORD commented

2026-02-05 05:47:24 +03:00

Originally created by @dzitzels1 on GitHub (Aug 3, 2022).

Attempted Debugging

I have read the debugging page

Searched GitHub Issues

I have searched GitHub for the issue.

Describe the Scenario

The AWS Marketplace AMI is at v21.05.3 and I am running an instance of it. I would like to upgrade my instance to v22.07 but none of the upgrade procedures seem to work. I am reaching out to Intuz who created the image but I am having little luck there.

Is there an existing procedure for this? Document? YouTube video? Anything to help me get through this?

Thanks,

Doug.

Exact BookStack Version

v21.05.3

Log Content

No response

PHP Version

7.4

Hosting Environment

AWS Marketplace AMI (Ubuntu 20.04)

Originally created by @dzitzels1 on GitHub (Aug 3, 2022). ### Attempted Debugging - [X] I have read the debugging page ### Searched GitHub Issues - [X] I have searched GitHub for the issue. ### Describe the Scenario The AWS Marketplace AMI is at v21.05.3 and I am running an instance of it. I would like to upgrade my instance to v22.07 but none of the upgrade procedures seem to work. I am reaching out to Intuz who created the image but I am having little luck there. Is there an existing procedure for this? Document? YouTube video? Anything to help me get through this? Thanks, Doug. ### Exact BookStack Version v21.05.3 ### Log Content _No response_ ### PHP Version 7.4 ### Hosting Environment AWS Marketplace AMI (Ubuntu 20.04)

OVERLORD added the 🐕 Support label 2026-02-05 05:47:24 +03:00

OVERLORD closed this issue

2026-02-05 05:47:26 +03:00

OVERLORD commented

2026-02-05 05:47:31 +03:00

@ssddanbrown commented on GitHub (Aug 3, 2022):

Hi @dzitzels1,

To be honest I have not control or idea of setup for these Intuz instances, and I have called them out before on twitter for being out of date.

Do you have terminal access to these systems?
If so, Does a /var/www/bookstack directory exist and does it contain an artisan file?

@ssddanbrown commented on GitHub (Aug 3, 2022): Hi @dzitzels1, To be honest I have not control or idea of setup for these Intuz instances, and I have called them out before on twitter for being out of date. Do you have terminal access to these systems? If so, Does a `/var/www/bookstack` directory exist and does it contain an `artisan` file?

OVERLORD commented

2026-02-05 05:47:35 +03:00

@dzitzels1 commented on GitHub (Aug 3, 2022):

Yes all the way up to I don’t know about the artisan file. I will need to
check when I get back to my desk.

Thanks for being so quick on the response.

Doug.

On Wed, Aug 3, 2022 at 12:19 Dan Brown @.***> wrote:

Hi @dzitzels1 https://github.com/dzitzels1,

To be honest I have not control or idea of setup for these Intuz
instances, and I have called them out before on twitter for being out of
date.

Do you have terminal access to these systems?
If so, Does a /var/www/bookstack directory exist and does it contain an
artisan file?

—
Reply to this email directly, view it on GitHub
https://github.com/BookStackApp/BookStack/issues/3618#issuecomment-1204318573,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANOUOSQM3XYLWVOQEMT52DDVXKZ2VANCNFSM55PYZRMA
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Doug Zitzelsberger, AWS CCP
(801) 341-9157
@.***

https://www.certmetrics.com/amazon/public/badge.aspx?i=9&t=c&d=2020-01-06&ci=AWS01223108

@dzitzels1 commented on GitHub (Aug 3, 2022): Yes all the way up to I don’t know about the artisan file. I will need to check when I get back to my desk. Thanks for being so quick on the response. Doug. On Wed, Aug 3, 2022 at 12:19 Dan Brown ***@***.***> wrote: > Hi @dzitzels1 <https://github.com/dzitzels1>, > > To be honest I have not control or idea of setup for these Intuz > instances, and I have called them out before on twitter for being out of > date. > > Do you have terminal access to these systems? > If so, Does a /var/www/bookstack directory exist and does it contain an > artisan file? > > — > Reply to this email directly, view it on GitHub > <https://github.com/BookStackApp/BookStack/issues/3618#issuecomment-1204318573>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ANOUOSQM3XYLWVOQEMT52DDVXKZ2VANCNFSM55PYZRMA> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> > -- Doug Zitzelsberger, AWS CCP (801) 341-9157 ***@***.*** https://www.certmetrics.com/amazon/public/badge.aspx?i=9&t=c&d=2020-01-06&ci=AWS01223108

OVERLORD commented

2026-02-05 05:47:38 +03:00

@ssddanbrown commented on GitHub (Aug 3, 2022):

@dzitzels1 Happy to help.

If you do find an artisan file there, it likely means that's the location of your BookStack install.
In that case, you might be able to go into that directory (cd /var/www/bookstack) and run our normal update commands:
https://www.bookstackapp.com/docs/admin/updates/

I'd advise backing up first, so snapshot the instance or whatever options you have in AWS before attempting.
Might need to backup the database aswell if not on the same machine.

If any of the update commands fail, just let me know.
If the composer command fails, don't be tempted to install the composer system package, that often creates more issues.

@ssddanbrown commented on GitHub (Aug 3, 2022): @dzitzels1 Happy to help. If you do find an artisan file there, it likely means that's the location of your BookStack install. In that case, you might be able to go into that directory (`cd /var/www/bookstack`) and run our normal update commands: https://www.bookstackapp.com/docs/admin/updates/ I'd advise backing up first, so snapshot the instance or whatever options you have in AWS before attempting. Might need to backup the database aswell if not on the same machine. If any of the update commands fail, just let me know. If the `composer` command fails, don't be tempted to install the `composer` system package, that often creates more issues.

OVERLORD commented

2026-02-05 05:47:42 +03:00

@dzitzels1 commented on GitHub (Aug 3, 2022):

Hi Dan,

I did find the artisan file in that folder. Fortunately, this is a dev
instance - I have a dev and a prod instance but the prod instance is
roughly identical.
I will try the update commands on my dev instance to see what happens and
where it fails.

I want to get this right on the dev side so the procedure is nice and clean
for the prod side.

I will let you know how it goes.

Thanks,

Doug.

On Wed, Aug 3, 2022 at 12:49 PM Dan Brown @.***> wrote:

@dzitzels1 https://github.com/dzitzels1 Happy to help.

If you do find an artisan file there, it likely means that's the location
of your BookStack install.
In that case, you might be able to go into that directory (cd
/var/www/bookstack) and run our normal update commands:
https://www.bookstackapp.com/docs/admin/updates/

I'd advise backing up first, so snapshot the instance or whatever options
you have in AWS before attempting.
Might need to backup the database aswell if not on the same machine.

If any of the update commands fail, just let me know.
If the composer command fails, don't be tempted to install the composer
system package, that often creates more issues.

—
Reply to this email directly, view it on GitHub
https://github.com/BookStackApp/BookStack/issues/3618#issuecomment-1204348023,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANOUOSSZMRVUYJ6O6FIDWRLVXK5K7ANCNFSM55PYZRMA
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Doug Zitzelsberger, AWS CCP
(801) 341-9157
@.***

https://www.certmetrics.com/amazon/public/badge.aspx?i=9&t=c&d=2020-01-06&ci=AWS01223108

@dzitzels1 commented on GitHub (Aug 3, 2022): Hi Dan, I did find the artisan file in that folder. Fortunately, this is a dev instance - I have a dev and a prod instance but the prod instance is roughly identical. I will try the update commands on my dev instance to see what happens and where it fails. I want to get this right on the dev side so the procedure is nice and clean for the prod side. I will let you know how it goes. Thanks, Doug. On Wed, Aug 3, 2022 at 12:49 PM Dan Brown ***@***.***> wrote: > @dzitzels1 <https://github.com/dzitzels1> Happy to help. > > If you do find an artisan file there, it likely means that's the location > of your BookStack install. > In that case, you might be able to go into that directory (cd > /var/www/bookstack) and run our normal update commands: > https://www.bookstackapp.com/docs/admin/updates/ > > I'd advise backing up first, so snapshot the instance or whatever options > you have in AWS before attempting. > Might need to backup the database aswell if not on the same machine. > > If any of the update commands fail, just let me know. > If the composer command fails, don't be tempted to install the composer > system package, that often creates more issues. > > — > Reply to this email directly, view it on GitHub > <https://github.com/BookStackApp/BookStack/issues/3618#issuecomment-1204348023>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ANOUOSSZMRVUYJ6O6FIDWRLVXK5K7ANCNFSM55PYZRMA> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> > -- Doug Zitzelsberger, AWS CCP (801) 341-9157 ***@***.*** https://www.certmetrics.com/amazon/public/badge.aspx?i=9&t=c&d=2020-01-06&ci=AWS01223108

OVERLORD commented

2026-02-05 05:47:47 +03:00

@dzitzels1 commented on GitHub (Aug 3, 2022):

Hi Dan,

So the first place the upgrade is failing is that the install folder is not
a git repository and does not have a .git folder therefore it cannot do a
proper pull of the release branch.

Unfortunately, I am relatively new to git because I come from a hardware
infrastructure background so I am poking around but I am not quite sure
what to do here. Is there something easy that I might be missing?

Doug.

On Wed, Aug 3, 2022 at 1:37 PM Doug Zitzelsberger @.***>
wrote:

Hi Dan,

I did find the artisan file in that folder. Fortunately, this is a dev
instance - I have a dev and a prod instance but the prod instance is
roughly identical.
I will try the update commands on my dev instance to see what happens and
where it fails.

I want to get this right on the dev side so the procedure is nice and
clean for the prod side.

I will let you know how it goes.

Thanks,

Doug.

On Wed, Aug 3, 2022 at 12:49 PM Dan Brown @.***>
wrote:

@dzitzels1 https://github.com/dzitzels1 Happy to help.

If you do find an artisan file there, it likely means that's the location
of your BookStack install.
In that case, you might be able to go into that directory (cd
/var/www/bookstack) and run our normal update commands:
https://www.bookstackapp.com/docs/admin/updates/

I'd advise backing up first, so snapshot the instance or whatever options
you have in AWS before attempting.
Might need to backup the database aswell if not on the same machine.

If any of the update commands fail, just let me know.
If the composer command fails, don't be tempted to install the composer
system package, that often creates more issues.

—
Reply to this email directly, view it on GitHub
https://github.com/BookStackApp/BookStack/issues/3618#issuecomment-1204348023,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANOUOSSZMRVUYJ6O6FIDWRLVXK5K7ANCNFSM55PYZRMA
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Doug Zitzelsberger, AWS CCP
(801) 341-9157
@.***

https://www.certmetrics.com/amazon/public/badge.aspx?i=9&t=c&d=2020-01-06&ci=AWS01223108

--
Doug Zitzelsberger, AWS CCP
(801) 341-9157
@.***

https://www.certmetrics.com/amazon/public/badge.aspx?i=9&t=c&d=2020-01-06&ci=AWS01223108

@dzitzels1 commented on GitHub (Aug 3, 2022): Hi Dan, So the first place the upgrade is failing is that the install folder is not a git repository and does not have a .git folder therefore it cannot do a proper pull of the release branch. Unfortunately, I am relatively new to git because I come from a hardware infrastructure background so I am poking around but I am not quite sure what to do here. Is there something easy that I might be missing? Doug. On Wed, Aug 3, 2022 at 1:37 PM Doug Zitzelsberger ***@***.***> wrote: > Hi Dan, > > I did find the artisan file in that folder. Fortunately, this is a dev > instance - I have a dev and a prod instance but the prod instance is > roughly identical. > I will try the update commands on my dev instance to see what happens and > where it fails. > > I want to get this right on the dev side so the procedure is nice and > clean for the prod side. > > I will let you know how it goes. > > Thanks, > > Doug. > > On Wed, Aug 3, 2022 at 12:49 PM Dan Brown ***@***.***> > wrote: > >> @dzitzels1 <https://github.com/dzitzels1> Happy to help. >> >> If you do find an artisan file there, it likely means that's the location >> of your BookStack install. >> In that case, you might be able to go into that directory (cd >> /var/www/bookstack) and run our normal update commands: >> https://www.bookstackapp.com/docs/admin/updates/ >> >> I'd advise backing up first, so snapshot the instance or whatever options >> you have in AWS before attempting. >> Might need to backup the database aswell if not on the same machine. >> >> If any of the update commands fail, just let me know. >> If the composer command fails, don't be tempted to install the composer >> system package, that often creates more issues. >> >> — >> Reply to this email directly, view it on GitHub >> <https://github.com/BookStackApp/BookStack/issues/3618#issuecomment-1204348023>, >> or unsubscribe >> <https://github.com/notifications/unsubscribe-auth/ANOUOSSZMRVUYJ6O6FIDWRLVXK5K7ANCNFSM55PYZRMA> >> . >> You are receiving this because you were mentioned.Message ID: >> ***@***.***> >> > > > -- > Doug Zitzelsberger, AWS CCP > (801) 341-9157 > ***@***.*** > > > https://www.certmetrics.com/amazon/public/badge.aspx?i=9&t=c&d=2020-01-06&ci=AWS01223108 > -- Doug Zitzelsberger, AWS CCP (801) 341-9157 ***@***.*** https://www.certmetrics.com/amazon/public/badge.aspx?i=9&t=c&d=2020-01-06&ci=AWS01223108

OVERLORD commented

2026-02-05 05:47:48 +03:00

@ssddanbrown commented on GitHub (Aug 4, 2022):

Darn, that does makes things a bit more difficult. Pretty sure it'd be possible to setup git within the existing folder but it's not something I do often, will need to test things out to find the smoothest approach. Will play around with ideas tomorrow (Almost midnight here) and get back to you.

@ssddanbrown commented on GitHub (Aug 4, 2022): Darn, that does makes things a bit more difficult. Pretty sure it'd be possible to setup git within the existing folder but it's not something I do often, will need to test things out to find the smoothest approach. Will play around with ideas tomorrow (Almost midnight here) and get back to you.

OVERLORD commented

2026-02-05 05:47:53 +03:00

@ssddanbrown commented on GitHub (Aug 4, 2022):

Alrighty, Just had a test and the below seems to convert an existing non-git setup to a git setup.
Of course, backup/snapshot before for safety.
All of these should be ran within your /var/www/bookstack directory. Could be further issues if there are other unexpected changes.

Lines starting with hashes are comments only.

# Initialize a git repo within the directory
git init

# Set git to ignore any file permission changes
git config core.fileMode false

# Add the BookStack repo as the origin remote
git remote add origin https://github.com/BookStackApp/BookStack.git

# Fetch data from the origin we just added
git fetch

# Force change the codebase & repo state to the current version
git checkout -f v21.05.3

# Check the status of the folder to ensure everything matches the
# official BookStack code state. Should output "nothing to commit, working tree clean"
git status

# Checkout to the latest branch (Latest release version).
# Do this when ready to upgrade
git checkout release

After the last command, you should be able to continue the update process as normal.

@ssddanbrown commented on GitHub (Aug 4, 2022): Alrighty, Just had a test and the below seems to convert an existing non-git setup to a git setup. Of course, backup/snapshot before for safety. All of these should be ran within your `/var/www/bookstack` directory. Could be further issues if there are other unexpected changes. Lines starting with hashes are comments only. ```shell # Initialize a git repo within the directory git init # Set git to ignore any file permission changes git config core.fileMode false # Add the BookStack repo as the origin remote git remote add origin https://github.com/BookStackApp/BookStack.git # Fetch data from the origin we just added git fetch # Force change the codebase & repo state to the current version git checkout -f v21.05.3 # Check the status of the folder to ensure everything matches the # official BookStack code state. Should output "nothing to commit, working tree clean" git status # Checkout to the latest branch (Latest release version). # Do this when ready to upgrade git checkout release ``` After the last command, you should be able to continue the update process as normal.

OVERLORD commented

2026-02-05 05:47:57 +03:00

@dzitzels1 commented on GitHub (Aug 4, 2022):

Thanks Dan! I will try this out this morning.

Doug.

On Thu, Aug 4, 2022 at 3:31 AM Dan Brown @.***> wrote:

Alrighty, Just had a test and the below seems to convert an existing
non-git setup to a git setup.
Of course, backup/snapshot before for safety.
All of these should be ran within your /var/www/bookstack directory.
Could be further issues if there are other unexpected changes.

Lines starting with hashes are comments only.

Initialize a git repo within the directory

git init

Set git to ignore any file permission changes

git config core.fileMode false

Add the BookStack repo as the origin remote

git remote add origin https://github.com/BookStackApp/BookStack.git

Fetch data from the origin we just added

git fetch

Force change the codebase & repo state to the current version

git checkout -f v21.05.3

Check the status of the folder to ensure everything matches the# official BookStack code state. Should output "nothing to commit, working tree clean"

git status

Checkout to the latest branch (Latest release version).# Do this when ready to upgrade

git checkout release

After the last command, you should be able to continue the update process
as normal.

—
Reply to this email directly, view it on GitHub
https://github.com/BookStackApp/BookStack/issues/3618#issuecomment-1205004406,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANOUOSXSWZRTCDCJBVPQPVLVXOEYFANCNFSM55PYZRMA
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Doug Zitzelsberger, AWS CCP
(801) 341-9157
@.***

https://www.certmetrics.com/amazon/public/badge.aspx?i=9&t=c&d=2020-01-06&ci=AWS01223108

@dzitzels1 commented on GitHub (Aug 4, 2022): Thanks Dan! I will try this out this morning. Doug. On Thu, Aug 4, 2022 at 3:31 AM Dan Brown ***@***.***> wrote: > Alrighty, Just had a test and the below seems to convert an existing > non-git setup to a git setup. > Of course, backup/snapshot before for safety. > All of these should be ran within your /var/www/bookstack directory. > Could be further issues if there are other unexpected changes. > > Lines starting with hashes are comments only. > > # Initialize a git repo within the directory > git init > # Set git to ignore any file permission changes > git config core.fileMode false > # Add the BookStack repo as the origin remote > git remote add origin https://github.com/BookStackApp/BookStack.git > # Fetch data from the origin we just added > git fetch > # Force change the codebase & repo state to the current version > git checkout -f v21.05.3 > # Check the status of the folder to ensure everything matches the# official BookStack code state. Should output "nothing to commit, working tree clean" > git status > # Checkout to the latest branch (Latest release version).# Do this when ready to upgrade > git checkout release > > After the last command, you should be able to continue the update process > as normal. > > — > Reply to this email directly, view it on GitHub > <https://github.com/BookStackApp/BookStack/issues/3618#issuecomment-1205004406>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ANOUOSXSWZRTCDCJBVPQPVLVXOEYFANCNFSM55PYZRMA> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> > -- Doug Zitzelsberger, AWS CCP (801) 341-9157 ***@***.*** https://www.certmetrics.com/amazon/public/badge.aspx?i=9&t=c&d=2020-01-06&ci=AWS01223108

OVERLORD commented

2026-02-05 05:48:02 +03:00

@dzitzels1 commented on GitHub (Aug 4, 2022):

Hi Dan,

So since this is on AWS, I just created a throwaway instance to try this
out and it worked perfectly! Thank you!

Next, I will be trying it on my real dev instance with our customizations
and assuming that works well (which I expect), it will be onto the prod
instance.

Thanks so much for your help!

Doug.

On Thu, Aug 4, 2022 at 9:25 AM Doug Zitzelsberger @.***>
wrote:

Thanks Dan! I will try this out this morning.

Doug.

On Thu, Aug 4, 2022 at 3:31 AM Dan Brown @.***> wrote:

Alrighty, Just had a test and the below seems to convert an existing
non-git setup to a git setup.
Of course, backup/snapshot before for safety.
All of these should be ran within your /var/www/bookstack directory.
Could be further issues if there are other unexpected changes.

Lines starting with hashes are comments only.

Initialize a git repo within the directory

git init

Set git to ignore any file permission changes

git config core.fileMode false

Add the BookStack repo as the origin remote

git remote add origin https://github.com/BookStackApp/BookStack.git

Fetch data from the origin we just added

git fetch

Force change the codebase & repo state to the current version

git checkout -f v21.05.3

Check the status of the folder to ensure everything matches the# official BookStack code state. Should output "nothing to commit, working tree clean"

git status

Checkout to the latest branch (Latest release version).# Do this when ready to upgrade

git checkout release

After the last command, you should be able to continue the update process
as normal.

—
Reply to this email directly, view it on GitHub
https://github.com/BookStackApp/BookStack/issues/3618#issuecomment-1205004406,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANOUOSXSWZRTCDCJBVPQPVLVXOEYFANCNFSM55PYZRMA
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Doug Zitzelsberger, AWS CCP
(801) 341-9157
@.***

https://www.certmetrics.com/amazon/public/badge.aspx?i=9&t=c&d=2020-01-06&ci=AWS01223108

--
Doug Zitzelsberger, AWS CCP
(801) 341-9157
@.***

https://www.certmetrics.com/amazon/public/badge.aspx?i=9&t=c&d=2020-01-06&ci=AWS01223108

@dzitzels1 commented on GitHub (Aug 4, 2022): Hi Dan, So since this is on AWS, I just created a throwaway instance to try this out and it worked perfectly! Thank you! Next, I will be trying it on my real dev instance with our customizations and assuming that works well (which I expect), it will be onto the prod instance. Thanks so much for your help! Doug. On Thu, Aug 4, 2022 at 9:25 AM Doug Zitzelsberger ***@***.***> wrote: > Thanks Dan! I will try this out this morning. > > Doug. > > On Thu, Aug 4, 2022 at 3:31 AM Dan Brown ***@***.***> wrote: > >> Alrighty, Just had a test and the below seems to convert an existing >> non-git setup to a git setup. >> Of course, backup/snapshot before for safety. >> All of these should be ran within your /var/www/bookstack directory. >> Could be further issues if there are other unexpected changes. >> >> Lines starting with hashes are comments only. >> >> # Initialize a git repo within the directory >> git init >> # Set git to ignore any file permission changes >> git config core.fileMode false >> # Add the BookStack repo as the origin remote >> git remote add origin https://github.com/BookStackApp/BookStack.git >> # Fetch data from the origin we just added >> git fetch >> # Force change the codebase & repo state to the current version >> git checkout -f v21.05.3 >> # Check the status of the folder to ensure everything matches the# official BookStack code state. Should output "nothing to commit, working tree clean" >> git status >> # Checkout to the latest branch (Latest release version).# Do this when ready to upgrade >> git checkout release >> >> After the last command, you should be able to continue the update process >> as normal. >> >> — >> Reply to this email directly, view it on GitHub >> <https://github.com/BookStackApp/BookStack/issues/3618#issuecomment-1205004406>, >> or unsubscribe >> <https://github.com/notifications/unsubscribe-auth/ANOUOSXSWZRTCDCJBVPQPVLVXOEYFANCNFSM55PYZRMA> >> . >> You are receiving this because you were mentioned.Message ID: >> ***@***.***> >> > > > -- > Doug Zitzelsberger, AWS CCP > (801) 341-9157 > ***@***.*** > > > https://www.certmetrics.com/amazon/public/badge.aspx?i=9&t=c&d=2020-01-06&ci=AWS01223108 > -- Doug Zitzelsberger, AWS CCP (801) 341-9157 ***@***.*** https://www.certmetrics.com/amazon/public/badge.aspx?i=9&t=c&d=2020-01-06&ci=AWS01223108

OVERLORD commented

2026-02-05 05:48:03 +03:00

@dzitzels1 commented on GitHub (Aug 4, 2022):

Hi Dan,

One more question for you if you will please - upgrading from 21.05.3, that
far back, are there any database schema changes or any other gotchas like
that where I need to be aware and take specific action? It does not seem
so in the tests that I have run but I thought I would ask before I get to
production.

Thanks,

Doug.

On Thu, Aug 4, 2022 at 9:52 AM Doug Zitzelsberger @.***>
wrote:

Hi Dan,

So since this is on AWS, I just created a throwaway instance to try this
out and it worked perfectly! Thank you!

Next, I will be trying it on my real dev instance with our customizations
and assuming that works well (which I expect), it will be onto the prod
instance.

Thanks so much for your help!

Doug.

On Thu, Aug 4, 2022 at 9:25 AM Doug Zitzelsberger @.***>
wrote:

Thanks Dan! I will try this out this morning.

Doug.

On Thu, Aug 4, 2022 at 3:31 AM Dan Brown @.***>
wrote:

Alrighty, Just had a test and the below seems to convert an existing
non-git setup to a git setup.
Of course, backup/snapshot before for safety.
All of these should be ran within your /var/www/bookstack directory.
Could be further issues if there are other unexpected changes.

Lines starting with hashes are comments only.

Initialize a git repo within the directory

git init

Set git to ignore any file permission changes

git config core.fileMode false

Add the BookStack repo as the origin remote

git remote add origin https://github.com/BookStackApp/BookStack.git

Fetch data from the origin we just added

git fetch

Force change the codebase & repo state to the current version

git checkout -f v21.05.3

Check the status of the folder to ensure everything matches the# official BookStack code state. Should output "nothing to commit, working tree clean"

git status

Checkout to the latest branch (Latest release version).# Do this when ready to upgrade

git checkout release

After the last command, you should be able to continue the update
process as normal.

—
Reply to this email directly, view it on GitHub
https://github.com/BookStackApp/BookStack/issues/3618#issuecomment-1205004406,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANOUOSXSWZRTCDCJBVPQPVLVXOEYFANCNFSM55PYZRMA
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Doug Zitzelsberger, AWS CCP
(801) 341-9157
@.***

https://www.certmetrics.com/amazon/public/badge.aspx?i=9&t=c&d=2020-01-06&ci=AWS01223108

--
Doug Zitzelsberger, AWS CCP
(801) 341-9157
@.***

https://www.certmetrics.com/amazon/public/badge.aspx?i=9&t=c&d=2020-01-06&ci=AWS01223108

--
Doug Zitzelsberger, AWS CCP
(801) 341-9157
@.***

https://www.certmetrics.com/amazon/public/badge.aspx?i=9&t=c&d=2020-01-06&ci=AWS01223108

@dzitzels1 commented on GitHub (Aug 4, 2022): Hi Dan, One more question for you if you will please - upgrading from 21.05.3, that far back, are there any database schema changes or any other gotchas like that where I need to be aware and take specific action? It does not seem so in the tests that I have run but I thought I would ask before I get to production. Thanks, Doug. On Thu, Aug 4, 2022 at 9:52 AM Doug Zitzelsberger ***@***.***> wrote: > Hi Dan, > > So since this is on AWS, I just created a throwaway instance to try this > out and it worked perfectly! Thank you! > > Next, I will be trying it on my real dev instance with our customizations > and assuming that works well (which I expect), it will be onto the prod > instance. > > Thanks so much for your help! > > Doug. > > On Thu, Aug 4, 2022 at 9:25 AM Doug Zitzelsberger ***@***.***> > wrote: > >> Thanks Dan! I will try this out this morning. >> >> Doug. >> >> On Thu, Aug 4, 2022 at 3:31 AM Dan Brown ***@***.***> >> wrote: >> >>> Alrighty, Just had a test and the below seems to convert an existing >>> non-git setup to a git setup. >>> Of course, backup/snapshot before for safety. >>> All of these should be ran within your /var/www/bookstack directory. >>> Could be further issues if there are other unexpected changes. >>> >>> Lines starting with hashes are comments only. >>> >>> # Initialize a git repo within the directory >>> git init >>> # Set git to ignore any file permission changes >>> git config core.fileMode false >>> # Add the BookStack repo as the origin remote >>> git remote add origin https://github.com/BookStackApp/BookStack.git >>> # Fetch data from the origin we just added >>> git fetch >>> # Force change the codebase & repo state to the current version >>> git checkout -f v21.05.3 >>> # Check the status of the folder to ensure everything matches the# official BookStack code state. Should output "nothing to commit, working tree clean" >>> git status >>> # Checkout to the latest branch (Latest release version).# Do this when ready to upgrade >>> git checkout release >>> >>> After the last command, you should be able to continue the update >>> process as normal. >>> >>> — >>> Reply to this email directly, view it on GitHub >>> <https://github.com/BookStackApp/BookStack/issues/3618#issuecomment-1205004406>, >>> or unsubscribe >>> <https://github.com/notifications/unsubscribe-auth/ANOUOSXSWZRTCDCJBVPQPVLVXOEYFANCNFSM55PYZRMA> >>> . >>> You are receiving this because you were mentioned.Message ID: >>> ***@***.***> >>> >> >> >> -- >> Doug Zitzelsberger, AWS CCP >> (801) 341-9157 >> ***@***.*** >> >> >> https://www.certmetrics.com/amazon/public/badge.aspx?i=9&t=c&d=2020-01-06&ci=AWS01223108 >> > > > -- > Doug Zitzelsberger, AWS CCP > (801) 341-9157 > ***@***.*** > > > https://www.certmetrics.com/amazon/public/badge.aspx?i=9&t=c&d=2020-01-06&ci=AWS01223108 > -- Doug Zitzelsberger, AWS CCP (801) 341-9157 ***@***.*** https://www.certmetrics.com/amazon/public/badge.aspx?i=9&t=c&d=2020-01-06&ci=AWS01223108

OVERLORD commented

2026-02-05 05:48:06 +03:00

@ssddanbrown commented on GitHub (Aug 4, 2022):

Hi @dzitzels1,

Database changes should generally be handled by the application itself when running the php artisan migrate update step.
Only in erroneous situation should you need to to manually be altering the database. Just be sure to record any errors that arise when originally running the upgrade commands.

Otherwise, It's wise to read through the relevant "Version Specific Instructions" on our updates page:
https://www.bookstackapp.com/docs/admin/updates/#version-specific-instructions

I ensure that anything that could be considered a breaking change or a security issue is listed there. The vast majority of them only apply to specific scenarios or features. Sometimes we update the requirements (Such as the minimum version of PHP required) which can be more wide-spread. You listed PHP 7.4 in your original post, which is still currently supported, but we will be making the minimum PHP 8.0 later this year, just a fore-warning.

One that you might come across is as change to the minimum version of composer (PHP dependency manager), as listed in the "Updating to v21.12.3 or higher" part of the updates page linked above.This part of the docs detail how to handle this.

@ssddanbrown commented on GitHub (Aug 4, 2022): Hi @dzitzels1, Database changes should generally be handled by the application itself when running the `php artisan migrate` update step. Only in erroneous situation should you need to to manually be altering the database. Just be sure to record any errors that arise when originally running the upgrade commands. Otherwise, It's wise to read through the relevant "Version Specific Instructions" on our updates page: https://www.bookstackapp.com/docs/admin/updates/#version-specific-instructions I ensure that anything that could be considered a breaking change or a security issue is listed there. The vast majority of them only apply to specific scenarios or features. Sometimes we update the requirements (Such as the minimum version of PHP required) which can be more wide-spread. You listed PHP 7.4 in your original post, which is still currently supported, but we will be making the minimum PHP 8.0 later this year, just a fore-warning. One that you might come across is as change to the minimum version of composer (PHP dependency manager), as listed in the "Updating to v21.12.3 or higher" part of the updates page linked above.This part of the docs detail how to handle this.

OVERLORD commented

2026-02-05 05:48:10 +03:00

@dzitzels1 commented on GitHub (Aug 6, 2022):

Hi Dan,

I realize that you are most likely asleep now so this should hopefully
greet you as a pleasant surprise in the morning.

With your guidance above, I was able to update my BookStack production
installation successfully. There were a few bumps and bruises along the
way but by and large they were of my own doing.

Hopefully going forward, this will be a much easier process. I plan to hit
the major versions that you release.

I want you to know that I do read the update notes pretty carefully and
they were spot on with what I encountered. I was probably overly concerned
that I had missed something - BookStack is a pretty big deal at our company
because it is our main wiki resource.

Thanks again for all of your help.

Doug.

On Thu, Aug 4, 2022 at 1:50 PM Dan Brown @.***> wrote:

Hi @dzitzels1 https://github.com/dzitzels1,

Database changes should generally be handled by the application itself
when running the php artisan migrate update step.
Only in erroneous situation should you need to to manually be altering the
database. Just be sure to record any errors that arise when originally
running the upgrade commands.

Otherwise, It's wise to read through the relevant "Version Specific
Instructions" on our updates page:

https://www.bookstackapp.com/docs/admin/updates/#version-specific-instructions

I ensure that anything that could be considered a breaking change or a
security issue is listed there. The vast majority of them only apply to
specific scenarios or features. Sometimes we update the requirements (Such
as the minimum version of PHP required) which can be more wide-spread. You
listed PHP 7.4 in your original post, which is still currently supported,
but we will be making the minimum PHP 8.0 later this year, just a
fore-warning.

One that you might come across is as change to the minimum version of
composer (PHP dependency manager), as listed in the "Updating to v21.12.3
or higher" part of the updates page linked above.This part of the docs
detail how to handle this.

—
Reply to this email directly, view it on GitHub
https://github.com/BookStackApp/BookStack/issues/3618#issuecomment-1205701730,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANOUOSUS3W3AH5SBYDI4TGDVXQNILANCNFSM55PYZRMA
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Doug Zitzelsberger, AWS CCP
(801) 341-9157
@.***

https://www.certmetrics.com/amazon/public/badge.aspx?i=9&t=c&d=2020-01-06&ci=AWS01223108

@dzitzels1 commented on GitHub (Aug 6, 2022): Hi Dan, I realize that you are most likely asleep now so this should hopefully greet you as a pleasant surprise in the morning. With your guidance above, I was able to update my BookStack production installation successfully. There were a few bumps and bruises along the way but by and large they were of my own doing. Hopefully going forward, this will be a much easier process. I plan to hit the major versions that you release. I want you to know that I do read the update notes pretty carefully and they were spot on with what I encountered. I was probably overly concerned that I had missed something - BookStack is a pretty big deal at our company because it is our main wiki resource. Thanks again for all of your help. Doug. On Thu, Aug 4, 2022 at 1:50 PM Dan Brown ***@***.***> wrote: > Hi @dzitzels1 <https://github.com/dzitzels1>, > > Database changes should generally be handled by the application itself > when running the php artisan migrate update step. > Only in erroneous situation should you need to to manually be altering the > database. Just be sure to record any errors that arise when originally > running the upgrade commands. > > Otherwise, It's wise to read through the relevant "Version Specific > Instructions" on our updates page: > > https://www.bookstackapp.com/docs/admin/updates/#version-specific-instructions > > I ensure that anything that could be considered a breaking change or a > security issue is listed there. The vast majority of them only apply to > specific scenarios or features. Sometimes we update the requirements (Such > as the minimum version of PHP required) which can be more wide-spread. You > listed PHP 7.4 in your original post, which is still currently supported, > but we will be making the minimum PHP 8.0 later this year, just a > fore-warning. > > One that you might come across is as change to the minimum version of > composer (PHP dependency manager), as listed in the "Updating to v21.12.3 > or higher" part of the updates page linked above.This part of the docs > detail how to handle this. > > — > Reply to this email directly, view it on GitHub > <https://github.com/BookStackApp/BookStack/issues/3618#issuecomment-1205701730>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ANOUOSUS3W3AH5SBYDI4TGDVXQNILANCNFSM55PYZRMA> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> > -- Doug Zitzelsberger, AWS CCP (801) 341-9157 ***@***.*** https://www.certmetrics.com/amazon/public/badge.aspx?i=9&t=c&d=2020-01-06&ci=AWS01223108

OVERLORD commented

2026-02-05 05:48:12 +03:00

@ssddanbrown commented on GitHub (Aug 7, 2022):

@dzitzels1 That's great to hear! Yeah, now that your instance is compatible with our updates process it should be relatively smooth sailing.

I'll therefore close this issue off.

@ssddanbrown commented on GitHub (Aug 7, 2022): @dzitzels1 That's great to hear! Yeah, now that your instance is compatible with our updates process it should be relatively smooth sailing. I'll therefore close this issue off.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/BookStack#2937