mirror of
https://github.com/wahyd4/gitlabhq.git
synced 2026-08-14 07:06:17 +10:00
Marin JankovskiandDmitriy Zaporozhets
dd9d17a6e3
Fix note attachments XSS and access control Replaces the reverted #1528, as proposed in https://gitlab.com/gitlab-org/omnibus-gitlab/issues/434, as discussed with @dzaporozhets and as summarized in #2032. @marin Could you take a look at the nginx config and apply it to Omnibus once this gets merged? See merge request !1553
Depending on the installation method and your GitLab version, there are multiple update guides. Choose one that fits your needs.
Omnibus Packages
- Omnibus update guide contains the steps needed to update a GitLab package.
Installation from source
- The individual upgrade guides are for those who have installed GitLab from source.
- The CE to EE update guides are for subscribers of the Enterprise Edition only. The steps are very similar to a version upgrade: stop the server, get the code, update config files for the new functionality, install libs and do migrations, update the init script, start the application and check the application status.
- Upgrader is an automatic ruby script that performs the update for installations from source.
- Patch versions guide includes the steps needed for a patch version, eg. 6.2.0 to 6.2.1.
Miscellaneous
- MySQL to PostgreSQL guides you through migrating your database from MySQL to PostgreSQL.