diff --git a/.vscode/settings.json b/.vscode/settings.json new file mode 100644 index 0000000..521a729 --- /dev/null +++ b/.vscode/settings.json @@ -0,0 +1,11 @@ +{ + "editor.columnSelection": true, + "editor.defaultColorDecorators": true, + "editor.experimental.asyncTokenizationLogging": true, + "editor.experimental.asyncTokenizationVerification": true, + "editor.suggest.preview": true, + "editor.suggest.showStatusBar": true, + "files.autoGuessEncoding": true, + "testing.automaticallyOpenPeekViewDuringAutoRun": true, + "testing.alwaysRevealTestOnStateChange": true +} \ No newline at end of file diff --git a/CNAME b/CNAME index c8f1ecd..d64b9fe 100644 --- a/CNAME +++ b/CNAME @@ -1,2 +1,2 @@ -igecloud.dev/creativestudio -igecloud.com/creativestudio +igecloud.dev/creativecloud +igecloud.dev/developerscloud diff --git a/CODEOWNERS b/CODEOWNERS index f9ed0b9..d4f7b70 100644 --- a/CODEOWNERS +++ b/CODEOWNERS @@ -1 +1 @@ -* @devcontainers/maintainers +* @igeclouds/developers diff --git a/_includes/footer.html b/_includes/footer.html index c97cef0..cec530e 100644 --- a/_includes/footer.html +++ b/_includes/footer.html @@ -27,10 +27,10 @@
  • - - © 2022 IGE CLOUD + © 2023 IGE CLOUD
    • diff --git a/overview.md b/overview.md index ccfb5e1..c651f75 100644 --- a/overview.md +++ b/overview.md @@ -3,30 +3,30 @@ title: Overview layout: singlePage sectionid: overview --- +## `` What are dev containers? `` -## What are development containers? As containerizing production workloads becomes commonplace, more developers are using containers for scenarios beyond deployment, including continuous integration, test automation, and even full-featured coding environments. Each scenario’s needs can vary between simple single container environments to complex, orchestrated multi-container setups. Rather than attempting to create another orchestrator format, the Development Containers Specification (or Dev Containers Spec for short) seeks to find ways to enrich existing formats with metadata for common development specific settings, tools, and configuration. -### A structured metadata format +### `` A structured metadata format `` -Like the [Language Server Protocol](https://microsoft.github.io/language-server-protocol/) before it, the first format in the specification, [`devcontainer.json`](implementors/json_reference), was born out of necessity. It is a structured JSON with Comments (jsonc) metadata format that tools can use to store any needed configuration required to develop inside of local or cloud-based containerized coding. +Like the [Language Server Protocol](https://microsoft.github.io/language-server-protocol/) before it, the first format in the specification, [`devcontainer.json`](implementors/json_reference), was born out of necessity. It is a structured JSON with Comments (jsonc) metadata format that tools can use to store any needed configuration required to develop inside of local or cloud-based containerized coding. Since the spec was initally published, Dev Container metadata can now be stored in [image labels](../implementors/spec/#image-metadata) and in reusable chunks of metadata and install scripts known as [Dev Container Features](../features). We envision that this same structured data can be embedded in other formats -- all while retaining a common object model for consistent processing. -### Development vs production +### `` Development vs production `` A Development Container defines an environment in which you develop your application before you are ready to deploy. While deployment and development containers may resemble one another, you may not want to include tools in a deployment image that you use during development. -Diagram of inner and outer loop of container-based development +`Diagram of inner and outer loop of container-based development` -### Build and test +### `` Build and test `` Beyond repeatable setup, these same development containers provide consistency to avoid environment specific problems across developers and centralized build and test automation services. The open-source [CLI reference implementation](https://github.com/devcontainers/cli) can either be used directly or integrated into product experience to use the structured metadata to deliver these benefits. It currently supports integrating with Docker Compose and a simplified, un-orchestrated single container option – so that they can be used as coding environments or for continuous integration and testing. A GitHub Action and an Azure DevOps Task are available in [devcontainers/ci](https://github.com/devcontainers/ci) for running a repository's dev container in continuous integration (CI) builds. This allows you to reuse the same setup that you are using for local development to also build and test your code in CI. -### Supporting tools +### `` Supporting tools `` You can [learn more](/supporting.md) about how other tools and services support the Development Container Specification. diff --git a/templates.html b/templates.html index 42f620b..45cc4f6 100644 --- a/templates.html +++ b/templates.html @@ -4,7 +4,7 @@ sectionid: collection-index-templates --- -

    Available Dev Container Templates

    +

    Container Templates

    This table contains all official and community-supported Dev Container Templates known at the time of crawling each registered collection. This list is continuously