Skip to content

Commit b17d58d

Browse files
authored
Merge pull request #354 from ByteInternet/fix-whole-bunch-of-deadlinks
Fix a lot of deadlinks and references to byte control panel
2 parents 2be684e + 44a2f0d commit b17d58d

24 files changed

+35
-48
lines changed

README.md

Lines changed: 16 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -2,14 +2,14 @@
22

33
## Generating new docs
44

5-
``` bash
5+
```bash
66
DOC_URL=https://support.hypernode.com/en/ecommerce/magento-1/how-to-enable-mysql-query-logging-for-magento-1-x
77
bin/download_doc --output-dir=docs/ecommerce-applications $DOC_URL
88
```
99

1010
## Setting up the project
1111

12-
``` bash
12+
```bash
1313
mkvirtualenv hypernode-docs-next
1414
echo "export PYTHONPATH=$(pwd)" >> $VIRTUAL_ENV/bin/postactivate
1515
workon hypernode-docs-next
@@ -19,33 +19,38 @@ pre-commit install
1919

2020
## Building the docs
2121

22-
``` bash
22+
```bash
2323
bin/build_docs
2424
```
2525

2626
## Serving the docs
2727

28-
``` bash
28+
```bash
2929
bin/serve_docs
3030
```
31+
3132
## Setup Frontend step by step
33+
3234
```
3335
clone the repository
3436
pip install -r requirements/development.txt
3537
bin/build_docs
3638
bin/serve_docs
3739
```
40+
3841
in another terminal run
39-
``` bin/watch ```
42+
`bin/watch`
4043

4144
open localhost and now you can make changes in style and refresh the page without rebuilding
4245

4346
when you're working on scss to compile it automatically run
47+
4448
```
4549
npx sass --watch docs/_static/scss:docs/_static/css
4650
```
4751

4852
or as a production build:
53+
4954
```
5055
npx sass --style compressed --no-source-map docs/_static/scss:docs/_static/css
5156
```
@@ -57,6 +62,7 @@ Deploys automatically after merging branchers to master.
5762
### Deploy with Hypernode Deploy
5863

5964
To deploy to a local Hypernode Docker environment:
65+
6066
```
6167
$ docker pull docker.hypernode.com/byteinternet/hypernode-buster-docker:latest
6268
$ 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)
6672
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.
6773

6874
Then deploy to your local Hypernode Docker:
75+
6976
```
7077
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
7178
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)"
7481
## Building the manpage deb
7582

7683
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:
84+
7785
```
7886
# First create the cow environment
7987
export ARCH=amd64
@@ -91,16 +99,19 @@ gbp buildpackage --git-pbuilder --git-dist=$DIST --git-arch=$ARCH --git-ignore-b
9199
```
92100

93101
Then after building the Deb you could install it with dpkg. For example:
102+
94103
```
95104
dpkg -i ../hndocsnext_20230121.173551_all.deb
96105
```
97106

98107
And test it out with:
108+
99109
```
100110
man hypernode
101111
```
102112

103113
To inspect the contents of the deb archive you can run:
114+
104115
```
105116
# dpkg -L hndocsnext
106117
/.

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

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -68,8 +68,6 @@ DigitalOcean and Amazon both have data centers all over the world.
6868

6969
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.
7070

71-
**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.
72-
7371
## Tips For Ordering a Hypernode
7472

