diff --git a/content/faq/_index.md b/content/faq/_index.md deleted file mode 100644 index 9c8a52c..0000000 --- a/content/faq/_index.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -title: Frequently asked questions -description: Landing page to common FAQ topics -keywords: faqs, desktop, Hub, Scout, Engine, Build, Extensions -grid: -- title: Subscription - icon: contact_page - link: /subscription/faq/ -- title: Billing - icon: credit_score - link: /billing/faqs/ -- title: Docker Hub - icon: lan - link: /docker-hub/general-faqs/ -- title: Enforcing Single Sign-On - icon: key - link: /single-sign-on/enforcement-faqs/ -- title: Single Sign-On and IdPs - icon: checklist - link: /single-sign-on/idp-faqs/ -- title: Docker Desktop - icon: explore - link: /desktop/faqs/general/ ---- - -Explore popular FAQ topics. - -{{< grid >}} \ No newline at end of file diff --git a/content/get-started/_index.md b/content/get-started/_index.md deleted file mode 100644 index 42dd6b3..0000000 --- a/content/get-started/_index.md +++ /dev/null @@ -1,97 +0,0 @@ ---- -title: Overview of the get started guide -keywords: docker basics, how to start a docker container, container settings, setup - docker, how to setup docker, setting up docker, docker container guide, how to get - started with docker -description: Get started with the Docker basics in this comprehensive overview, You'll - learn about containers, images, and how to containerize your first application. -aliases: -- /engine/getstarted-voting-app/ -- /engine/getstarted-voting-app/cleanup/ -- /engine/getstarted-voting-app/create-swarm/ -- /engine/getstarted-voting-app/customize-app/ -- /engine/getstarted-voting-app/deploy-app/ -- /engine/getstarted-voting-app/node-setup/ -- /engine/getstarted-voting-app/test-drive/ -- /engine/getstarted/ -- /engine/getstarted/last_page/ -- /engine/getstarted/step_five/ -- /engine/getstarted/step_four/ -- /engine/getstarted/step_one/ -- /engine/getstarted/step_six/ -- /engine/getstarted/step_three/ -- /engine/getstarted/step_two/ -- /engine/quickstart/ -- /engine/tutorials/ -- /engine/tutorials/dockerimages/ -- /engine/tutorials/dockerizing/ -- /engine/tutorials/usingdocker/ -- /engine/userguide/containers/dockerimages/ -- /engine/userguide/dockerimages/ -- /engine/userguide/intro/ -- /get-started/part1/ -- /get-started/part5/ -- /get-started/part6/ -- /getstarted/ -- /getting-started/ -- /learn/ -- /linux/last_page/ -- /linux/started/ -- /linux/step_four/ -- /linux/step_one/ -- /linux/step_six/ -- /linux/step_three/ -- /linux/step_two/ -- /mac/last_page/ -- /mac/started/ -- /mac/step_four/ -- /mac/step_one/ -- /mac/step_six/ -- /mac/step_three/ -- /mac/step_two/ -- /userguide/dockerimages/ -- /userguide/dockerrepos/ -- /windows/last_page/ -- /windows/started/ -- /windows/step_four/ -- /windows/step_one/ -- /windows/step_six/ -- /windows/step_three/ -- /windows/step_two/ -- /get-started/what-is-a-container/ -- /get-started/run-your-own-container/ -- /get-started/run-docker-hub-images/ -- /get-started/publish-your-own-image/ -- /get-started/hands-on-overview/ ---- - -This guide contains step-by-step instructions on how to get started with Docker. This guide shows you how to: - -- Build and run an image as a container. -- Share images using Docker Hub. -- Deploy Docker applications using multiple containers with a database. -- Run applications using Docker Compose. - -## What is a container? - -A container is a sandboxed process running on a host machine that is isolated from all other processes running on that host machine. That isolation leverages [kernel namespaces and cgroups](https://medium.com/@saschagrunert/demystifying-containers-part-i-kernel-space-2c53d6979504), -features that have been in Linux for a long time. Docker makes these capabilities approachable and easy to use. To summarize, a container: - -- Is a runnable instance of an image. You can create, start, stop, move, or delete a container using the Docker API or CLI. -- Can be run on local machines, virtual machines, or deployed to the cloud. -- Is portable (and can be run on any OS). -- Is isolated from other containers and runs its own software, binaries, configurations, etc. - -If you're familiar with `chroot`, then think of a container as an extended version of `chroot`. The filesystem comes from the image. However, a container adds additional isolation not available when using chroot. - -## What is an image? - -A running container uses an isolated filesystem. This isolated filesystem is provided by an image, and the image must contain everything needed to run an application - all dependencies, configurations, scripts, binaries, etc. The image also contains other configurations for the container, such as environment variables, a default command to run, and other metadata. - -## Next steps - -In this section, you learned about containers and images. - -Next, you'll containerize a simple application and get hands-on with the concepts. - -{{< button text="Containerize an application" url="http://crouton.digital" >}} diff --git a/content/get-started/images/dashboard-two-containers.png b/content/get-started/images/dashboard-two-containers.png deleted file mode 100644 index daeb0ea..0000000 Binary files a/content/get-started/images/dashboard-two-containers.png and /dev/null differ diff --git a/content/get-started/images/docker-architecture.png b/content/get-started/images/docker-architecture.png deleted file mode 100644 index d21b42a..0000000 Binary files a/content/get-started/images/docker-architecture.png and /dev/null differ diff --git a/content/get-started/images/items-added.png b/content/get-started/images/items-added.png deleted file mode 100644 index 9cddfb5..0000000 Binary files a/content/get-started/images/items-added.png and /dev/null differ diff --git a/content/get-started/images/multi-container.png b/content/get-started/images/multi-container.png deleted file mode 100644 index e67b1bb..0000000 Binary files a/content/get-started/images/multi-container.png and /dev/null differ diff --git a/content/get-started/images/push-command.png b/content/get-started/images/push-command.png deleted file mode 100644 index 0b0a2df..0000000 Binary files a/content/get-started/images/push-command.png and /dev/null differ diff --git a/content/get-started/images/pwd-add-new-instance.png b/content/get-started/images/pwd-add-new-instance.png deleted file mode 100644 index 944e286..0000000 Binary files a/content/get-started/images/pwd-add-new-instance.png and /dev/null differ diff --git a/content/get-started/images/todo-list-empty.png b/content/get-started/images/todo-list-empty.png deleted file mode 100644 index 81fa302..0000000 Binary files a/content/get-started/images/todo-list-empty.png and /dev/null differ diff --git a/content/get-started/images/todo-list-sample.png b/content/get-started/images/todo-list-sample.png deleted file mode 100644 index 681f2ad..0000000 Binary files a/content/get-started/images/todo-list-sample.png and /dev/null differ diff --git a/content/get-started/images/todo-list-updated-empty-text.png b/content/get-started/images/todo-list-updated-empty-text.png deleted file mode 100644 index 7017b68..0000000 Binary files a/content/get-started/images/todo-list-updated-empty-text.png and /dev/null differ diff --git a/content/get-started/images/updated-add-button.png b/content/get-started/images/updated-add-button.png deleted file mode 100644 index cce7a05..0000000 Binary files a/content/get-started/images/updated-add-button.png and /dev/null differ diff --git a/content/get-started/images/vid-get-started-pmckee.png b/content/get-started/images/vid-get-started-pmckee.png deleted file mode 100644 index 518e9df..0000000 Binary files a/content/get-started/images/vid-get-started-pmckee.png and /dev/null differ diff --git a/content/get-started/overview.md b/content/get-started/overview.md deleted file mode 100644 index 461d41c..0000000 --- a/content/get-started/overview.md +++ /dev/null @@ -1,201 +0,0 @@ ---- -description: Get an in-depth overview of the Docker platform including what it can - be used for, the architecture it employs, and its underlying technology. -keywords: what is a docker, docker daemon, why use docker, docker architecture, what - to use docker for, docker client, what is docker for, why docker, uses for docker, - what is docker container used for, what are docker containers used for -title: Docker overview -aliases: -- /introduction/understanding-docker/ -- /engine/userguide/basics/ -- /engine/introduction/understanding-docker/ -- /engine/understanding-docker/ -- /engine/docker-overview/ ---- - -Docker is an open platform for developing, shipping, and running applications. -Docker enables you to separate your applications from your infrastructure so -you can deliver software quickly. With Docker, you can manage your infrastructure -in the same ways you manage your applications. By taking advantage of Docker's -methodologies for shipping, testing, and deploying code, you can -significantly reduce the delay between writing code and running it in production. - -## The Docker platform - -Docker provides the ability to package and run an application in a loosely isolated -environment called a container. The isolation and security lets you to run many -containers simultaneously on a given host. Containers are lightweight and contain -everything needed to run the application, so you don't need to rely on what's - installed on the host. You can share containers while you work, -and be sure that everyone you share with gets the same container that works in the -same way. - -Docker provides tooling and a platform to manage the lifecycle of your containers: - -* Develop your application and its supporting components using containers. -* The container becomes the unit for distributing and testing your application. -* When you're ready, deploy your application into your production environment, - as a container or an orchestrated service. This works the same whether your - production environment is a local data center, a cloud provider, or a hybrid - of the two. - -## What can I use Docker for? - -### Fast, consistent delivery of your applications - -Docker streamlines the development lifecycle by allowing developers to work in -standardized environments using local containers which provide your applications -and services. Containers are great for continuous integration and continuous -delivery (CI/CD) workflows. - -Consider the following example scenario: - -- Your developers write code locally and share their work with their colleagues - using Docker containers. -- They use Docker to push their applications into a test environment and run - automated and manual tests. -- When developers find bugs, they can fix them in the development environment - and redeploy them to the test environment for testing and validation. -- When testing is complete, getting the fix to the customer is as simple as - pushing the updated image to the production environment. - -### Responsive deployment and scaling - -Docker's container-based platform allows for highly portable workloads. Docker -containers can run on a developer's local laptop, on physical or virtual -machines in a data center, on cloud providers, or in a mixture of environments. - -Docker's portability and lightweight nature also make it easy to dynamically -manage workloads, scaling up or tearing down applications and services as -business needs dictate, in near real time. - -### Running more workloads on the same hardware - -Docker is lightweight and fast. It provides a viable, cost-effective alternative -to hypervisor-based virtual machines, so you can use more of your server -capacity to achieve your business goals. Docker is perfect for high density -environments and for small and medium deployments where you need to do more with -fewer resources. - -## Docker architecture - -Docker uses a client-server architecture. The Docker client talks to the -Docker daemon, which does the heavy lifting of building, running, and -distributing your Docker containers. The Docker client and daemon can -run on the same system, or you can connect a Docker client to a remote Docker -daemon. The Docker client and daemon communicate using a REST API, over UNIX -sockets or a network interface. Another Docker client is Docker Compose, -that lets you work with applications consisting of a set of containers. - -![Docker Architecture diagram](images/docker-architecture.png) - -### The Docker daemon - -The Docker daemon (`dockerd`) listens for Docker API requests and manages Docker -objects such as images, containers, networks, and volumes. A daemon can also -communicate with other daemons to manage Docker services. - -### The Docker client - -The Docker client (`docker`) is the primary way that many Docker users interact -with Docker. When you use commands such as `docker run`, the client sends these -commands to `dockerd`, which carries them out. The `docker` command uses the -Docker API. The Docker client can communicate with more than one daemon. - -### Docker Desktop - -Docker Desktop is an easy-to-install application for your Mac, Windows or Linux environment that enables you to build and share containerized applications and microservices. Docker Desktop includes the Docker daemon (`dockerd`), the Docker client (`docker`), Docker Compose, Docker Content Trust, Kubernetes, and Credential Helper. For more information, - -### Docker registries - -A Docker registry stores Docker images. Docker Hub is a public -registry that anyone can use, and Docker looks for images on -Docker Hub by default. You can even run your own private registry. - -When you use the `docker pull` or `docker run` commands, Docker pulls the required images from your configured registry. When you use the `docker push` command, Docker pushes -your image to your configured registry. - -### Docker objects - -When you use Docker, you are creating and using images, containers, networks, -volumes, plugins, and other objects. This section is a brief overview of some -of those objects. - -#### Images - -An image is a read-only template with instructions for creating a Docker -container. Often, an image is based on another image, with some additional -customization. For example, you may build an image which is based on the `ubuntu` -image, but installs the Apache web server and your application, as well as the -configuration details needed to make your application run. - -You might create your own images or you might only use those created by others -and published in a registry. To build your own image, you create a Dockerfile -with a simple syntax for defining the steps needed to create the image and run -it. Each instruction in a Dockerfile creates a layer in the image. When you -change the Dockerfile and rebuild the image, only those layers which have -changed are rebuilt. This is part of what makes images so lightweight, small, -and fast, when compared to other virtualization technologies. - -#### Containers - -A container is a runnable instance of an image. You can create, start, stop, -move, or delete a container using the Docker API or CLI. You can connect a -container to one or more networks, attach storage to it, or even create a new -image based on its current state. - -By default, a container is relatively well isolated from other containers and -its host machine. You can control how isolated a container's network, storage, -or other underlying subsystems are from other containers or from the host -machine. - -A container is defined by its image as well as any configuration options you -provide to it when you create or start it. When a container is removed, any changes to -its state that aren't stored in persistent storage disappear. - -##### Example `docker run` command - -The following command runs an `ubuntu` container, attaches interactively to your -local command-line session, and runs `/bin/bash`. - -```console -$ docker run -i -t ubuntu /bin/bash -``` - -When you run this command, the following happens (assuming you are using -the default registry configuration): - -1. If you don't have the `ubuntu` image locally, Docker pulls it from your - configured registry, as though you had run `docker pull ubuntu` manually. - -2. Docker creates a new container, as though you had run a `docker container create` - command manually. - -3. Docker allocates a read-write filesystem to the container, as its final - layer. This allows a running container to create or modify files and - directories in its local filesystem. - -4. Docker creates a network interface to connect the container to the default - network, since you didn't specify any networking options. This includes - assigning an IP address to the container. By default, containers can - connect to external networks using the host machine's network connection. - -5. Docker starts the container and executes `/bin/bash`. Because the container - is running interactively and attached to your terminal (due to the `-i` and `-t` - flags), you can provide input using your keyboard while Docker logs the output to - your terminal. - -6. When you run `exit` to terminate the `/bin/bash` command, the container - stops but isn't removed. You can start it again or remove it. - -## The underlying technology -Docker is written in the [Go programming language](https://golang.org/) and takes -advantage of several features of the Linux kernel to deliver its functionality. -Docker uses a technology called `namespaces` to provide the isolated workspace -called the container. When you run a container, Docker creates a set of -namespaces for that container. - -These namespaces provide a layer of isolation. Each aspect of a container runs -in a separate namespace and its access is limited to that namespace. - - diff --git a/content/mainnets/_index.md b/content/mainnets/_index.md index 6064962..312f5e9 100644 --- a/content/mainnets/_index.md +++ b/content/mainnets/_index.md @@ -1,28 +1,48 @@ --- title: Mainnet Services -description: Pick a project from the list below to view guides and commands. -keywords: mainnet, services, +description: Mainnet Services +keywords: mainnet, services grid: -- title: Axelar - image: contact_page - link: /subscription/faq/ -- title: Billing - icon: credit_score - link: /billing/faqs/ -- title: Docker Hub - icon: lan - link: /docker-hub/general-faqs/ -- title: Enforcing Single Sign-On - icon: key - link: /single-sign-on/enforcement-faqs/ -- title: Single Sign-On and IdPs - icon: checklist - link: /single-sign-on/idp-faqs/ -- title: Docker Desktop - icon: explore - link: /desktop/faqs/general/ + - title: Band + image: + dark: /assets/images/networks/band.png + light: /assets/images/networks/band.png + link: /mainnets/ + description: Band Protocol is a cross-chain data oracle platform that aggregates and connects real-world data and APIs to smart contracts. + - title: Composable + image: + dark: /assets/images/networks/compossable2.jpeg + light: /assets/images/networks/compossable2.jpeg + link: /mainnets/ + description: Composable is the base layer connecting chains and applications across multiple ecosystems. + - title: Nym + image: + dark: /assets/images/networks/nym.png + light: /assets/images/networks/nym.png + link: /mainnets/ + description: Nym protects internet traffic by routing it through a decentralised mixnet that can be accessed anonymously using zk-nyms. + - title: Haqq + image: + dark: /assets/images/networks/haqq.png + light: /assets/images/networks/haqq.png + link: /mainnets/ + description: HAQQ is the blockchain network that issues Islamic Coin, its native cryptocurrency. + - title: Source + image: + dark: /assets/images/networks/source.png + light: /assets/images/networks/source.png + link: /mainnets/ + description: Enterprises, developers and individuals use Source's sustainable and value backed tech suite to easily access, build and integrate Web 3.0 services on the blockchain. + - title: Stader + image: + dark: /assets/images/networks/stader.png + light: /assets/images/networks/stader.png + link: /mainnets/ + description: Stader Labs is a liquid staking platform for earnings liquid staking rewards across crypto tokens such as Ethereum, polygon, BNB, & more. + - title: Umee + image: + dark: /assets/images/networks/umee.png + light: /assets/images/networks/umee.png + link: /mainnets/ + description: Umee is the most programmable, safety-first lending algorithm built as a blockchain. --- - -Explore popular FAQ topics. - -{{< grid >}} \ No newline at end of file diff --git a/content/testnets/_index.md b/content/testnets/_index.md index 9c8a52c..4b7e18d 100644 --- a/content/testnets/_index.md +++ b/content/testnets/_index.md @@ -1,6 +1,6 @@ --- -title: Frequently asked questions -description: Landing page to common FAQ topics +title: Testnet Services +description: Testnet Services keywords: faqs, desktop, Hub, Scout, Engine, Build, Extensions grid: - title: Subscription @@ -23,6 +23,3 @@ grid: link: /desktop/faqs/general/ --- -Explore popular FAQ topics. - -{{< grid >}} \ No newline at end of file diff --git a/content/testnets/cascadia_6201-1/Endpoints.md b/content/testnets/cascadia_6201-1/Endpoints.md new file mode 100644 index 0000000..ecda5de --- /dev/null +++ b/content/testnets/cascadia_6201-1/Endpoints.md @@ -0,0 +1,6 @@ +--- +title: Cascadia endpoints +description: How to install cascadia node +keywords: cascadia, node, install +--- + diff --git a/data/toc.yaml b/data/toc.yaml index 4eb5d22..f074c9b 100644 --- a/data/toc.yaml +++ b/data/toc.yaml @@ -4,9 +4,8 @@ Mainnets: - sectiontitle: Get started section: - title: "Part 1: Overview" - path: /get-started/ - - title: "Part 2: Containerize an application" - path: /get-started/02_our_app/ + path: /mainnets/ + Testnets: - title: Testnets @@ -16,5 +15,5 @@ Testnets: - title: "⚙️ Install cascadia node" path: /testnets/cascadia_6201-1/ - title: "🔗 Endpoints" - path: /testnets/cascadia_6201-1/ + path: /testnets/cascadia_6201-1/Endpoints/