edx devstack bug report - bringup error, theme feature off - https://github.com/edx/configuration/issues/744

build-version.yml

---

##  build-version.yml
#
# Use with ansible bringup;
# - *_version specs can be branches, tags, or commits
# - you can comment out any items you do not want to override;
#   they will retain their settings as in ansible playbooks
#   for those items.
#
# github.com account names / repo owners:
#
OPEN_EDX: edx    # Open edX repos
GIT_ACCT: yarko  # your github acct (your development repos), or edx
# Theme repo;
#  Stanford-Online is the Canonical theme;
#  start there in developing a theme.
## Stanford-Online theme has error for now;
THEME_ACCT: yarko  # Theme repos
# COMMON_GIT_MIRROR: 'github.com'
##
# For production stack, I'm hoping this works from here:
# worker_django_settings_module: aws

##
# source repositories and versions
#
# To begin Open edX product development, fork a starting tree,
#   and override repo & version settings to use your fork & devel branch;
#
# Note:  this is your snapshot, and the version
#   of this build-version.yml file is your edx version!

##
# edx_ansible_source_repo: https://{{ COMMON_GIT_MIRROR }}/{{ OPEN_EDX }}/configuration.git
# edx_ansible_source_repo: https://{{ COMMON_GIT_MIRROR }}/{{ GIT_ACCT }}/configuration.git
# configuration_version: master
# configuration_version: 'yarko/build-version'

##
# edx_platform_repo: https://{{ COMMON_GIT_MIRROR }}/{{ GIT_ACCT }}/edx-platform.git
edx_platform_repo: https://{{ COMMON_GIT_MIRROR }}/{{ GIT_ACCT }}/edx-platform.git
# edx_platform_version: release   # would be NICE if this were for latest Open edX release
edx_platform_version: yarko/fix-rake-env-assets

##
# xqueue_source_repo: https://{{ COMMON_GIT_MIRROR }}/{{ OPEN_EDX }}/xqueue.git
# xqueue_version: HEAD
#

##
# xserver_source_repo: https://{{ COMMON_GIT_MIRROR }}/{{ OPEN_EDX }}/xserver.git 
# xserver_version: master

## 
# forum_source_repo: https://{{ COMMON_GIT_MIRROR }}/{{ GIT_ACCT }}/cs_comments_service.git
# forum_version: master   # no release tag/branch, as yet

##
# discern_ease_source_repo: https://{{ COMMON_GIT_MIRROR }}/{{ OPEN_EDX }}/ease.git
# discern_ease_version: HEAD

##
# discern_source_repo: https://{{ COMMON_GIT_MIRROR }}/{{ OPEN_EDX }}/discern.git
# discern_version: master

##
# ora_ease_source_repo: https://{{ COMMON_GIT_MIRROR }}/{{ OPEN_EDX }}/ease.git
# ora_ease_version: master

##
# ora_source_repo: https://{{ COMMON_GIT_MIRROR }}/{{ OPEN_EDX }}/edx-ora.git
# ora_version: master

##
# Theming selection
#  typical process:
#  - bring up the standard edx theme;
#  - bring up a canonically Stanford themed edx;
#  - fork and develop your theme;
edxapp_theme_name: stanford
edxapp_theme_source_repo: https://{{ COMMON_GIT_MIRROR }}/{{ THEME_ACCT }}/edx-theme.git
edxapp_theme_version: master
edxapp_use_custom_theme: true  # false to disable & use std. theme

Yarko - I have a production stack. I would like to play with it in a DevStack. I know how to build a DevStack, but I don't know how to propagate changes from the DevStack to the Production stack. Could you point me in the right direction? For example, theme-ing. If I play with the theme in DevStack, how would I propagate that through to production?

Thanks!