# made a small change in email\_backend class, quickest way to test

**URL:** <https://forum.ansible.com/t/made-a-small-change-in-email-backend-class-quickest-way-to-test/27108>\
**Category:** AWX Project\
**Created:** [March 26, 2018, 12:53am UTC](https://forum.ansible.com/t/made-a-small-change-in-email-backend-class-quickest-way-to-test/27108 "2018-03-26T00:53:18Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![MarcG](https://avatars.discourse-cdn.com/v4/letter/m/bb73d2/32.png) [@MarcG](https://forum.ansible.com/u/MarcG)\
**Post date:** [March 26, 2018, 12:53am UTC](https://forum.ansible.com/t/made-a-small-change-in-email-backend-class-quickest-way-to-test/27108/1 "2018-03-26T00:53:18Z")

</div>

Hi,

I made a small change in the docker awx\_task backend in main/notifications/email\_backend.py.

What is the quickest way to have those changes be picked up? Obviously I can restart the docker container, but I’m assuming I can do this with awx\_manage somehow?

Many thanks.

---

<div class="post-metadata">

**Author:** ![matburt](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/matburt/32/3612_2.png) [@matburt](https://forum.ansible.com/u/matburt)\
**Post date:** [March 26, 2018, 12:59am UTC](https://forum.ansible.com/t/made-a-small-change-in-email-backend-class-quickest-way-to-test/27108/2 "2018-03-26T00:59:34Z")

</div>

When developing on AWX it’s best to follow the CONTRIBUTING instructions for the development environment: [https://github.com/ansible/awx/blob/devel/CONTRIBUTING.md](https://github.com/ansible/awx/blob/devel/CONTRIBUTING.md)

---

<div class="post-metadata">

**Author:** ![MarcG](https://avatars.discourse-cdn.com/v4/letter/m/bb73d2/32.png) [@MarcG](https://forum.ansible.com/u/MarcG)\
**Post date:** [March 27, 2018, 11:32am UTC](https://forum.ansible.com/t/made-a-small-change-in-email-backend-class-quickest-way-to-test/27108/3 "2018-03-27T11:32:04Z")

</div>

Thanks Matthew,

I have tried following the contribution guide but I am hitting some errors. I have posted a seperate thread about it.
