little pitfalls about Update documentation from 8.16 to 8.17
Summary
They needs some tweaks for (in my case) source installation.
- https://github.com/gitlabhq/gitlabhq/blob/master/doc/update/8.16-to-8.17.md
- https://github.com/gitlabhq/gitlabhq/blob/master/doc/install/database_mysql.md
Steps to reproduce
Some trouble I've met is described below.
What is the current bug behavior?
gitlab requires `rake webpack:compile RAILS_ENV=production', but not documented.
It should be added at assets:precompile line, or so.
mysql utf8mb4 migration tasks didn't go well
I happen to know this document (and new requirements for mysql) this time, so trying to the procedure described.
- I've got the error in some of `convert to character set' series of sql execution.
#1071 (closed) - Specified key was too long; max key length is 767 bytes
I guess this is because I've quit mysql session once at
Now, ensure that innodb_file_format and innodb_large_prefix are persisted in your my.cnf file.
to edit my.cnf file and reconnect. So runtime `SET GLOBAL innodb_file_format=Barracuda, innodb_large_prefix=1;' setting vanished. It (ensureing my.cnf file line) had better to move latter part, after finishing character set conversion, I think.