diff --git a/tutorials/systemd-essentials/index.mdx b/tutorials/systemd-essentials/index.mdx index 4eeecace2e..6b92c5b693 100644 --- a/tutorials/systemd-essentials/index.mdx +++ b/tutorials/systemd-essentials/index.mdx @@ -1,10 +1,10 @@ --- meta: title: Learning systemd essentials - description: This page shows how to manage units on your server with systemd. + description: Learn the essentials of systemd, a core component of Linux systems, and master its usage with our in-depth tutorial, covering key concepts and practical examples. content: h1: Learning systemd essentials - paragraph: This page shows how to manage units on your server with systemd. + paragraph: Learn the essentials of systemd, a core component of Linux systems, and master its usage with our in-depth tutorial, covering key concepts and practical examples. tags: systemd instances categories: - instances @@ -87,7 +87,7 @@ systemctl list-unit-files ## Using units -The most common object that `systemd` manages and acts upon is a "`unit`". +The most common object that `systemd` manages and acts upon is a `unit`. Units can be, for example, services (.service), devices (.device), mount points (.mount), or sockets (.socket). You should always specify the complete name of the unit file, including its suffix (for example sshd.socket). A short form is available for .service files. For example `nginx` is equivalent to `nginx.service`. @@ -157,7 +157,11 @@ To **disable** a unit to not start during bootup: systemctl disable unit ``` -Every service unit that is known to systemd may be started manually – even if it is disabled. To explicitly keep a service from running, use the **mask** command _(Attention: This makes it impossible to start the concerned service. Neither manually nor as a dependency. Use it carefully.)_: +Every service unit that is known to systemd may be started manually – even if it is disabled. To explicitly keep a service from running, use the **mask** command + + +This makes it impossible to start the concerned service either manually or as a dependency. Use it carefully. + ```s systemctl mask unit @@ -185,7 +189,7 @@ To shut down and **reboot** the system, type: systemctl reboot ``` -To shut down and **power-off** the system, run the following command: +To shut down and **power off** the system, run the following command: ```s systemctl poweroff @@ -272,10 +276,10 @@ journalctl -u unit ## Exploring units and unit files -To explore the content of a Unit File, some options are available. -A Unit File contains the parameters that are used by systemd to manage and run a unit. +To explore the content of a unit file, some options are available. +A unit file contains the parameters that are used by systemd to manage and run a unit. -To see the full content of a Unit file, type: +To see the full content of a unit file, type: ```s systemctl cat unit @@ -299,13 +303,13 @@ This command will give you a list in return, showing each parameter being manage Systemctl allows you to edit unit files directly from the application, without needing to know the exact location of the file on the disk. -To add a snippet to an existing unit file, which can be used to append or overwrite configurations in the default Unit File, type: +To add a snippet to an existing unit file, which can be used to append or overwrite configurations in the default unit file, type: ```s systemctl edit unit ``` -It is also possible to modify the entire content of the Unit File instead of creating a snippet by using the `--full` flag: +It is also possible to modify the entire content of the unit file instead of creating a snippet by using the `--full` flag: ```s systemctl edit --full unit diff --git a/tutorials/trigger-ifttt-actions/assets/scaleway-iothub_ifttt_howto_applet_continue.webp b/tutorials/trigger-ifttt-actions/assets/scaleway-iothub_ifttt_howto_applet_continue.webp deleted file mode 100644 index 175098b9b2..0000000000 Binary files a/tutorials/trigger-ifttt-actions/assets/scaleway-iothub_ifttt_howto_applet_continue.webp and /dev/null differ diff --git a/tutorials/trigger-ifttt-actions/assets/scaleway-iothub_ifttt_howto_applet_done.webp b/tutorials/trigger-ifttt-actions/assets/scaleway-iothub_ifttt_howto_applet_done.webp deleted file mode 100644 index 5c20323f1e..0000000000 Binary files a/tutorials/trigger-ifttt-actions/assets/scaleway-iothub_ifttt_howto_applet_done.webp and /dev/null differ diff --git a/tutorials/trigger-ifttt-actions/assets/scaleway-iothub_ifttt_howto_googlesheet.webp b/tutorials/trigger-ifttt-actions/assets/scaleway-iothub_ifttt_howto_googlesheet.webp deleted file mode 100644 index 4efba4f3c3..0000000000 Binary files a/tutorials/trigger-ifttt-actions/assets/scaleway-iothub_ifttt_howto_googlesheet.webp and /dev/null differ diff --git a/tutorials/trigger-ifttt-actions/assets/scaleway-iothub_ifttt_howto_route.webp b/tutorials/trigger-ifttt-actions/assets/scaleway-iothub_ifttt_howto_route.webp deleted file mode 100644 index c5911f1577..0000000000 Binary files a/tutorials/trigger-ifttt-actions/assets/scaleway-iothub_ifttt_howto_route.webp and /dev/null differ diff --git a/tutorials/trigger-ifttt-actions/assets/scaleway-iothub_ifttt_howto_webclient.webp b/tutorials/trigger-ifttt-actions/assets/scaleway-iothub_ifttt_howto_webclient.webp deleted file mode 100644 index 6fdebb7a00..0000000000 Binary files a/tutorials/trigger-ifttt-actions/assets/scaleway-iothub_ifttt_howto_webclient.webp and /dev/null differ diff --git a/tutorials/trigger-ifttt-actions/assets/scaleway_ifttt.webp b/tutorials/trigger-ifttt-actions/assets/scaleway_ifttt.webp deleted file mode 100644 index 35d65bf4b3..0000000000 Binary files a/tutorials/trigger-ifttt-actions/assets/scaleway_ifttt.webp and /dev/null differ diff --git a/tutorials/trigger-ifttt-actions/index.mdx b/tutorials/trigger-ifttt-actions/index.mdx deleted file mode 100644 index 3f5295d092..0000000000 --- a/tutorials/trigger-ifttt-actions/index.mdx +++ /dev/null @@ -1,79 +0,0 @@ ---- -meta: - title: Triggering IFTTT actions from IoT Hub messages - description: This page explains how to combine IoT Hub and IFTTT to easily make powerful applications. -content: - h1: Triggering IFTTT actions from IoT Hub messages - paragraph: This page explains how to combine IoT Hub and IFTTT to easily make powerful applications. -tags: IoT IFTTT -hero: assets/scaleway_ifttt.webp -categories: - - iot-hub -dates: - validation: 2024-10-29 - posted: 2021-01-04 ---- - -IFTTT, an acronym for "If This, Then That," offers a user-friendly yet robust automation service, enabling users to trigger actions based on specific events. - -With an extensive array of customizable events and actions at your fingertips, the possibilities are virtually endless — an incredibly empowering feature. - -In this tutorial, we will show you how to quickly build a simple reporting application that stores your devices' data in a Google sheet. - - - -- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - -## Create an IFTTT account and set up an applet - -1. [Sign up](https://ifttt.com/) to IFTTT. When done, click the **create** button to start building your applet. -2. Choose `Webhooks: Receive a web request` as the "If This" trigger. Type in `iot_event` as the event name and create the trigger. -3. Choose `Google Sheets: Add row to spreadsheet` as the "Then That" action. We will use default settings and just create the action without changing them. -4. Click the **continue** button - -5. Choose a title, such as `Scaleway IoT Hub to Google Sheet` as your applet name and click Finish. You're done with the applet. - - -Now the applet is set up, we need to find our webhook key. Head to your [webhook settings](https://ifttt.com/maker_webhooks/settings) and you will find a URL like `https://maker.ifttt.com/use/`. Write down the key part - we will use it later. - -## Creating an IoT Hub and setting up the IoT Route - -Now that we have our IFTTT applet ready, we need to create an IoT Hub. This will be where our simulated IoT Device will publish messages to trigger our IFTTT applet. - -1. Follow [this procedure](/iot-hub/how-to/create-hub/) to create an IoT Hub. Select your name and plan of choice, and click the `Create Hub` button. -2. Head to the Routes tab of your IoT Hub. -3. Create a new route with the following settings: - - Name: anything you'd like (ex: `IFTTT Route`) - - Topic: This will be the topic to publish to from your Device, let's use `my/data` - - Route type: `REST Query` - - Verb: `POST` - - Endpoint: `https://maker.ifttt.com/trigger/iot_event/with/key/` where `` is the key you got from IFTTT earlier. - - HTTP Headers: `Content-Type: application/json` - - - -Now that we have everything set up, let's add a Device and send a message from there. - -## Adding a Device a triggering the IFTTT applet - -In your [Scaleway console](https://console.scaleway.com), head to the `Devices` tab of your IoT Hub. From there, to add a new Device, give it any name and pick the `Allow insecure connection` option (you do not want to do that in production, but this is fine for this tutorial's purpose). Click the `Add` button, and, finally, the `Close` button. - -Now your Device appears in the Device list, click it and then on the `MQTT Webclient` button to simulate a real device. - -In the `Topic` field write `my/data` (which is the topic we chose for the IoT Route). In the `Message` field write `{ "value1" : "Hi", "value2" : "from", "value3" : "Scaleway!" }`. Then click the `Publish` button (no confirmation will be issued). - - - -The message published on `my/data` topic will be received by the IoT Route and forwarded to the IFTTT Webhook trigger, which will save the values in the Google sheet. - -Now head to your [Google sheet home page](https://docs.google.com/spreadsheets/), open the `IFTTT_Maker_Webhooks_Events` spreadsheet, and voila. You can even see data flowing in live when publishing more messages. - - - -### All done - -We hope you had fun collecting data from your IoT Hub to a Google sheet. This is one of the many possibilities the IoT Hub REST Route provides. Stay tuned for more REST Route usage examples. - ---- - -Learn more about [Scaleway IoT Hub](/iot-hub/concepts/), discover how to add [Devices to the hub](/iot-hub/how-to/add-device/) or check out the [IoT Hub metrics](/iot-hub/how-to/view-metrics/). \ No newline at end of file diff --git a/tutorials/vpc-public-gateway-autoconfiguration/index.mdx b/tutorials/vpc-public-gateway-autoconfiguration/index.mdx index 90441d7dd5..1a1a476285 100644 --- a/tutorials/vpc-public-gateway-autoconfiguration/index.mdx +++ b/tutorials/vpc-public-gateway-autoconfiguration/index.mdx @@ -10,7 +10,7 @@ categories: - instances tags: Private-Network instances Public-Gateway dates: - validation: 2024-11-05 + validation: 2025-05-14 --- ## Private Networks and Public Gateways - Overview @@ -47,7 +47,7 @@ dates: valid_lft forever preferred_lft forever ``` 3. Go to the [VPC page](https://console.scaleway.com/vpc/vpc) of the Scaleway console. -4. Click the default VPC of the region that covers your Instance's Availability Zone. +4. Click a VPC of the region that covers your Instance's Availability Zone. 5. Click **Create Private Network**. The Private Network creation wizard displays: 6. Leave the default settings in place, or enter a customized **name**, **tags** and, in **Advanced Settings**, **CIDR block**. @@ -113,4 +113,6 @@ Congratulations, you have completed your first configuration of Instances in a P * [VPC Quickstart](/public-gateways/quickstart/) * [How to use Private Networks](/instances/how-to/use-private-networks/) -* [How to configure a Public Gateway](/public-gateways/how-to/configure-a-public-gateway/) \ No newline at end of file +* [How to configure a Public Gateway](/public-gateways/how-to/configure-a-public-gateway/) +* [Getting the most from your Private Networks](/vpc/reference-content/getting-most-private-networks/) +* [Creating a basic infrastructure to leverage VPC isolation](/vpc/reference-content/use-case-basic/) \ No newline at end of file diff --git a/tutorials/zabbix-monitoring/index.mdx b/tutorials/zabbix-monitoring/index.mdx index 67e270a8ee..771317a8e7 100644 --- a/tutorials/zabbix-monitoring/index.mdx +++ b/tutorials/zabbix-monitoring/index.mdx @@ -1,10 +1,10 @@ --- meta: title: Monitoring Instances with Zabbix on Ubuntu Jammy Jellyfish (22.04 LTS) - description: Zabbix is an open-source monitoring solution for devices and services + description: Learn how to set up Zabbix monitoring on Scaleway with our step-by-step tutorial. Discover how to efficiently monitor your infrastructure and applications with this comprehensive guide. content: h1: Monitoring Instances with Zabbix on Ubuntu Jammy Jellyfish (22.04 LTS) - paragraph: Zabbix is an open-source monitoring solution for devices and services + paragraph: Learn how to set up Zabbix monitoring on Scaleway with our step-by-step tutorial. Discover how to efficiently monitor your infrastructure and applications with this comprehensive guide. tags: instances Zabbix monitoring MariaDB categories: - instances