# Set Gateway Settings in a Script?

**URL:** <https://forum.inductiveautomation.com/t/set-gateway-settings-in-a-script/45720>\
**Category:** Ignition\
**Tags:** ignition80, scripting\
**Created:** [April 18, 2021, 5:51pm UTC](https://forum.inductiveautomation.com/t/set-gateway-settings-in-a-script/45720 "2021-04-18T17:51:55Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![sydney.bergeron](https://avatars.discourse-cdn.com/v4/letter/s/779978/32.png) [@sydney.bergeron](https://forum.inductiveautomation.com/u/sydney.bergeron)\
**Post date:** [April 19, 2021, 4:36pm UTC](https://forum.inductiveautomation.com/t/set-gateway-settings-in-a-script/45720/3 "2021-04-19T16:36:07Z")

</div>

@paul-griffith Tackling the same problem as here: [Any 'configuration' tools to set up different connections based on configuration](http://forum.inductiveautomation.com/t/any-configuration-tools-to-set-up-different-connections-based-on-configuration/44099)

Where I have two servers, a development and production server, that I want to be able to perform backup restores to without changing db connection strings. I solved the db problem with a startup script to read a configuration.

I realized after posting that I can change the name of the gateway as an option in the backup restore, so that issue is solved.

But I’d like to be able to do the same thing for the backup folder. That way the development backups aren’t saved in the same place as production backups. (It’s not a huge issue, since the name of the backup file has the name of the gateway, so they are technically discernable if in the same folder. But would be nice to have.)

---

_[View the full topic](https://forum.inductiveautomation.com/t/set-gateway-settings-in-a-script/45720)._
