-
Notifications
You must be signed in to change notification settings - Fork 7
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
Current version doesn't work as docked, or docs unclear #2
Comments
and the
|
that's after repairing the strange |
Yeah, I have a README update to push. Apologies, I haven’t had a chance to do that given everything else I’ve been trying to pull together |
@squillace you shouldn't need to change anything with:
That is indeed the strange format (where we are just replacing the region. I believe your error is related to credentials. I've updated the README.md, please give that a look and see if it is any clearer. |
The README doesn't describe a working process, and the steps for the creds may be unclear, but here's the error when I pull it and try to install it after cloning and then generating a cred from the bundle in MASTER, as below.
My current guess is that I'm munging the concepts of the "do access key" -- for which I apparently only pass the name? in addition, the current porter.yaml file has this:
--host-bucket=%(bucket)s.{{bundle.parameters.region}}.digitaloceanspaces.com"
Um, don't we mean to escape the "bucket)s" part?
and if I build it from scratch, and THEN install:
The text was updated successfully, but these errors were encountered: