diff --git a/.eleventy.js b/.eleventy.js index bb1dbcf..4d4e19e 100644 --- a/.eleventy.js +++ b/.eleventy.js @@ -152,6 +152,14 @@ module.exports = function (config) { config.addFilter("markdown", (content) => { return markdownLibrary.render(content); }); + markdownLibrary.renderer.rules.link_open = function (tokens, idx, options, env, self) { + const href = tokens[idx].attrGet("href"); + if (href && href.startsWith("http")) { + tokens[idx].attrPush(["target", "_blank"]); + tokens[idx].attrPush(["rel", "noopener noreferrer"]); + } + return self.renderToken(tokens, idx, options); + }; markdownLibrary.renderer.rules.code_inline = (tokens, idx, {langPrefix = ''}) => { const token = tokens[idx]; return `${htmlEntities(token.content)} `; diff --git a/_data/assetPaths.json b/_data/assetPaths.json index 44f4e81..77646fa 100644 --- a/_data/assetPaths.json +++ b/_data/assetPaths.json @@ -1,8 +1,11 @@ { "admin.js": "/assets/js/admin-OYJBR6FH.js", "admin.map": "/assets/js/admin-OYJBR6FH.js.map", + "anchor.min.js": "/assets/js/anchor.min.js", "app.js": "/assets/js/app-SPESETTN.js", "app.map": "/assets/js/app-SPESETTN.js.map", + "uswds.js": "/assets/js/uswds-init.js", + "prism-atom.css": "/assets/styles/prism-atom-dark.css", "styles.css": "/assets/styles/styles-2K2P2X4U.css", "styles.map": "/assets/styles/styles-2K2P2X4U.css.map" } \ No newline at end of file diff --git a/_img/content/cloud-gov-pages-faster-builds-1.svg b/_img/content/cloud-gov-pages-faster-builds-1.svg new file mode 100644 index 0000000..11b438b --- /dev/null +++ b/_img/content/cloud-gov-pages-faster-builds-1.svg @@ -0,0 +1,83 @@ + + + \ No newline at end of file diff --git a/_img/content/could-gov-pages-faster-builds-2.svg b/_img/content/could-gov-pages-faster-builds-2.svg new file mode 100644 index 0000000..5013a6f --- /dev/null +++ b/_img/content/could-gov-pages-faster-builds-2.svg @@ -0,0 +1,80 @@ + + + \ No newline at end of file diff --git a/_includes/layouts/post.html b/_includes/layouts/post.html index de204a4..1a1b694 100644 --- a/_includes/layouts/post.html +++ b/_includes/layouts/post.html @@ -17,6 +17,11 @@

{{title}}

{{ content }} + +
+
+

Suggest edits

+
diff --git a/content/news/articles/2015-09-14-sprint-5-update.md b/content/news/articles/2015-09-14-sprint-5-update.md index aeb19b6..68c9753 100644 --- a/content/news/articles/2015-09-14-sprint-5-update.md +++ b/content/news/articles/2015-09-14-sprint-5-update.md @@ -14,18 +14,18 @@ Now you can view log and event data for your apps and adjust permissions for you When you take a look at the details for an application via the [cloud.gov console](http://console.cloud.gov), you'll now be able to see any recent logs generated by your application, as well as a list of recent deployment events from cloud.gov itself. ### Adjust permissions for your orgs and spaces in the console It's now possible to inspect and adjust the permissions for the individual orgs and spaces you control. ### Updates now published via the cloud.gov website diff --git a/content/news/articles/2017-02-02-fedramp-authorized.md b/content/news/articles/2017-02-02-fedramp-authorized.md index 08580f4..399d380 100644 --- a/content/news/articles/2017-02-02-fedramp-authorized.md +++ b/content/news/articles/2017-02-02-fedramp-authorized.md @@ -24,7 +24,7 @@ We’ve been making changes to the cloud.gov website in order to make our [prici #### A more functional dashboard for using cloud.gov without using the command line Our web-based [dashboard](https://dashboard.fr.cloud.gov/) gives people an easy web-based way to manage their applications. You can see an overview of your apps, spaces, and their current state. The dashboard now offers more visual clarity between activities. And now you can edit limits on your applications with a few clicks. -![Demonstration of edit mode on the cloud.gov dashboard app panel. User clicks “Modify allocation and scale” to change their application’s allocated memory and disk space.](../../img/cloud-gov_editapplimits.gif "Editing app limits in the dashboard") +![Demonstration of edit mode on the cloud.gov dashboard app panel. User clicks “Modify allocation and scale” to change their application’s allocated memory and disk space.]({{site.baseurl}}/img/cloud-gov_editapplimits.gif "Editing app limits in the dashboard") ### Interested in using cloud.gov? diff --git a/content/news/articles/2017-05-24-get-what-you-need.md b/content/news/articles/2017-05-24-get-what-you-need.md index bfca305..344163a 100644 --- a/content/news/articles/2017-05-24-get-what-you-need.md +++ b/content/news/articles/2017-05-24-get-what-you-need.md @@ -13,7 +13,7 @@ redirect_from: The dashboard is the web-based interface for managing apps and services on cloud.gov. With the dashboard, you don’t need to use the command line to handle some of the basic tasks of managing applications on the platform. You can orient yourself more easily now with information we’ve added to some of the dashboard’s core tools. Meaningful error messages (for example, alerts about data retrieval issues) can help you troubleshoot. Prompts in empty fields (for example, an empty list of applications or users) help you figure out how to get started. If you have a cloud.gov account, [log in to get started](https://dashboard.fr.cloud.gov/). If you don’t but you have a federal government email address, you can [create a free sandbox](https://account.fr.cloud.gov/signup) to explore. -![Example of the text prompt that appears to someone who is the only user in their organization. It describes the user's ability to invite other users and then offers a link to more information about how to do so.](../../img/only_org_user.png) +![Example of the text prompt that appears to someone who is the only user in their organization. It describes the user's ability to invite other users and then offers a link to more information about how to do so.]({{site.baseurl}}/img/only_org_user.png) _If you’re the only user in your organization, this prompt helps you figure out how to add more users. cloud.gov now has more information like this to help you orient yourself._ #### Strengthen your cloud.gov know-how with Cloud Foundry diff --git a/content/news/articles/2017-08-11-continuous-improvement-more-tools-help-use-cloud-gov.md b/content/news/articles/2017-08-11-continuous-improvement-more-tools-help-use-cloud-gov.md index 70fd171..35734f1 100644 --- a/content/news/articles/2017-08-11-continuous-improvement-more-tools-help-use-cloud-gov.md +++ b/content/news/articles/2017-08-11-continuous-improvement-more-tools-help-use-cloud-gov.md @@ -13,7 +13,7 @@ Every quarter we update you with the important news about new features and updat Managing users in your organization and granting them the permissions they need should be a straightforward process so your team can get to work building your app on cloud.gov. To make it easier for you and us, we built new features for inviting new users and giving them roles within your organization using the dashboard. With these changes, it's easy for even the least technical people on your team to invite new folks and manage their roles. -!["The user invitation screen with notification"](../../img/invite-users.png){:width=624,height=272} +!["The user invitation screen with notification"]({{site.baseurl}}/img/invite-users.png){:width=624,height=272} #### Continuous improvement @@ -47,10 +47,10 @@ If you have leftover funds at the end of the fiscal year and need a prototyping The Federal Bureau of Investigation (FBI) recently launched their new Crime Data Explorer (CDE) on cloud.gov. 18F and the FBI partnered to make crime data more accessible to the American public. The CDE enables users to visualize national, state, and local crime trends and offers bulk datasets and an open API for more detailed views of the data. Check it out at: [https://crime-data-explorer.fr.cloud.gov/](https://crime-data-explorer.fr.cloud.gov/) -!["the fbi crime data explorer homepage" width="624" height="320"](../../img/ fbi-crime-data.png) +!["the fbi crime data explorer homepage" width="624" height="320"]({{site.baseurl}}/img/ fbi-crime-data.png) #### Federal Election Commission The Federal Election Commission (FEC) recently relaunched their flagship website, fec.gov, with cloud.gov. The FEC collects financial reports for all federal elections and discloses fundraising figures to the public. By hosting FEC.gov on cloud.gov and moving its data to the cloud, the FEC anticipates saving 85% in hosting costs and is better prepared for peak traffic events. Read a case study about the FEC here: [{{ site.baseurl }}/overview/customer-stories/fec/]({{ site.baseurl }}/overview/customer-stories/fec/) and check out their new, cloud.gov-hosted website at [https://www.fec.gov](https://www.fec.gov) -!["the new cloud.gov hosted fec homepage" width="624" height="320"](../../img/ fec-screen.png) +!["the new cloud.gov hosted fec homepage" width="624" height="320"]({{site.baseurl}}/img/ fec-screen.png) diff --git a/content/news/articles/2017-08-16-release-notes.md b/content/news/articles/2017-08-16-release-notes.md index 7078d06..4ad4c0c 100644 --- a/content/news/articles/2017-08-16-release-notes.md +++ b/content/news/articles/2017-08-16-release-notes.md @@ -18,7 +18,7 @@ Curious what’s new that you might find helpful as a cloud.gov user? Here are h ### Changed * On the dashboard, new error messages alert you when you try to remove someone from your organization who still has roles in your spaces. -
![remove space user dashboard screen](../../img/remove-space-user.png) +
![remove space user dashboard screen]({{site.baseurl}}/img/remove-space-user.png) * Visualization of platform uptime available from the [cloud.gov status page](https://cloudgov.statuspage.io/). You can see current and the previous 90 days uptime for customer applications, API, dashboard, and many other components of the cloud.gov platform. ### Platform releases diff --git a/content/news/articles/2017-11-20-release-notes-buildpacks-volume-services-other-new-features.md b/content/news/articles/2017-11-20-release-notes-buildpacks-volume-services-other-new-features.md index 25a5fb1..77b0226 100644 --- a/content/news/articles/2017-11-20-release-notes-buildpacks-volume-services-other-new-features.md +++ b/content/news/articles/2017-11-20-release-notes-buildpacks-volume-services-other-new-features.md @@ -21,7 +21,7 @@ We’ve been hard at work shipping out new features to help you make your apps b Thanks to our antipodal compatriots with the [Australian Government Digital Transformation Agency](https://www.dta.gov.au/what-we-do/platforms/cloud/) for this code contribution. -!["Screenshot of the environment variable editing view on the dashboard in which a user-defined environment variable with the name 'app_version' has been assigned the value '1.0.1'"](../../img/dashboard-envs.png) +!["Screenshot of the environment variable editing view on the dashboard in which a user-defined environment variable with the name 'app_version' has been assigned the value '1.0.1'"]({{site.baseurl}}/img/dashboard-envs.png) ### Updates diff --git a/content/news/articles/2018-02-13-elasticsearch-56-upcoming-cloud-foundry-summit-and-platform-updates.md b/content/news/articles/2018-02-13-elasticsearch-56-upcoming-cloud-foundry-summit-and-platform-updates.md index 265cfe8..29e24d5 100644 --- a/content/news/articles/2018-02-13-elasticsearch-56-upcoming-cloud-foundry-summit-and-platform-updates.md +++ b/content/news/articles/2018-02-13-elasticsearch-56-upcoming-cloud-foundry-summit-and-platform-updates.md @@ -7,7 +7,7 @@ redirect_from: - /updates/2018-02-13-elasticsearch-56-upcoming-cloud-foundry-summit-and-platform-updates/ --- -!["FEC case study illustration"](../../img/"fec-case-study-illo.svg") +!["FEC case study illustration"]({{site.baseurl}}/img/"fec-case-study-illo.svg") ### Announcements - **In this featured [FEC Case Study]({{ site.baseurl }}/overview/customer-stories/fec/)**, find out how cloud.gov helps the agency ensure their applications are available, secure, and resilient. Want us to feature your agency? Drop us a line at [inquiries@cloud.gov](mailto:inquiries@cloud.gov?subject="Case%20Study"). diff --git a/content/news/articles/2019-02-26-quarterly-update.md b/content/news/articles/2019-02-26-quarterly-update.md index b741fe8..e4af922 100644 --- a/content/news/articles/2019-02-26-quarterly-update.md +++ b/content/news/articles/2019-02-26-quarterly-update.md @@ -57,7 +57,7 @@ There’s no denying the deep and abiding love that data analytics folks have fo Many customers have told us they want to deploy apps built using R and Shiny on cloud.gov, and now it’s possible! Check out the [new R buildpack](https://docs.cloudfoundry.org/buildpacks/r/index.html). We’ve also published [a demonstration](https://github.com/18f/cf-rshiny-demo) showing how to run the the movie explorer application from the official [Shiny examples](https://github.com/rstudio/shiny-examples), pictured below. -!["R Shiny movie explorer application screenshot"](../../img/"r-shiny-demo.png"){:style="border:1px solid grey;"} +!["R Shiny movie explorer application screenshot"]({{site.baseurl}}/img/"r-shiny-demo.png"){:style="border:1px solid grey;"} ### Build edge-facing web engineering apps using the NGINX buildpack diff --git a/content/news/articles/2019-05-13-cflinuxfs2-final-warning.md b/content/news/articles/2019-05-13-cflinuxfs2-final-warning.md index 7a937c1..e8aa9cd 100644 --- a/content/news/articles/2019-05-13-cflinuxfs2-final-warning.md +++ b/content/news/articles/2019-05-13-cflinuxfs2-final-warning.md @@ -30,11 +30,11 @@ We are also explicitly emailing people with administrative control over applicat **How to change the stack:** If you use a manifest for deployment, edit your application manifest to [set the `stack:`](https://docs.cloudfoundry.org/devguide/deploy-apps/manifest-attributes.html#stack) to cflinuxfs3. For example: -``` +```shell stack: cflinuxfs3 ``` If you don’t use a manifest for deployment, add the `-s` command-line parameter to the push command in your deployment script. For example: -``` +```shell cf push YOUR-APPNAME-HERE -s cflinuxfs3 ``` In either case: after making that update, redeploy the app. diff --git a/content/news/articles/2019-08-26-changes-to-cloud-gov-services-and-prices.md b/content/news/articles/2019-08-26-changes-to-cloud-gov-services-and-prices.md index d935cdd..291a2ef 100644 --- a/content/news/articles/2019-08-26-changes-to-cloud-gov-services-and-prices.md +++ b/content/news/articles/2019-08-26-changes-to-cloud-gov-services-and-prices.md @@ -37,12 +37,11 @@ Resource | Previous monthly price | New monthly price | - Previously, cloud.gov provided RDS, S3, Elasticsearch, and Redis at no additional cost for a “limited time.” We will continue to provide these services at no additional cost as long as your memory quota remains below the following limits. - - | Previous storage cap | New storage cap | Additional Storage - --------- | ----------- | ----- | ----- - `RDS` | unspecified | 1 TB | $300 per terabyte/month - `S3` | unspecified | 5 TB | $100 per terabyte/month - `Redis` | 10 GB | 10 GB | $100 per gigabyte/month - `ElasticSearch` | 10 GB | 10 GB | $100 per gigabyte/month +| | Previous storage cap | New storage cap | Additional Storage | +| --------- |----------------------| ----- | ----- | +| `RDS` | unspecified | 1 TB | $300 per terabyte/month | +| `S3` | unspecified | 5 TB | $100 per terabyte/month | +| `Redis` | 10 GB | 10 GB | $100 per gigabyte/month | +| `ElasticSearch` | 10 GB | 10 GB | $100 per gigabyte/month | If you have questions or want a customized cost projection for your agreement, email us at [inquiries@cloud.gov](mailto:inquiries@cloud.gov) and we’ll be happy to help. diff --git a/content/news/articles/2020-04-28-changes-to-cloud-govs-existing-cdn-and-custom-domain-services.md b/content/news/articles/2020-04-28-changes-to-cloud-govs-existing-cdn-and-custom-domain-services.md index aff6734..5f7d213 100644 --- a/content/news/articles/2020-04-28-changes-to-cloud-govs-existing-cdn-and-custom-domain-services.md +++ b/content/news/articles/2020-04-28-changes-to-cloud-govs-existing-cdn-and-custom-domain-services.md @@ -28,7 +28,7 @@ Service brokers are a fundamental part of the cloud.gov platform. They allow dev You can see the cdn and domains services in the [Dashboard](https://dashboard.fr.cloud.gov/), or by running cf marketplace from the command line: -``` +```shell $ cf marketplace cdn-route Custom domains, CDN caching, and TLS certificates with automatic renewal cdn-broker diff --git a/content/news/articles/2021-07-02-migrating-from-legacy-drupal-to-federalist.md b/content/news/articles/2021-07-02-migrating-from-legacy-drupal-to-federalist.md index 85fccd4..0a7aa91 100644 --- a/content/news/articles/2021-07-02-migrating-from-legacy-drupal-to-federalist.md +++ b/content/news/articles/2021-07-02-migrating-from-legacy-drupal-to-federalist.md @@ -10,7 +10,7 @@ excerpt: "With the end of life dates for Drupal versions 7 and 8 fast approachin Drupal is a commonly used content management system (CMS) in the Federal government. Many existing Drupal sites are still using older, outdated versions of the CMS and site owners may be facing challenges with upgrading to the latest version. In addition, because Drupal is a multi-tiered web application, it has multiple components that must be managed and maintained, adding to complexity and support costs. -With the [end of life dates for Drupal versions 7 and 8 fast approaching](https://www.drupal.org/psa-2020-06-24){:target="_blank"}, Drupal site owners should understand the options they have for migrating to new, simplified, more modern web platforms. This post will discuss migrating from Drupal to the Federalist platform, and will run through a simple example of how such a migration can be accomplished. +With the [end of life dates for Drupal versions 7 and 8 fast approaching](https://www.drupal.org/psa-2020-06-24), Drupal site owners should understand the options they have for migrating to new, simplified, more modern web platforms. This post will discuss migrating from Drupal to the Federalist platform, and will run through a simple example of how such a migration can be accomplished. This post will demonstrate how to use some of the commonly available Drupal migration tools to export content from a legacy Drupal site and import the content to a new Federalist starter template. We will discuss some of the issues that Drupal site owners should evaluate when considering a migration to a new platform. @@ -18,7 +18,7 @@ This post will demonstrate how to use some of the commonly available Drupal migr The end of life date for both Drupal 7 and 8 is fast approaching. Drupal 8 will reach it's scheduled end of life on November 2, 2021. Drupal 7 wil reach it's scheduled end of life on November 28, 2022 (after being extended for a period of about 1 year). -As the challenges and work required to upgrade to the latest version of Drupal are considered by agencies, other platform options may also be evaluated. One potential option for current Drupal users is the [Federalist platform](https://cloud.gov/pages/){:target="_blank"}. +As the challenges and work required to upgrade to the latest version of Drupal are considered by agencies, other platform options may also be evaluated. One potential option for current Drupal users is the [Federalist platform](https://cloud.gov/pages/). ## What is Federalist? @@ -85,14 +85,14 @@ The cloud.gov and Pages team is ready to help you as you evaluate your options f In addition, the following resources are also available for agencies: -* [Pages](https://pages.cloud.gov/){:target="_blank"} +* [Pages](https://pages.cloud.gov/) * Static site generators - - [Tome](https://tome.fyi/){:target="_blank"} - - [Netlify](https://www.netlify.com/){:target="_blank"} - - [Hugo](https://gohugo.io/){:target="_blank"} - - [Gatsby](https://www.gatsbyjs.com/){:target="_blank"} + - [Tome](https://tome.fyi/) + - [Netlify](https://www.netlify.com/) + - [Hugo](https://gohugo.io/) + - [Gatsby](https://www.gatsbyjs.com/) * Drupal export / migration tools: - - [Markdown Exporter](https://www.drupal.org/project/markdown_exporter){:target="_blank"} - - [Migrate Git](https://www.drupal.org/project/migrate_git){:target="_blank"} + - [Markdown Exporter](https://www.drupal.org/project/markdown_exporter) + - [Migrate Git](https://www.drupal.org/project/migrate_git) Questions or inquiries can be sent to [federalist-inquiries@gsa.gov](mailto:federalist-inquiries@gsa.gov). diff --git a/content/news/articles/2022-02-09-sharing-service-instances.md b/content/news/articles/2022-02-09-sharing-service-instances.md index fcef9cc..fbe52fa 100644 --- a/content/news/articles/2022-02-09-sharing-service-instances.md +++ b/content/news/articles/2022-02-09-sharing-service-instances.md @@ -19,16 +19,16 @@ We are happy to announce that [service instance sharing](https://docs.cloudfound * A developer uses the standard `cf create-service` command to instantiate a new service instance in a particular space. * When initially created, viewing the service details via `cf service {service_name}` will indicate that the service is not currently shared with any other spaces (see below). -!["Showing details of a service that is not shared"](../../img/service-not-shared.png) +!["Showing details of a service that is not shared"]({{site.baseurl}}/img/service-not-shared.png) * A developer can share a service instance created in one space with another space - provided that they have the Space Developer role in _both_ spaces - by using `cf share-service {service_name} -s {other-space}` * Once the service instance is shared, viewing the service details via `cf service {service_name}` **in the space it was created in** will indicate which other spaces it is shared with and the number of bound apps (see below). -!["Showing details of a service that is shared"](../../img/service-shared.png) +!["Showing details of a service that is shared"]({{site.baseurl}}/img/service-shared.png) * Viewing the service details **in the space the service was shared with** indicates that this is a shared service, and the org/space the service it was shared from (see below). -!["Showing service details from another space"](../../img/show-service-details.png) +!["Showing service details from another space"]({{site.baseurl}}/img/show-service-details.png) ### Security considerations diff --git a/content/news/articles/2023-02-23-cloud-gov-pages-faster-builds.md b/content/news/articles/2023-02-23-cloud-gov-pages-faster-builds.md index 821037b..36d8ba6 100644 --- a/content/news/articles/2023-02-23-cloud-gov-pages-faster-builds.md +++ b/content/news/articles/2023-02-23-cloud-gov-pages-faster-builds.md @@ -6,102 +6,34 @@ date: 2023-02-23 excerpt: We advertise that cloud.gov Pages, previously known as Federalist, can “securely deploy a website from your repository in minutes.” Getting your content on the web quickly, seeing fast previews, and even seeing errors early are all important to good maintenance of a website --- -We advertise that [cloud.gov Pages](https://cloud.gov/pages), previously known as Federalist, can “securely deploy a website from your repository in minutes.” Getting your content on the web quickly, seeing fast previews, and even seeing errors early are all important to good maintenance of a website. But as sites become larger and more complex, this can be a difficult task. We’ve made two recent changes to cloud.gov Pages to make website deployment faster so you can focus on your code, design, and content. +We advertise that [cloud.gov Pages](https://cloud.gov/pages), previously known as Federalist, can “securely deploy a +website from your repository in minutes.” Getting your content on the web quickly, seeing fast previews, and even seeing +errors early are all important to good maintenance of a website. But as sites become larger and more complex, this can +be a difficult task. We’ve made two recent changes to cloud.gov Pages to make website deployment faster so you can focus +on your code, design, and content. ## Publishing improvements -Static site generators, like those frequently used with cloud.gov Pages, generate each website page in advance. We then copy each page to our hosting service so it can appear online. If we want to save time, we can choose to only copy the page if we can tell that it changed from the previous build. +Static site generators, like those frequently used with cloud.gov Pages, generate each website page in advance. We then +copy each page to our hosting service so it can appear online. If we want to save time, we can choose to only copy the +page if we can tell that it changed from the previous build. -Starting in late 2020, cloud.gov Pages was publishing every file individually. We did this because a new feature for [adding headers](https://cloud.gov/pages/documentation/custom-headers/) prevented us from quickly comparing whether files had changed. This past October, we made a change to return to only publishing changed files if sites weren’t using the header feature. +Starting in late 2020, cloud.gov Pages was publishing every file individually. We did this because a new feature +for [adding headers](https://cloud.gov/pages/documentation/custom-headers/) prevented us from quickly comparing whether +files had changed. This past October, we made a change to return to only publishing changed files if sites weren’t using +the header feature. -Sites like [Digital.gov](https://digital.gov/), with over 20,000 files, had been taking seventeen minutes on each build! Now their production builds only update about one-third of the total files and have brought the build times down to seven or eight minutes (fresh preview builds still take about fourteen). Across our whole portfolio, production sites saw 25% faster builds, saving 1 minute 40 seconds on average. +Sites like [Digital.gov](https://digital.gov/), with over 20,000 files, had been taking seventeen minutes on each build! +Now their production builds only update about one-third of the total files and have brought the build times down to +seven or eight minutes (fresh preview builds still take about fourteen). Across our whole portfolio, production sites +saw 25% faster builds, saving 1 minute 40 seconds on average.

Median Build Times (in minutes) for Digital.gov by Month

Digital.gov was taking seventeen minutes to build on cloud.gov Pages with most of the time spent uploading new files. After the October release of publishing improvements, build times were reduced to about seven or eight minutes.

- - - +!["Chart - Faster Builds"]({{site.baseurl}}/img/content/cloud-gov-pages-faster-builds-1.svg) @@ -139,96 +71,25 @@ Sites like [Digital.gov](https://digital.gov/), with over 20,000 files, had been ## Caching build dependencies -Sites were installing all required custom software dependencies on each build. This process commonly takes about two or three minutes. We replaced this step with a new, opt-out, caching strategy: -- If your dependencies didn’t change from the previous build, we’ll re-download the prior package from a secure cache. This takes about fifteen seconds +Sites were installing all required custom software dependencies on each build. This process commonly takes about two or +three minutes. We replaced this step with a new, opt-out, caching strategy: + +- If your dependencies didn’t change from the previous build, we’ll re-download the prior package from a secure cache. + This takes about fifteen seconds - If your dependencies did change, which doesn’t happen often, we’ll re-install them. -- Because downloading dependencies from a cache can create some errors, we have an [option to opt-out](https://cloud.gov/pages/documentation/cache-dependencies/#configuration). +- Because downloading dependencies from a cache can create some errors, we have + an [option to opt-out](https://cloud.gov/pages/documentation/cache-dependencies/#configuration). -We just recently added this change, so we’re still waiting to see the full metrics on how it’s improved build time. But many sites using the popular [Jekyll framework](https://jekyllrb.com/) have seen their build time reduced by about three minutes. You can see the effect of both of these changes in our median build time since June of last year: +We just recently added this change, so we’re still waiting to see the full metrics on how it’s improved build time. But +many sites using the popular [Jekyll framework](https://jekyllrb.com/) have seen their build time reduced by about three +minutes. You can see the effect of both of these changes in our median build time since June of last year:

Median Build Times (in minutes) for cloud.gov Pages Sites by Month

Sites were taking about six minutes to build in mid-2022. Publishing improvements in October helped reduce the time by about two minutes. Caching improvements in January reduced the build time by about another minute.

- - - +!["Chart - Faster Builds 2"]({{site.baseurl}}/img/content/could-gov-pages-faster-builds-2.svg)
Median Build Times for Digital.gov by Month
diff --git a/content/news/articles/2023-03-28-cflinuxfs3-deprecation.md b/content/news/articles/2023-03-28-cflinuxfs3-deprecation.md index 7cd916f..763ef01 100644 --- a/content/news/articles/2023-03-28-cflinuxfs3-deprecation.md +++ b/content/news/articles/2023-03-28-cflinuxfs3-deprecation.md @@ -30,7 +30,7 @@ However, there may be exceptions! For example, you may have used the `apt-buildp If you are using buildpacks to build your apps, you should try out the new cflinuxfs4 stack before we make it the default on April 27th. Check out the [Cloud Foundry stack docs](https://docs.cloudfoundry.org/devguide/deploy-apps/stacks.html) to see how. To change your stack and re-push your app, run the following command: -``` +```shell cf push MY-APP -s cflinuxfs4 ``` @@ -39,7 +39,7 @@ cf push MY-APP -s cflinuxfs4 If you find problems, you can continue using the deprecated cflinuxfs3 stack until you’ve resolved any issues and are ready to transition your apps. After April 27th you can use the following command to temporarily use the older stack: -``` +```shell cf push MY-APP -s cflinuxfs3 ``` @@ -59,7 +59,7 @@ To quickly see the which of your applications are still using `cflinuxfs3`, the -``` +```shell cf curl "/v3/apps?per_page=5000&include=space.organization" | jq '(.included.spaces | INDEX(.guid)) as $spaces | (.included.organizations | INDEX(.guid)) as $orgs | [ .resources[] | select(.lifecycle.data.stack == "cflinuxfs3") | {app: .name, org:$orgs[$spaces[.relationships.space.data.guid].relationships.organization.data.guid].name ,space: $spaces[.relationships.space.data.guid].name , lifecycle} ]' ``` diff --git a/content/news/articles/2023-04-27-cflinuxfs3-deprecation-update.md b/content/news/articles/2023-04-27-cflinuxfs3-deprecation-update.md index 727be33..ee700f4 100644 --- a/content/news/articles/2023-04-27-cflinuxfs3-deprecation-update.md +++ b/content/news/articles/2023-04-27-cflinuxfs3-deprecation-update.md @@ -27,7 +27,7 @@ For existing applications which were created under `cflinuxfs3` you will need to 1. Push the app manually and specify the stack with the cf cli: - ``` + ```shell cf push MY-APP -s cflinuxfs4 ``` @@ -44,7 +44,7 @@ For existing applications which were created under `cflinuxfs3` you will need to For any new applications, simply run a `cf push` to pick up the new `cflinuxfs4` stack: -``` +```shell cf push MY-APP ``` diff --git a/content/news/articles/2023-05-16-cflinuxfs3-buildpack-deprecation.md b/content/news/articles/2023-05-16-cflinuxfs3-buildpack-deprecation.md index 90ce391..034234e 100644 --- a/content/news/articles/2023-05-16-cflinuxfs3-buildpack-deprecation.md +++ b/content/news/articles/2023-05-16-cflinuxfs3-buildpack-deprecation.md @@ -1,7 +1,7 @@ --- layout: layouts/post tags: news -date: "2023-05-16" +date: 2023-05-16 title: "Deprecation Notice for cflinuxfs3 stack and cflinuxfs3 Buildpacks" excerpt: cflinuxfs4 buildpacks are here and cflinuxfs3 buildpacks are retiring, upgrade your apps now! --- @@ -36,7 +36,7 @@ For existing applications which were created under `cflinuxfs3` you will need to 1. Push the app manually and specify the stack with the cf cli: - ``` + ```shell cf push MY-APP -s cflinuxfs4 ``` @@ -53,7 +53,7 @@ For existing applications which were created under `cflinuxfs3` you will need to For any new applications, simply run a `cf push` to pick up the new `cflinuxfs4` stack: -``` +```shell cf push MY-APP ``` @@ -61,7 +61,7 @@ cf push MY-APP Until September 28th, 2023, you can use an external buildpack to push apps to the cflinuxfs3 stack by referencing a URL in a `cf push` command. As an example, to push a Ruby app using 2.7.6 on cflinuxfs3: -``` +```shell cf push MY-APP -b https://github.com/cloudfoundry/ruby-buildpack/releases/download/v1.9.4/ruby-buildpack-cflinuxfs3-v1.9.4.zip -s cflinuxfs3 ``` diff --git a/content/news/articles/2023-05-30-cloud-gov-pages-jekyll-ruby-upgrade.md b/content/news/articles/2023-05-30-cloud-gov-pages-jekyll-ruby-upgrade.md index d5bd3d4..2bae558 100644 --- a/content/news/articles/2023-05-30-cloud-gov-pages-jekyll-ruby-upgrade.md +++ b/content/news/articles/2023-05-30-cloud-gov-pages-jekyll-ruby-upgrade.md @@ -33,7 +33,7 @@ We’ve documented the migration process in a [PR to our deprecated jekyll templ - [The hard step] Replace the primary functionality of jekyll-assets: - First move everything from the `_assets` folder to the `assets` folder - - Remove any uses of the {% raw %}`{% asset %}`{% endraw %} liquid tag or `asset_url` function in your content. This tag and function provided a way to find a given asset in any of multiple specified site folders. You’ll likely want to replace this with {% raw %} `../../img/example.png` or `{{ /assets/example.png | relative_url }}`{% endraw %} where `example.png` is the name of the example file. + - Remove any uses of the {% raw %}`{% asset %}`{% endraw %} liquid tag or `asset_url` function in your content. This tag and function provided a way to find a given asset in any of multiple specified site folders. You’ll likely want to replace this with {% raw %} `{{site.baseurl}}/img/example.png` or `{{ /assets/example.png | relative_url }}`{% endraw %} where `example.png` is the name of the example file. - Move all SASS partials to a new folder called `_sass`. You can leave the entrypoint SASS file (styles.scss) in `assets/css` but you’ll need to add [two sets of triple dashes to the start of the file](https://jekyllrb.com/docs/assets/). - Add our two helper jekyll plugins to the `_plugins` folder: - [`asset-helper.rb`](https://github.com/cloud-gov/pages-uswds-jekyll/blob/main/_plugins/asset-helper.rb) copies USWDS assets from the `node_modules` folder into your `assets` folder @@ -41,7 +41,7 @@ We’ve documented the migration process in a [PR to our deprecated jekyll templ - You’ll need to update `_config.yml` to reflect passing configuration options to our new plugins instead of `jekyll-assets`. You can see an [example configuration change in our template PR](https://github.com/cloud-gov/pages-uswds-jekyll/pull/314/files#diff-ecec67b0e1d7e17a83587c6d27b6baaaa133f42482b07bd3685c77f34b62d883). - Add a new empty file called `.gitkeep` in `assets/uswds` and then add these three lines to `.gitignore` to ignore temporary USWDS assets during the build: - ``` + ```shell assets/uswds/* !assets/uswds/.gitkeep assets/js/uswds* diff --git a/content/news/articles/2024-05-30-release-notes.md b/content/news/articles/2024-05-30-release-notes.md index 5b98181..22ddd89 100644 --- a/content/news/articles/2024-05-30-release-notes.md +++ b/content/news/articles/2024-05-30-release-notes.md @@ -47,7 +47,7 @@ This release contains support for Tomcat 10.1 in the form of a new version line, The default version of Tomcat will remain at 9.x, but you can now specify 10.1.x to be used by the buildpack, in the same way as changing the JRE version. -```bash +```shell cf set-env JBP_CONFIG_TOMCAT '{ tomcat: { version: 10.1.+ } }' ```
Median Build Times for cloud.gov Pages Sites by Month