Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

refactor to be deployed as an app on workflow #135

Open
bacongobbler opened this issue Aug 12, 2016 · 2 comments
Open

refactor to be deployed as an app on workflow #135

bacongobbler opened this issue Aug 12, 2016 · 2 comments

Comments

@bacongobbler
Copy link
Member

bacongobbler commented Aug 12, 2016

Right now if you attempt to add the following envvars and disable routing, the application won't deploy because it relies on the hard-coded secret paths:

><> deis create postgres
Creating Application... done, created postgres
Git remote deis successfully created for app postgres.
><> deis routing
Routing is disabled.
><> deis config:push
Creating config... done

=== postgres Config
AWS_ACCESS_KEY_ID          ****************
AWS_DEFAULT_REGION         us-west-1
AWS_SECRET_ACCESS_KEY      *************
BUCKET_NAME                test-bucket
DATABASE_STORAGE           s3
PORT                       5432
><> deis pull quay.io/deis/postgres:v2.2.1
Creating build... ...^C

I'd expect that with the above environment variables, deis/postgres should be deployable on Workflow as a standalone app.

@krancour
Copy link
Contributor

Just want some clarification on the intentions behind this... we don't want to deploy / run Workflow's own Postgres this way, right? This is purely so that others can easily deploy Postgres as a Workflow app, yes?

@bacongobbler
Copy link
Member Author

correct.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants