# Let's talk about the native installation

**URL:** <https://discuss.openedx.org/t/lets-talk-about-the-native-installation/3269>\
**Category:** Build-Test-Release\
**Created:** [September 21, 2020, 7:35am UTC](https://discuss.openedx.org/t/lets-talk-about-the-native-installation/3269 "2020-09-21T07:35:26Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![felipe.espinoza.r](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/felipe.espinoza.r/32/282_2.png) [@felipe.espinoza.r](https://discuss.openedx.org/u/felipe.espinoza.r)\
**Post date:** [October 13, 2020, 12:47pm UTC](https://discuss.openedx.org/t/lets-talk-about-the-native-installation/3269/8 "2020-10-13T12:47:58Z")

</div>

To give an alternative of a full migration to tutor, we could instead start migrating services to docker in the current edx/configuration repository, and have ansible install docker and start the services (We could probably have supervisord start the docker images).

This allows us to migrate one service at a time, reusing all the configuration already done by the configuration repo, and give us an incremental upgrade path for all services, as not all of them have a ready to use docker image right now.

---

_[View the full topic](https://discuss.openedx.org/t/lets-talk-about-the-native-installation/3269)._
