# XBlock SDK – Docker – workbench\_database

**URL:** <https://discuss.openedx.org/t/xblock-sdk-docker-workbench-database/4204>\
**Category:** Development\
**Created:** [February 4, 2021, 4:24pm UTC](https://discuss.openedx.org/t/xblock-sdk-docker-workbench-database/4204 "2021-02-04T16:24:34Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![arbrandes](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/arbrandes/32/158_2.png) [@arbrandes](https://discuss.openedx.org/u/arbrandes)\
**Post date:** [February 5, 2021, 10:58am UTC](https://discuss.openedx.org/t/xblock-sdk-docker-workbench-database/4204/2 "2021-02-05T10:58:45Z")

</div>

@Zachary_Trabookis, let me refer you to Braden’s comment from [a couple of months back](https://discuss.openedx.org/t/xblock-sdk-setting-entry-points-for-virtenv/3590/2):

> [@Xblock SDK: Setting entry points for virtenv](https://discuss.openedx.org/t/xblock-sdk-setting-entry-points-for-virtenv/3590/2):
>
> It’s probably worth mentioning that as an XBlock developer, I personally don’t use the XBlock SDK anymore, and just develop and test my XBlock directly in Studio+LMS. The XBlock SDK is useful for learning XBlocks and testing very simple XBlocks but for anything complex it acts differently than the LMS so is less useful.

In other words, unless you have a strong reason for using the SDK, you should probably be developing your XBlock against edx-platform in the devstack.

---

_[View the full topic](https://discuss.openedx.org/t/xblock-sdk-docker-workbench-database/4204)._