diff --git a/tutorials/deploy-mdbooks-serverless-containers/index.mdx b/tutorials/deploy-mdbooks-serverless-containers/index.mdx index 9115341b7a..4dead25db4 100644 --- a/tutorials/deploy-mdbooks-serverless-containers/index.mdx +++ b/tutorials/deploy-mdbooks-serverless-containers/index.mdx @@ -11,11 +11,11 @@ categories: - containers - container-registry dates: - validation: - posted: + validation: 2024-10-30 + posted: 2024-10-30 --- -Publish modern online books, for product, API documentation, tutorials, course material or anything that requires a clean, easily navigable and customizable presentation. +`mdBooks` lets you publish modern online books, for product, API documentation, tutorials, course material or anything that requires a clean, easily navigable and customizable presentation. This tutorial uses `mdbooks` to publish simple documentation but the main goal of this tutorial is to show how simple it is to pick a project, package it inside an image and deploy it on Serverless Containers. @@ -26,11 +26,11 @@ pick a project, package it inside an image and deploy it on Serverless Container - [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization - Docker installed on your local machine -## Why deploying on Serverless +## Why deploy on Serverless? -Serverless products are perfect for cost efficiency with a pay-as-you-go model and scale very well. +Serverless products are perfect for cost efficiency with a pay-as-you-go model, and scale very well. -With zero infrastructure management and many tools to integrate in CI/CD environments, `mdbooks` can benefit a lot of Serverless Containers. +With zero infrastructure management and many tools to integrate in CI/CD environments, an `mdbooks` deployment is well suited to Serverless Containers. ## Local setup @@ -40,9 +40,9 @@ With zero infrastructure management and many tools to integrate in CI/CD environ - `mdbook init my-first-book` in order to create a sample book. - `cd my-first-book` to open the directory created by init command. -3. *(optional)* Now you can edit the content of the book to publish. +3. *(Optional)* Edit the content of the book to publish. -4. It is recommended to test the book using the command: `mdbook test`. +4. Test the book using the command: `mdbook test`. ## Prepare Container Registry @@ -73,11 +73,11 @@ ENV PATH="$PATH:/home/mdbooks" ENTRYPOINT ["mdbook", "serve", "-n", "0.0.0.0", "-p", "8080" ] ``` -2. Open a web browser on your computer and navigate to the [Container Registry](https://console.scaleway.com/containers/) product in the Scaleway Console. +2. Open a web browser on your computer and navigate to the [Container Registry](https://console.scaleway.com/containers/) product in the Scaleway console. 3. Click **Create namespace**. A namespace is used to hold the image. - A pop-up will appear with informations to log into your Container Registry Namespace with `docker login`. This will allow to push the image later. + A pop-up will appear with information to log into your Container Registry Namespace with `docker login`. This will allow us to push the image later. 4. Create the namespace and save the registry endpoint. The registry endpoint looks like `rg..scw.cloud/` @@ -105,7 +105,7 @@ ENTRYPOINT ["mdbook", "serve", "-n", "0.0.0.0", "-p", "8080" ] You can keep default values of other parameters and fine-tune them later at anytime without downtime. 3. Click **Deploy container** button and wait few seconds for the deployment. -4. Congratulation you Serverless Container is deployed an ready. You can access it via it's **endpoint**. +Your Serverless Container is deployed and ready. You can access it via its **endpoint**. ## Going further