Christian Engvall

The Pihole web interface tells you to run pihole -up to get the latest version. But if you are running pihole as a docker container we need to do it a little bit different.

To update pihole; Open a terminal and do the following:

Stop the container:

docker stop pihole

Pull the latest Pihole

docker pull pihole/pihole

Remove your existing pihole container

docker rm -f pihole

Start container

#Depending on how you set it up you might run
./docker-run.sh

#or

docker run pihole/pihole

After updating this the custom blacklist was still intact.

To be able to place orders locally using a payment app it needs to be able to communicate with the outside world. Lets have a look how to get that working with ngrok.

1. Download and register ngrok

Download ngrok and sign up free account. We will need that to use https. After you have signed up you will get an authtoken. Fire up you ngrok-terminal and type:

ngrok authtoken <my-token>

use ngrok.exe if you are using windows.

ngrok.exe authtoken <my-token>

2. Exposing a server

Open up your docker-compose.yaml-file and scroll down to the ports section of the desired app. Shown below is the direct-payment example, in which we are interested in knowing that it uses port 10011.

The direct-payment app doesn’t need ngrok to work. But since it is present in the default installation of Litium we will use it as an example. You are probably doing this for a payment app such as Svea or Klarna.

  direct-payment:
    ports:
    - "10010:80"
    - "10011:443"

Now go back to your terminal and run:

ngrok http https://localhost:10011

Or this in Windows:

ngrok.exe http https://localhost:10011

You will now see something looking like this:

ngrok by @inconshreveable                                                                                                                   (Ctrl+C to quit)                                                                                                                                                            Session Status                online                                                                                                                        Account                       My name (Plan: Free)                                                                                                Version                       2.3.666                                                                                                                        Region                        United States (us)                                                                                                            Web Interface                 http://127.0.0.1:4040                                                                                                         Forwarding                    http://61c5-1515-4-97kh-88.ngrok.io -> https://localhost:14001                                                                  Forwarding                    https://61c5-1515-4-97kh-88.ngrok.io -> https://localhost:14001                                                                                                                                                                                                                             Connections                   ttl     opn     rt1     rt5     p50     p90                                                                                                                 0       0       0.00    0.00    0.00    0.00                                                                                  

Copy the ngrok-url using https and lets continue.

3. Using the ngrok url

Go back to your docker-compose.yaml-file and set the AppMetadata__AppUrl to your ngrok url.

  direct-payment:
    ports:
    - "10010:80"
    - "10011:443"
    environment:
    - AppMetadata__AppUrl=https://61c5-1515-4-97kh-88.ngrok.io

4. Docker time

Now stop your applications in docker and then run:

docker-compose up

And that is it. Thanks to Nils at Litium support!

fail: IdentityServer4.Validation.ClientSecretValidator[0]
      Client secret validation failed for client:

I got the error Client secret validation failed for client when using a Litium app one day. The reason was that Litium apps are not built to be used in a multiple development environment scenario and another developer has reinstalled an app on his machine. That way the app got new service account-credentials, that my environment did not know about.

To fix this you need to uninstall the app in question and remove the folder containing the app information as explained in the Payment and shipping documentation.

Litium apps are single install only, when you have installed your app once that apps install-link will not work again. If needed just follow the steps below to clear the app for re-installation:

Stop the container of the app you want to clear

Open the folder where you keep the docker-compose.yaml file from the docker-task

In the /data-subfolder of that folder you will find a direct-payment and a direct-shipment folder, delete the one you want to clear

Start the container again and the install link will work

Thanks to Nils at the Litium support for pointing this out to me.

One way to access the shared files folder that is used in some projects is to let the IIS application pool use the identity of the user that has access to that shared folder. That won’t work now when we are using the Kestrel web server.

Instead you can map that shared folder as a Network drive and reference that in appsettings.json. In Windows you right click in the explorer and select Add network location, on the mac you open Finder, select Go in the menu and click on Connect to server.

"Folder": {
  "Local": "..\\Files",
  "Shared": "\\\\network.path\\sharedfiles\\customer\\Files"
},

If you are going to use a multi-site setup where the sites should look a bit different to each other you need to change the default webpack configuration that is delivered with the Accelerator.

This is tested with the first version of the Litium 8 accelerator. Previous and later versions may differ.

1. Change entries

Add a new .scss file at Litium.Accelerator.Mvc/Client/Styles that we call secondsite.scss.

The existing site.scss has been renamed to firstsite.scss in this example.

Open up Litium.Accelerator.Mvc/Client/webpack/webpack.es6.js and find the entry points. At the time when I’m writing this post the entries looks like this:

entry: {
    app: [
        path.resolve(JS_DIR, 'index.js'),
        path.resolve(CSS_DIR, 'site.scss'),
    ],
},

Now lets split that up to add a second entry:

entry: {
    app: [
        path.resolve(JS_DIR, 'index.js'),
    ],
    firstsite: [
        path.resolve(CSS_DIR, 'firstsite.scss'),
    ],
    secondsite: [
        path.resolve(CSS_DIR, 'secondsite.scss'),
    ]
},

2. Update the MiniCssExtractPlugin

Scroll down to the MiniCssExtractPlugin settings in the same file as above. Right now it looks like this:

plugins: [
    new RemovePlugin({
        before: {
            include: [BUILD_DIR],
            log: false,
        },
    }),
    new MiniCssExtractPlugin({
        filename: '../css/site.min.css',
    }),
    // new BundleAnalyzerPlugin(),
],

Update this section to look like this instead:

plugins: [
    new RemovePlugin({
        before: {
            include: [BUILD_DIR],
            log: false,
        },
    }),
    new MiniCssExtractPlugin({
        filename: '../css/[name].min.css',
    }),
    // new BundleAnalyzerPlugin(),
],

If you have yarn run build:w running you should restart it. This will generate two separate .css-files in the output directory.

3.Reference the correct file

This is out of scope of the post so I leave this up to you. But you must reference the correct css-file in Litium.Accelerator.Mvc/Views/Framework/Head.cshtml

4. Read more

You can read more about Webpack Entry points in the official docs