add-header="x-amz-meta-surrogate-key: site-$PROJECT" \ The Packer template also calls our custom bash script, which uses s3cmd to upload the static site to S3. For a complete example, please see the Packer template used to build the Terraform static site. In the case of our static sites, we use a simple Packer template that spins up a Docker container, builds the static site, and uploads the static site to S3. In Atlas we configure everything using a Packer template. Because of our familiarity, we chose to build the static sites using Atlas and deploy the static sites onto Amazon S3 using the popular s3cmd tool. While static sites were previously built and served by a PaaS, we had to separate the build stage from the deploy stage as part of this effort. The pre-built file was built on each deploy, which led to occasional deployment issues ranging from conflicting Ruby versions, stalled pushes, or incomplete website deploys. A common complaint from customers was that our static websites were slow or inaccessible from different parts of the world. This resulted in less than optimal performance and made global caching difficult and costly. First, all requests to the static site hit a Ruby web server, which then loaded a pre-built file from disk.
FILEZILLA S3 SERIES
The HashiCorp static sites have historically been hosted using a PaaS with a series of custom buildpacks.
FILEZILLA S3 GENERATOR
Each project's website uses Middleman which is a static website generator written in Ruby. Not only do we put significant time and effort to the command line interfaces, error messages, and output, but each project is given its own unique identity and website. As an added bonus, we pre-warm the cache and check for broken links to ensure the best experience possible! What is a Static Site?Īt HashiCorp, we believe an important design and user experience is a key factor in the success of a project. Cache times are set to one year, and we use surrogate keys to purge a specific subset of the cache during deploys. Fastly is configured to pull from the S3 bucket as the origin and dynamically rewrites URL paths to support multiple sites in the same bucket. OverviewĪt a high level, our new static site architecture is modeled as:Ītlas is responsible for building the static site and uploading it to S3. You may have noticed subtle frontend and backend changes to our various websites - this post details the steps we took to migrate our static sites to Fastly. Since then, we have expanded our use of Fastly to front all of our static sites. In November we announced our partnership with Fastly to power the new HashiCorp releases service. Please refer to this tutorial which remains up to date.
0 kommentar(er)
