# GenieACS reference deployment **URL:** \ **Category:** Uncategorized\ **Created:** [November 21, 2019, 6:25am UTC](https://forum.genieacs.com/t/genieacs-reference-deployment/469 "2019-11-21T06:25:40Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![pobk](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.genieacs.com/pobk/32/109_2.png) [@pobk](https://forum.genieacs.com/u/pobk)\ **Post date:** [November 21, 2019, 11:13am UTC](https://forum.genieacs.com/t/genieacs-reference-deployment/469/2 "2019-11-21T11:13:49Z")
It has. I wouldn’t say there’s a specific reference deployment since each provider will utilise different mechanisms for provisioning CPE devices with configuration. Off the top of my head, some options you can use here: Flat files, REST APIs, RADIUS, some custom OSS/BSS DB lookup? Different providers have different methodologies so there’s no one-size-fits-all. All I can suggest is deploy it. Ask questions. I will say that unfortunately the documentation is not the greatest for GenieACS… The scripting side/sandbox elements drive me nuts… (e.g. why can I not get some of the HTTP headers for the SOAP request?) and the DSL for provisionioning is a little terse and will take you a while before you stop tearing your hair out… ~ R --- _[View the full topic](https://forum.genieacs.com/t/genieacs-reference-deployment/469)._