Skip to main content
Classic

Snapt

Learn how to use the Snapt module.

Deploy

Submit a support request to have the Snapt module deployed.

note

By default Snapt will set a session persistence cookie. If you are using the Varnish Cache module, this will potentially bypass the cache. If this is not the desired behavior, then this cookie needs to be prevented from being set. To do this, either disable the Session Persistence setting in the Snapt dashboard or strip that Set-Cookie response header in the Varnish Cache module (e.g. in the vcl_backend_response subroutine).

Manage

Manage the Snapt module through the Snapt dashboard.

note

Submit a support request if you need help managing this module.

Delete

Follow the steps below to delete the Snapt module from your environment:

  1. Go to the advanced config of the environment you want to delete the Snapt module from.

  2. In the top of the page, copy the URL next to Clone with HTTPS.

  3. Open a terminal and change the current working directory to the location where you want the cloned environment repository.

  4. Clone the environment repository to your local computer. Type git clone followed by the copied URL and then press Enter:

    git clone <copied_url>
  5. In the root directory of the environment repository, delete the Snapt module directory (typically named snapt).

    note

    Skip this step to disable the module instead of deleting it.

  6. In the environment's section.config.json file, delete the module object from the proxychain array, which will look like the following:

    section.config.json
    ...
    "proxychain": [
    ...
    {
    "name": "<module_directory_name>",
    "image": "<module_image>"
    },
    ...
    ],
    ...
    section.config.json
    ...
    "proxychain": [
    ...
    {
    "name": "snapt",
    "image": "snapt:1.0.1"
    },
    ...
    ],
    ...
  7. Stage, commit, and push the changes to the environment's remote repository:

    git add .
    git commit -m "Delete the Snapt module"
    git push