Skip to content
This repository was archived by the owner on Dec 11, 2019. It is now read-only.

Conversation

@neongreen
Copy link
Member

Fixes #267

export TAG=$(git rev-parse --abbrev-ref HEAD)
export SERVER_HOST=localhost
export SERVER_PORT=9000
export SECRET_KEY="u?:IPZT:Cun;SP>edigHDs:cpUf2cY\`<7D>b9lHg98^NsVGn]:eLCIjz1Tt_VyIv"
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

TODO: how was this key generated? Add a comment.

Copy link
Contributor

@kamilongus kamilongus May 15, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Run command: sbt playGenerateSecret | grep -i 'generated' | cut -d ' ' -f5 in root project directory.

JAVA_OPTS: "-Dplay.filters.hosts.allowed.1=staging.codesearch.aelve.com -Dplay.filters.hosts.allowed.2=cloud.digitalocean.com"
# In production you must override the APPLICATION_SECRET key
APPLICATION_SECRET: ${SECRET_KEY:-"u?:IPZT:Cun;SP>edigHDs:cpUf2cY\`<7D>b9lHg98^NsVGn]:eLCIjz1Tt_VyIv"}
JAVA_OPTS: "-Dplay.filters.hosts.allowed.1=${SERVER_HOST:?}"
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This removes the cloud.digitalocean.com host. It's unclear whether we can actually remove it without getting in trouble, though.

@neongreen
Copy link
Member Author

Left to do: fix .gitlab-ci.yml (I need help with that; it's unclear where STAGING_SECRET_KEY comes from)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Use the same deployment config for production and staging

3 participants