Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Installation of MySQL

We are running MySQL 5.5.12.  Dev / test stacks can use a local MySQL installation, staging and production stacks use Amazon's RDS service.  Currently, both stacks use different databases in the same RDS instance.

New Stack Database Configuration

These steps assume you are creating a new database where stack = one of dev, bamboo (test), staging, prod, and instance = some unique name.  For developers, we recommend using stack=dev and instance = your unix login

  • Create a new db user <stack><instance>User
  • Generate a unique password for that user, important to not share passwords to decrease chances of accidently stomping on the wrong data.  On windows, I use KeePass to generate a 40-bit hex key.
  • Create the schema <stack><instance>
  • For staging / prod systems, grant the user ability to SELECT and INSERT on the common idGeneratorDB schema
  • Grant the user all permissions except GRANT OPTION, CREATE ROUTINE, ALTER ROUTINE, and TRIGGER on their own schema
  • Important: do not hand out this use to multiple instances

The repository service will create all needed db options on startup.  If you start the repo service, you should shortly see a new set of tables in the db.  If you don't, something has gone wrong in the bootstrapping process and you should look at the service logs to figure out the problem (likely a misconfiguration of the service.)

  • No labels