Add cancel cmd to obj storage docs

.devcontainer/devcontainer.json

@@ -12,7 +12,6 @@
     },
     "vscode": {
       "extensions": [
-        "bierner.markdown-mermaid",
         "davidanson.vscode-markdownlint",
         "ms-python.python"
       ]

.github/workflows/cleanup_acceptance.yaml

@@ -7,7 +7,7 @@ on:
 jobs:
   cleanup:
     runs-on: ubuntu-latest
-    container: quay.io/hypernode/deploy:4-php8.3-node20
+    container: quay.io/hypernode/deploy:latest-php8.3-node20
     environment: acceptance
     steps:
       - uses: actions/checkout@v2

.github/workflows/deploy.yaml

@@ -12,7 +12,7 @@ env:
 jobs:
   build:
     runs-on: ubuntu-latest
-    container: quay.io/hypernode/deploy:4-php8.3-node20
+    container: quay.io/hypernode/deploy:latest-php8.3-node20
     steps:
       - uses: actions/checkout@v3
         with:
@@ -47,7 +47,7 @@ jobs:
       name: acceptance
       url: ${{ steps.get_brancher_hostname.outputs.BRANCHER_URL }}
     if: github.ref != 'refs/heads/master'
-    container: quay.io/hypernode/deploy:4-php8.3-node20
+    container: quay.io/hypernode/deploy:latest-php8.3-node20
     steps:
       - uses: actions/checkout@v3
         with:
@@ -102,7 +102,7 @@ jobs:
       name: production
       url: https://docs.hypernode.io
     if: github.ref == 'refs/heads/master'
-    container: quay.io/hypernode/deploy:4-php8.3-node20
+    container: quay.io/hypernode/deploy:latest-php8.3-node20
     steps:
       - uses: actions/checkout@v3
       - name: download build artifact

.github/workflows/lint.yaml

@@ -0,0 +1,29 @@
+name: Run linting and suggest changes
+
+on:
+  pull_request:
+
+permissions:
+  contents: read
+  pull-requests: write
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ['3.10']
+
+    steps:
+      - uses: actions/checkout@v3
+      - uses: actions/setup-python@v4
+        with:
+          python-version: ${{ matrix.python-version }}
+      - name: Install dependencies
+        run: |
+          pip install -r requirements/base.txt
+      - name: Check markdown format
+        run: mdformat docs/
+      - uses: parkerbxyz/suggest-changes@v1
+        with:
+          event: 'REQUEST_CHANGES'

README.md

@@ -2,14 +2,14 @@
 
 ## Generating new docs
 
-``` bash
+```bash
 DOC_URL=https://support.hypernode.com/en/ecommerce/magento-1/how-to-enable-mysql-query-logging-for-magento-1-x
 bin/download_doc --output-dir=docs/ecommerce-applications $DOC_URL
 ```
 
 ## Setting up the project
 
-``` bash
+```bash
 mkvirtualenv hypernode-docs-next
 echo "export PYTHONPATH=$(pwd)" >> $VIRTUAL_ENV/bin/postactivate
 workon hypernode-docs-next
@@ -19,33 +19,38 @@ pre-commit install
 
 ## Building the docs
 
-``` bash
+```bash
 bin/build_docs
 ```
 
 ## Serving the docs
 
-``` bash
+```bash
 bin/serve_docs
 ```
+
 ## Setup Frontend step by step
+
 ```
 clone the repository
 pip install -r requirements/development.txt
 bin/build_docs
 bin/serve_docs
 ```
+
 in another terminal run
-``` bin/watch ```
+`bin/watch`
 
 open localhost and now you can make changes in style and refresh the page without rebuilding
 
 when you're working on scss to compile it automatically run
+
 ```
 npx sass --watch docs/_static/scss:docs/_static/css
 ```
 
 or as a production build:
+
 ```
 npx sass --style compressed --no-source-map docs/_static/scss:docs/_static/css
 ```
@@ -57,6 +62,7 @@ Deploys automatically after merging branchers to master.
 ### Deploy with Hypernode Deploy
 
 To deploy to a local Hypernode Docker environment:
+
 ```
 $ docker pull docker.hypernode.com/byteinternet/hypernode-buster-docker:latest
 $ docker run docker.hypernode.com/byteinternet/hypernode-buster-docker:latest
@@ -66,6 +72,7 @@ $ # Note the IP address, it should be 172.17.0.2 (otherwise refer to deploy.php)
 Next make sure your `~/.ssh/yourdeploykey` equivalent can log in to the Docker host (172.17.0.2) as the app user. You can add it to the `/data/web/.ssh/authorized_keys` file on in the instance manually.
 
 Then deploy to your local Hypernode Docker:
+
 ```
 docker run --rm -it --env SSH_PRIVATE_KEY="$(cat ~/.ssh/yourdeploykey | base64)" -v ${PWD}:/build quay.io/hypernode/deploy:latest hypernode-deploy build -vvv  # First build the artifact
 docker run --rm -it --env SSH_PRIVATE_KEY="$(cat ~/.ssh/yourdeploykey | base64)" -v ${PWD}:/build quay.io/hypernode/deploy:latest hypernode-deploy deploy docker -vvv  # Then perform the deploy
@@ -74,6 +81,7 @@ docker run --rm -it --env SSH_PRIVATE_KEY="$(cat ~/.ssh/yourdeploykey | base64)"
 ## Building the manpage deb
 
 The docs are also packaged as a debian package named `hndocsnext` so that on a Hypernode you can run `man hypernode` (or `hypernode-manual`) and page through a `manpage` version of the Hypernode docs. To build that debian package on a Debian machine you can run these commands:
+
 ```
 # First create the cow environment
 export ARCH=amd64
@@ -91,16 +99,19 @@ gbp buildpackage --git-pbuilder --git-dist=$DIST --git-arch=$ARCH --git-ignore-b
 ```
 
 Then after building the Deb you could install it with dpkg. For example:
+
 ```
 dpkg -i ../hndocsnext_20230121.173551_all.deb
 ```
 
 And test it out with:
+
 ```
 man hypernode
 ```
 
 To inspect the contents of the deb archive you can run:
+
 ```
 # dpkg -L hndocsnext
 /.

docs/_templates/layout.html

@@ -279,13 +279,13 @@ <h4>Need support?</h4>
       <div class="aside-tile__container aside-tile__feedback">
         <div class="aside-tile__content">
           <img src="https://static.hypernode.com/img/icons-multi-color/chat-bot.svg">
-          <h4>Join our<br>Feedback Group</h4>
+          <h4>Join our<br>Beta Test Group</h4>
           <ul class="aside-tile__feedback-list">
             <li><i class="fa fa-check-circle"></i>Experience new features first</li>
-            <li><i class="fa fa-check-circle"></i>Get a gift after each session</li>
+            <li><i class="fa fa-check-circle"></i>Get swag & giveaways</li>
             <li><i class="fa fa-check-circle"></i>Join product decision making</li>
           </ul>
-          <p><a class="ahref-orange" href="https://forms.gle/ocQjMzhghMkUzkB19" target="_blank">read more</a></p>
+          <p><a class="ahref-orange" href="https://www.hypernode.com/en/join-feedback-group/" target="_blank">Read more</a></p>
         </div>
       </div>
     </aside>

docs/about-hypernode/billing/how-to-choose-and-order-a-hypernode-plan.md

@@ -68,8 +68,6 @@ DigitalOcean and Amazon both have data centers all over the world.
 
 You can order a Hypernode plan via our [order page](https://www.hypernode.com/magento-cloud-hosting/#plans). The Control Panel is our default panel, which means all new Hypernode plans and trials will be booted in the Control Panel.
 
-**Please note:** if you are a Service Panel user (i.e. you use the Dutch panel), please order your new plans directly via [this page in the Service Panel](https://service.byte.nl/planinfo/order-selection/). This is to prevent plans from being booted in the wrong system.
-
 ## Tips For Ordering a Hypernode
 
 - Choose a logical name. IE: If your site is example.com, order example.hypernode.com

docs/about-hypernode/security-policies/one-of-your-magento-extensions-is-vulnerable.md

@@ -22,7 +22,7 @@ This can include creditcard theft, sending email spam in your name, stealing cus
 
 ## Special attention to online credit card theft
 
-A hot topic over the past few years are digital skimmers. A hacker group (also know as Magecart) use code inserted into websites to steal credit card details. As of October 2018 more than 20 extensions have been abused by hackers. Details can be found[in this blog explaining the attack method PHP Object Injection (POI)](https://sansec.io/labs/2018/10/23/magecart-extension-0days/). Former Hypernode owner Willem will update the list of vulnerable extensions regularly.
+A hot topic over the past few years are digital skimmers. A hacker group (also know as Magecart) use code inserted into websites to steal credit card details. As of October 2018 more than 20 extensions have been abused by hackers. Details can be found [in this blog explaining the attack method PHP Object Injection (POI)](https://sansec.io/labs/2018/10/23/magecart-extension-0days/). Former Hypernode owner Willem will update the list of vulnerable extensions regularly.
 
 ## How do I fix it?
 

docs/about-hypernode/security-policies/security-hall-of-fame.md

@@ -29,7 +29,7 @@ We would like to thank the following individuals and/or organizations, who have
 | [Pethuraj M](https://www.pethuraj.com/)                                                                                                                                                                 | 1 July 2020       | Reported a flaw in our password reset flow                                                             |
 | [Miguel Santareno](https://www.linkedin.com/in/miguelsantareno/)                                                                                                                                        | 14 May 2020       | Reported information leakage from marketing sites.                                                     |
 | [Gaurav Kumar](https://www.facebook.com/drago4344) and [Shivam Dattana](https://www.facebook.com/profile.php?id=100010397858328) / [Team Bugmania](https://www.openbugbounty.org/researchers/bugmania/) | 28 September 2019 | Reported a Cross site scripting (XSS) on magereport.com.                                               |
-| [Mike de Landgraaf](https://www.linkedin.com/in/mdelandgraaf/) / [MDL Online](https://mdlonline.com/)                                                                                                   | 21 March 2019     | Reported a misconfiguration that allowed user impersonation on Hypernode hosted webshops.              |
+| [Mike de Landgraaf](https://www.linkedin.com/in/mdelandgraaf/) / MDL Online                                                                                                                             | 21 March 2019     | Reported a misconfiguration that allowed user impersonation on Hypernode hosted webshops.              |
 | [Maksym Bendeberia](https://www.linkedin.com/in/jogspokoen/) / [WebSafety Ninja](https://websafety.ninja/)                                                                                              | 12 March 2019     | Reported information leakage from an internal deployment server.                                       |
 | [Jan Piet van Dijk](https://www.linkedin.com/in/janpietvandijk/) / [Interwijs B.V.](https://www.interwijs.nl/)                                                                                          | 28 August 2018    | Reported a privilege escalation on Hypernode, leading to a local root exploit.                         |
 | [Wijnand Wieskamp](https://www.linkedin.com/in/wijnand-wieskamp-8a784313/) / [Crystalsoft B.V.](https://www.crystalsoft.nl/)                                                                            | 1 June 2018       | Reported a misconfiguration that allowed a Hypernode’s preconfigured security settings to be bypassed. |