# Print outside of the script console

**URL:** <https://forum.inductiveautomation.com/t/print-outside-of-the-script-console/83149>\
**Category:** Ignition\
**Tags:** ignition81, perspective, scripting\
**Created:** [December 14, 2023, 4:50pm UTC](https://forum.inductiveautomation.com/t/print-outside-of-the-script-console/83149 "2023-12-14T16:50:13Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![Matrix\_Engineering](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/matrix_engineering/32/19781_2.png) [@Matrix\_Engineering](https://forum.inductiveautomation.com/u/Matrix_Engineering)\
**Post date:** [December 14, 2023, 5:22pm UTC](https://forum.inductiveautomation.com/t/print-outside-of-the-script-console/83149/9 "2023-12-14T17:22:08Z")

</div>

> [@Best Practive Integrator Dev Environment](https://forum.inductiveautomation.com/t/best-practive-integrator-dev-environment/27470):
>
> I lead a group of engineers in a medium size integration company, working on multiple different ignition projects at once, for different customers, in different environments, on different versions. Currently for local development we have been spinning up a windows VM for each different gateway our end projects have, and developing off of those. Utilizing locally created memory tag versions of UDTs, and a central SQL Server instance. As you can imagine that starts to really add up, when you have…

---

_[View the full topic](https://forum.inductiveautomation.com/t/print-outside-of-the-script-console/83149)._