Skip to content

Commit

Permalink
Use env constants
Browse files Browse the repository at this point in the history
No longer using _ss_env in the 4.x version
  • Loading branch information
chillu committed Jul 1, 2019
1 parent 13475d7 commit 40b5857
Showing 1 changed file with 5 additions and 5 deletions.
10 changes: 5 additions & 5 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,13 +15,13 @@ Add these custom repositories to your composer.json

## Sessions with DynamoDB

If you wish to store sessions in DynamoDB, set the following environment variables in your `_ss_environment.php` file:
If you wish to store sessions in DynamoDB, set the required environment variables in `.env`:

// the name of the DynamoDB table to store sessions in
define('AWS_DYNAMODB_SESSION_TABLE', 'mysession');
AWS_DYNAMODB_SESSION_TABLE=mysession

// the region that the DynamoDB table will live in (in this example here it uses Sydney)
define('AWS_REGION_NAME', 'ap-southeast-2');
AWS_REGION_NAME=ap-southeast-2

Once these are in place, this module will configure DynamoDB and register that as the session handler.

Expand All @@ -35,8 +35,8 @@ in EC2 instances, as credentials are automatically handled by the IAM role insid

// the AWS access key and secret. This is optional if you've configured an instance with an IAM role
// http://docs.aws.amazon.com/aws-sdk-php/guide/latest/credentials.html#caching-iam-role-credentials
define('AWS_ACCESS_KEY', '<access key here>');
define('AWS_SECRET_KEY', '<access secret here>');
AWS_ACCESS_KEY=my-access-key
AWS_SECRET_KEY=my-secret

## Garbage collecting sessions

Expand Down

0 comments on commit 40b5857

Please sign in to comment.