initial draft

Author: dominik-matic

docs/ecommerce-applications/magento-2/how-to-configure-remote-storage-for-magento-2-x.md

@@ -22,6 +22,11 @@ This can be useful for many reasons, such as:
 
 Configuring Magento 2 to start storing files in your bucket is done using a single command.
 
+**Hypernode Object Storage**
+```bash
+something something?
+```
+
 **AWS S3**
 
 ```bash
@@ -55,124 +60,54 @@ Instead of running (which is Magento's official way to do this):
 bin/magento remote-storage:sync
 ```
 
-One can run the following instead to really speed up the process:
+you can run the following to really speed up the process:
+
+```bash
+hypernode-object-storage objects sync pub/media/ s3://my_bucket_name/media/
+hypernode-object-storage objects sync var/import_export s3://my_bucket_name/import_export
+```
+
+`hypernode-object-storage objects sync` will run a sync process in the background for you,
+and will tell you what the PID of that process is. With the PID you can run the following
+command to check up on the progress of the sync: 
+
+```bash
+hypernode-object-storage objects show PID
+```
+
+Alternatively, you can run the `aws s3 sync` command directly:
 
 ```bash
 aws s3 sync pub/media/ s3://my_bucket_name/media/
 aws s3 sync var/import_export s3://my_bucket_name/import_export
 ```
 
-This is much faster than Magento's built-in sync, because `aws s3 sync` uploads files concurrently.
+In any case, that is much faster than Magento's built-in sync, because `aws s3 sync` uploads files concurrently.
 
 ## The storage flag file in the bucket
 
 Magento's S3 implementation creates a test file called `storage.flag`, which is basically created to test if the connection works. So this is not a magic file to mark anything ([source](https://github.com/magento/magento2/blob/6f4805f82bb7511f72935daa493d48ebda3d9039/app/code/Magento/AwsS3/Driver/AwsS3.php#L104)).
 
 ## Serving assets from your S3 bucket
 
-To start serving media assets from your S3 bucket, you need to make some adjustments to your nginx configuration. Create the following file at `/data/web/nginx/example.com/server.assets.conf` for each relevant vhost:
-
-```nginx
-set $backend "haproxy";
-
-location @object_storage_fallback {
-    # Proxy to object storage
-    set $bucket "my_bucket_name";
-    proxy_cache_key "$bucket$uri";
-    proxy_cache_valid 200 302 7d;
-    proxy_cache_methods GET HEAD;
-    proxy_cache_background_update on;
-    proxy_cache_use_stale updating;
-    proxy_cache asset_cache;
-    resolver 8.8.8.8;
-    proxy_pass https://$bucket.s3.amazonaws.com$uri;
-    proxy_pass_request_body off;
-    proxy_pass_request_headers off;
-    proxy_intercept_errors on;
-    proxy_hide_header "x-amz-id-2";
-    proxy_hide_header "x-amz-request-id";
-    proxy_hide_header "x-amz-storage-class";
-    proxy_hide_header "x-amz-server-side-encryption";
-    proxy_hide_header "Set-Cookie";
-    proxy_ignore_headers "Set-Cookie";
-    add_header Cache-Control "public";
-    add_header X-Frame-Options "SAMEORIGIN";
-    add_header X-Cache-Status $upstream_cache_status;
-    expires +1y;
-
-    # If object storage fails, fallback to PHP handler
-    error_page 404 = @asset_fallback;
-    error_page 403 = @asset_fallback;
-}
-
-location @php_asset_fallback {
-    # Handle with phpfpm
-    rewrite ^/media /get.php?$args last;
-    rewrite ^/static/(version\d*/)?(.*)$ /static.php?resource=$2 last;
-    echo_exec @phpfpm;
-}
-
-location @haproxy {
-    # Handle with haproxy
-    include /etc/nginx/proxy_to_haproxy.conf;
-    proxy_pass http://127.0.0.1:8080;
-}
-
-location @asset_fallback {
-    try_files "" $asset_fallback_handler;
-}
+To start serving media assets from your S3 bucket, you need to make some adjustments to your nginx configuration. Luckily, `hypernode-manage-vhosts` does this for you! If you are using Hypernode's object storage solution, all you need to do is run the following for relevant vhosts:
 
-location ~ ^/static/ {
-    expires max;
-
-    # Remove signature of the static files that is used to overcome the browser cache
-    location ~ ^/static/version\d*/ {
-        rewrite ^/static/version\d*/(.*)$ /static/$1 last;
-    }
-
-    location ~* \.(ico|jpg|jpeg|png|gif|svg|svgz|webp|avif|avifs|js|css|eot|ttf|otf|woff|woff2|html|json|webmanifest)$ {
-        add_header Cache-Control "public";
-        add_header X-Frame-Options "SAMEORIGIN";
-        expires +1y;
-
-        try_files $uri $uri/ @asset_fallback;
-    }
-    location ~* \.(zip|gz|gzip|bz2|csv|xml)$ {
-        add_header Cache-Control "no-store";
-        add_header X-Frame-Options "SAMEORIGIN";
-        expires    off;
-
-        try_files $uri $uri/ @asset_fallback;
-    }
-    try_files $uri $uri/ @asset_fallback;
-    add_header X-Frame-Options "SAMEORIGIN";
-}
+```bash
+hmv example.com --object-storage
+```
 
-location /media/ {
-    try_files $uri $uri/ @asset_fallback;
+In the case that you're using custom object storage, such as Amazon's S3, you will need to supply the bucket name and the bucket URL yourself:
+```bash
+hmv example.com --object-storage --object-storage-bucket mybucket --object-storage-url https://example_url.com
+```
 
-    location ~ ^/media/theme_customization/.*\.xml {
-        deny all;
-    }
+If you have previously set your own custom bucket name and URL, but have since switched to Hypernode's object storage solution, then you can use the `--object-storage-defaults` flag to force overwrite your values to Hypernode's default ones:
 
-    location ~* \.(ico|jpg|jpeg|png|gif|svg|svgz|webp|avif|avifs|js|css|swf|eot|ttf|otf|woff|woff2)$ {
-        add_header Cache-Control "public";
-        add_header X-Frame-Options "SAMEORIGIN";
-        expires +1y;
-	      try_files $uri $uri/ @object_storage_fallback;
-    }
-    location ~* \.(zip|gz|gzip|bz2|csv|xml)$ {
-        add_header Cache-Control "no-store";
-        add_header X-Frame-Options "SAMEORIGIN";
-        expires    off;
-	      try_files $uri $uri/ @object_storage_fallback;
-    }
-    add_header X-Frame-Options "SAMEORIGIN";
-}
+```bash
+hmv example.com --object-storage --object-storage-defaults
 ```
 
-Make sure to change the string `my_bucket_name` to the name of your bucket and keep in mind that your bucket URL might be different depending on your AWS region. For example, you might need to change it from `https://$bucket.s3.amazonaws.com$uri` to `https://s3.amazonaws.com/$bucket$uri` instead.
-Furthermore, ensure that your S3 bucket policies are configured correctly, so that only `/media` is publicly readable. For example:
+Furthermore, if you're using Amazon S3 as your bucket, ensure that your S3 bucket policies are configured correctly, so that only `/media` is publicly readable. For example:
 
 ```json
 {