# Allow asset compilation without \`color\_schemes\` table

**URL:** <https://meta.discourse.org/t/allow-asset-compilation-without-color-schemes-table/16297>\
**Category:** Feature\
**Created:** [June 6, 2014, 5:37pm UTC](https://meta.discourse.org/t/allow-asset-compilation-without-color-schemes-table/16297 "2014-06-06T17:37:40Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![hstove](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/hstove/32/114343_2.png) [@hstove](https://meta.discourse.org/u/hstove)\
**Post date:** [June 6, 2014, 5:37pm UTC](https://meta.discourse.org/t/allow-asset-compilation-without-color-schemes-table/16297/1 "2014-06-06T17:37:40Z")

</div>

Heroku setup with Discourse has been simplified a lot over the development of Discourse (from what I can tell), but at the moment there is a hangup during asset compilation when the database has not been set up.

Is it possible to allow asset compilation when the DB hasn’t been created at all? I see that other assets fail ‘smoothly’, but compilation fails and exits when the `color_schemes` table hasn’t been created. Is there an easy workaround for this?

Otherwise, it seems like I can temporarily disable color schemes, but I’m not sure how. For now, I’ve been able to get past this by manually changing a few lines in `discourse_sass_importer.rb` (and now `discourse_stylesheets.rb`), which is definitely a hack.

Thanks!

---

_[View the full topic](https://meta.discourse.org/t/allow-asset-compilation-without-color-schemes-table/16297)._