Skip to content

Latest commit

 

History

History
63 lines (43 loc) · 2.28 KB

README.md

File metadata and controls

63 lines (43 loc) · 2.28 KB
Raw

SC Gateway

Deploy it on Google Cloud Run

Run on Google Cloud

Deploy it on AWS Cloudformation

Updated front-end code:

<!-- Snap Pixel Code -->
<script type='text/javascript'>
  (function(e,t,n){if(e.snaptr)return;var a=e.snaptr=function()
          {a.handleRequest?a.handleRequest.apply(a,arguments):a.queue.push(arguments)};
          a.queue=[];var s='script';r=t.createElement(s);r.async=!0;
          r.src=n;var u=t.getElementsByTagName(s)[0];
          u.parentNode.insertBefore(r,u);})(window,document,
  '{{***HOST_URL_GOES_HERE***}}/scevent.min.js');

        snaptr('init', '{{***PIXEL_ID_GOES_HERE***}}', {
  'user_email': '__INSERT_USER_EMAIL__'
              });

        snaptr('track', 'PAGE_VIEW');

</script>
<!-- End Snap Pixel Code -->

To Build a dockerimage:

Prerequisites:

  • Install Docker (if you don't already have it)
  • Install pack
brew install buildpacks/tap/pack

Creating the Image

We utilize Google's Cloud Function Builder buildpack to ensure consistency with what will be generated on Google Cloud Functions

pack build snap-pixel-gateway -B gcr.io/buildpacks/builder:v1

After running that command you should have a docker image named snap-pixel-gateway

This image can then be pushed to a repository with docker push or exported as a .tar.gz with docker export

Running the container

To run the built contianer, you may simply:

docker run --rm -p 8080:8080 snap-pixel-gateway

And the server should be up and running on port 8080

While this is suitable for very testing and development, in production you should use something like docker compose or kubernetes or utilize your hosting architecture's container orchestration such as Amazon ECS to automatically scale up and down and ensure health of containers.