# Best practice to prevent to stolen ignition resources

**URL:** <https://forum.inductiveautomation.com/t/best-practice-to-prevent-to-stolen-ignition-resources/44344>\
**Category:** Ignition\
**Created:** [March 11, 2021, 2:25am UTC](https://forum.inductiveautomation.com/t/best-practice-to-prevent-to-stolen-ignition-resources/44344 "2021-03-11T02:25:11Z")\
**Posts on this page:** 1\
**Showing post:** 98

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [August 10, 2023, 11:58am UTC](https://forum.inductiveautomation.com/t/best-practice-to-prevent-to-stolen-ignition-resources/44344/98 "2023-08-10T11:58:32Z")

</div>

> [@chaoliang](#):
>
> Maybe it's just a simple script with hundreds of lines

If it is that valuable, it should be easy to justify a little bit of time to make it a compiled resource instead of a script.

---

_[View the full topic](https://forum.inductiveautomation.com/t/best-practice-to-prevent-to-stolen-ignition-resources/44344)._
