Migration Guide for v2.1.0

From version 2.1.0, Aurora moved to docker and thus certain code changes were made which are not backward compatible. Meaning, if you directly put 2.1.0 code on the earlier version, changes are your aurora instance will go down. Now there are two ways to rectify this issue.

Add environment variables

Earlier, we used to have config files that would need to be updated with MySQL credentials. From, version 2.1.0 we moved to docker and thus require this configuration to move from files to environment variables. Meaning, you will need to set the following environment variables for the web interface

• AURORA_SQL_USER_FILE
• AURORA_SQL_PASS_FILE
• AURORA_SQL_DB_FILE
• AURORA_SQL_HOST_FILE
• AURORA_SQL_PORT_FILE

and the following environment variables for the judge inside the jail you have configured

• AURORA_SQL_HOSTNAME_FILE
• AURORA_SQL_HOSTPORT_FILE
• AURORA_SQL_USERNAME_FILE
• AURORA_SQL_PASSWORD_FILE
• AURORA_SQL_DATABASE_FILE

Note: These variables should be set to a file path on your filesystem and these files should be readable only by the root user. Otherwise, a user may run a malicious code to read environment variables and then these files to get sensitive information.

Move to docker

For this, check our usign docker in production guide.