7573
- Choose a logical name. IE: If your site is example.com, order example.hypernode.com

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ We would like to thank the following individuals and/or organizations, who have
2929
| [Pethuraj M](https://www.pethuraj.com/) | 1 July 2020 | Reported a flaw in our password reset flow |
3030
| [Miguel Santareno](https://www.linkedin.com/in/miguelsantareno/) | 14 May 2020 | Reported information leakage from marketing sites. |
3131
| [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. |
32-
| [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. |
32+
| [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. |
3333
| [Maksym Bendeberia](https://www.linkedin.com/in/jogspokoen/) / [WebSafety Ninja](https://websafety.ninja/) | 12 March 2019 | Reported information leakage from an internal deployment server. |
3434
| [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. |
3535
| [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. |

docs/about-hypernode/support/how-to-handle-os-and-room-change-upgrade.md

100755100644
File mode changed.

docs/best-practices/performance/how-to-improve-your-magento-search.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,6 @@ Please note that due to the relatively heavy resource requirements for ElasticSe
3434
If you are on a lower plan, you’ll need to either upgrade, or make use of an external search provider. There a several companies you can choose for a monthly subscription:
3535

3636
- [Bonsai.io](https://bonsai.io/)
37-
- [Qbox.io](https://qbox.io/)
3837
- [Elastic.co](https://www.elastic.co/cloud/as-a-service)
3938

4039
**If you choose Bonsai, we have made a special deal with Bonsai. Please send a mail to support@hypernode.com for a discount code.**

docs/best-practices/performance/how-to-optimize-your-images.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ redirect_from:
1515

1616
If you want a faster shop, you have probably looked at [Google Pagespeed Insights](https://developers.google.com/speed/pagespeed/insights/) for useful suggestions. It probably told you to optimize your images. Which means, reducing the size-on-disk without losing quality. This is a very cumbersome process if you do this by hand (opening in Photoshop, saving-as, etcetera). But it is very easy if you use Hypernode. If you follow this article, **it will take you only a couple of minutes to set up automatic image optimization**.
1717

18-
Thanks to Peter Jaap for doing the [initial research](https://www.byte.nl/blog/afbeeldingen-optimaliseren-magento-bespaart-veel-webruimte/) (in Dutch).
18+
Thanks to Peter Jaap for doing the initial research.
1919

2020
> [@Hypernode_com](https://twitter.com/Hypernode_com) hypernode-image-optimizer is pretty effective "Optimization profit over all files: 502812 KB (82%)". Thanks for that!
2121
>

docs/best-practices/security/how-to-fix-malicious-javascript-credit-card-hijack.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ With this relatively new way of hacking, malware is added in the browser of your
2626

2727
In 2015 we analyzed the malware and found out that a staggering amount of 3500 Magento shops are part of a zombie network that interfere credit card credentials, and send this data to so called command&control servers. (Command&control servers are a network of servers where hackers collect this sort of data). This was the first time we encountered an automated credit card fraud on this scale. It’s obvious hackers have massively improved in becoming more professional in automating large-scale credit card fraud.
2828

29-
[Read more about Credit card Hijack](https://www.byte.nl/blog/widespread-credit-card-hijacking-discovered)
29+
[Read more about Credit card Hijack](../../best-practices/security/how-to-fix-malicious-javascript-credit-card-hijack.md#what-is-credit-card-hijack)
3030

3131
We suspect this leak has been made possible due to unpatched Magento shops. So if you haven’t completely patched your Magento shop yet, make sure you do. Use Magereport.com to check if there are any patches not yet installed.
3232

docs/best-practices/testing/hypernode-docker.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,8 +13,6 @@ redirect_from:
1313

1414
The official Hypernode Docker image for Magento development is now available. This image can be used to set up a fast and easy local development environment for Hypernode, or as a build machine in a CI environment representative of the production environment. The image contains the exact same packages and configuration as a real Hypernode except for some Docker specific tweaks. By testing and developing against this image you can be sure that when you deploy to a Hypernode in production there will be no surprises because of different software versions or configurations.
1515

16-
Interested in a case study? Read [this article](https://blog.guapa.nl/local-development-with-the-hypernode-docker-container-linux/) about the Hypernode docker of one of our partners!
17-
1816
## About the Hypernode Docker Image
1917

2018
We build this image multiple times a day (every time we do a [release](https://changelog.hypernode.com/)) by applying our configuration management on the [phusion/baseimage-docker](https://github.com/phusion/baseimage-docker) ["fat" container](https://blog.phusion.nl/2015/01/20/baseimage-docker-fat-containers-treating-containers-vms/). By treating the Docker as a lightweight VM instead of as a vehicle for a single process we stay close to what an actual Hypernode actually looks like. No micro-services or a multi-container application, but a single instance with minimal network overhead and all batteries included.

docs/best-practices/usage/hypernode-magerun.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -72,7 +72,7 @@ Outputs or saves a http.magerunmaps boilerplate containing your store setup for
7272
n98-magerun hypernode:varnish:config-save
7373
```
7474

75-
Fetches the VCL configuration from turpentine and applies it. Make sure [turpentine is installed and configured](https://support.hypernode.com/knowledgebase/varnish-on-hypernode/) correctly.
75+
Fetches the VCL configuration from turpentine and applies it. Make sure [turpentine is installed and configured](../../ecommerce-applications/magento-1/how-to-configure-varnish-for-magento-1-x.md#configure-turpentine) correctly.
7676

7777
### Flush all URL's in Varnish cache
7878

@@ -120,7 +120,7 @@ Building a .deb for release:
120120
./build.sh
121121
```
122122

123-
Then if everything is alright, upload the new version to your repository with something like [dput](http://manpages.ubuntu.com/manpages/precise/man1/dput.1.html)
123+
Then if everything is alright, upload the new version to your repository with something like [dput](https://manpages.ubuntu.com/manpages/plucky/en/man1/dput.1.html)
124124

125125
## n98-magerun2 compatibility
126126

docs/ecommerce-applications/magento-1/how-to-clean-the-magento-1-x-logs.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -65,4 +65,4 @@ Scroll down to select ‘Empty’ from the dropdown ‘With selected’ and clic
6565

6666
## Turn Off Database Logging
6767

68-
If you don’t need any database logging it can be worthwhile to disable all logging. To do so, install the [`disablelog extension by Yireo`](https://www.yireo.com/software/magento-extensions). For shops that are heavy on the database, this can help reduce the amount of update/insert queries and therefore reducing load times.
68+
If you don’t need any database logging it can be worthwhile to disable all logging. To do so, install the [`disablelog extension by Yireo`](https://github.com/yireo-magento1/Yireo_DisableLog). For shops that are heavy on the database, this can help reduce the amount of update/insert queries and therefore reducing load times.

0 commit comments

Comments
 (0)