Archived documentation — this article is no longer maintained.

The information below is retained for historical reference and may be outdated.

View the current documentation: https://www.quotaguard.com/docs/

Many people handle this with a launch script. Basically make a .qgtunnel.staging and a .qgtunnel.production file.

Then in the launch script do something like this:

#!/bin/bash

if [ "$ENVIRONMENT" == "staging" ]; then
  cp .qgtunnel.staging .qgtunnel
else
  cp .qgtunnel.production .qgtunnel
fi

bin/qgtunnel $@

Then save that as something like bin/qglaunch. Then change your startup code to call bin/qglaunch with all your program arguments instead of bin/qgtunnel.

Others have saved the full .qgtunnel file into an environment variable and in the launch script they create the .qgtunnel file from the environment variable.

If you are using transparent mode, be sure that vendor/nss_wrapper/libnss_wrapper.so is also added to your
repository.

If you have questions, or if this solution doesn’t work or fit your use case, please reach out to us at Support so we can help figure it out with you.


Working with sensitive data, like HIPAA, Financial, or Personally Identifiable Information (PII)? 
    Then you will want to check out our QuotaGuard Shield solution, it's the same as QuotaGuard Static, but with stronger end to end security for your requests. We can also help migrate current Static customers to Shield for free, just reach out to us at Support to request assistance.