Age | Commit message (Collapse) | Author |
|
Instead of requiring one separate document for every version (which is
created by release managers), we now use a single document for both
Community Edition and Enterprise Edition. This allows developers to add
guidelines right away, instead of release managers having to determine
what to add.
Version specific upgrading instructions are placed in a separate
section. This prevents instructions from lingering around for many
versions should a developer forget to remove them. This also ensures
that all instructions are kept in a single place, instead of being
spread across different documents.
A minor downside is that CE and EE guidelines now live in the same
document, which could cause merge conflicts. Since we are working
towards a single codebase, this should only be an issue until we merge
the codebases together; something we expect to do in the coming months.
This commit also removes all old upgrading instructions, but these can
still be accessed using Git branch specific URLs (included in the
updating README).
|
|
|
|
- Also makes other minor Markdown fixes that were near the main fixes.
|
|
|
|
[ci skip]
|
|
[ci skip]
|
|
[ci skip]
|
|
add editor command to update database.yml; cleanup
|
|
product names, plus a couple of instances of bad Markdown markup.
|
|
start gitlab after mysql tweaks
|
|
|
|
|
|
|
|
Just fixed a minor bug in the markdown notation
|
|
|
|
|
|
[7.4 rc fix] [doc] clarify when database.yml needs to be updated
|
|
[7.4 rc fix] [doc] stop gitlab before mysql optimizations, run checks
|
|
[7.4 rc fix] [doc] actually give command necessary to update unicorn
|
|
Stopping gitlab before backup ensures that backup has everything before upgrade incase something goes wrong. Also remove extra cd.
|
|
Give command to update unicorn.rb rather than just say you need to do it.
|
|
Update MySQL optimizations to reflect doing updates after GitLab has already been started back up.
|
|
Clarify that database.yml should be updated if you are running a MySQL Database. Remove wording that de-emphasises importance of update.
|
|
|
|
As discussed at https://github.com/gitlabhq/gitlabhq/pull/7742#issuecomment-58897445 make sure that tables have correct char set.
|
|
* take -> make
* correct incorrect details about when pool size was changed
|
|
Addresses changes made to installation guide and config files but never
applied in update process. Relevant changes to installation guide and
config files were made in
gitlabhq@cbb5b00,
gitlabhq@498a4e6,
gitlabhq@c33d5e1,
gitlabhq@485162e#diff-e1059d0fa0437ffad94facff86210603,
gitlabhq@72e2fe2#diff-d1b4ff7de834bae6008dd49550413a6f,
gitlabhq@5163a8f#diff-e1059d0fa0437ffad94facff86210603,
gitlabhq@993af5d#diff-e1059d0fa0437ffad94facff86210603,
&
gitlabhq@d3f5a0c.
|