Skip to content

Move Collections Name into .env #81

@peblair

Description

@peblair
Collaborator

Per an issue that was mentioned on Slack, we really should be able to specify the collections name used by a CPO in the .env file (because, currently, dev builds of CPO use the production version's Google Drive folder). Primarily, this line would be the the target of some Mustache-generated value.

Activity

jpolitz

jpolitz commented on Jun 16, 2016

@jpolitz
Member

Go for it if you want to tackle it. Though I would keep any templated globals in editor.template.html, and refer to them that way. It's (a) how all of them are done, and (b) avoids templating more files. It'll also make it easier for what Paul is doing to find and incorporate into the webpack stuff.

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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @jpolitz@peblair

        Issue actions

          Move Collections Name into `.env` · Issue #81 · brownplt/code.pyret.org