[GH-ISSUE #707] Dark Mode Support

Owner

Originally created by @redtripleAAA on GitHub (Nov 9, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/707

RFE for Dark Mode Support

Originally created by @redtripleAAA on GitHub (Nov 9, 2020). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/707 RFE for Dark Mode Support

kerem added the

enhancement

label

kerem commented

Author

Owner

@C-Fu commented on GitHub (Dec 29, 2020):

This would be awesome!

@C-Fu commented on GitHub (Dec 29, 2020): This would be awesome!

kerem commented

Author

Owner

@vMeph commented on GitHub (Jan 20, 2021):

+ 1 for it :)

@vMeph commented on GitHub (Jan 20, 2021): `+ `1 for it :)

kerem commented

Author

Owner

@wrdx commented on GitHub (Feb 17, 2021):

It looks like Tabler supports it: https://preview.tabler.io/layout-dark.html

@wrdx commented on GitHub (Feb 17, 2021): It looks like Tabler supports it: https://preview.tabler.io/layout-dark.html

kerem commented

Author

Owner

@jc21 commented on GitHub (Feb 17, 2021):

And it indeed looks sexy. I'm rewriting the UI with react for version 3, which which be much easier to integrate a dark mode.

@jc21 commented on GitHub (Feb 17, 2021): And it indeed looks sexy. I'm rewriting the UI with react for version 3, which which be much easier to integrate a dark mode.

kerem commented

Author

Owner

@jonasled commented on GitHub (Apr 10, 2021):

I've played a bit around with the SCSS and also implementing one without the tabler resources is not very difficult: https://gitlab.jonasled.de/jonasled/nginx-proxy-manager-dark/-/blob/master/frontend/scss/darkmode.scss

@jonasled commented on GitHub (Apr 10, 2021): I've played a bit around with the SCSS and also implementing one without the tabler resources is not very difficult: https://gitlab.jonasled.de/jonasled/nginx-proxy-manager-dark/-/blob/master/frontend/scss/darkmode.scss

kerem commented

Author

Owner

@TropicLegend commented on GitHub (Jul 16, 2021):

Where can I change these files?

@TropicLegend commented on GitHub (Jul 16, 2021): Where can I change these files?

kerem commented

Author

Owner

@root9191 commented on GitHub (Aug 20, 2021):

I've played a bit around with the SCSS and also implementing one without the tabler resources is not very difficult: https://gitlab.jonasled.de/jonasled/nginx-proxy-manager-dark/-/blob/master/frontend/scss/darkmode.scss

Hello, how Can i implent the Dark Mode in my Proxy Manager Version 2.9.7?

@root9191 commented on GitHub (Aug 20, 2021): > I've played a bit around with the SCSS and also implementing one without the tabler resources is not very difficult: https://gitlab.jonasled.de/jonasled/nginx-proxy-manager-dark/-/blob/master/frontend/scss/darkmode.scss Hello, how Can i implent the Dark Mode in my Proxy Manager Version 2.9.7?

kerem commented

Author

Owner

@FroggMaster commented on GitHub (Nov 27, 2021):

I created a Dark Mode theme VIA CSS which can be easily applied VIA the Stylish Extension. Stylish will allow you to toggle the theme quickly if you so choose. In addition it will allow for you to make easy/live modifications if you'd like to change the theme to your preferences. I have heavily commented my CSS to give you some understanding of the areas I've changed.

You can find the Stylish theme that I created here:
https://userstyles.org/styles/220202/nginx-proxy-manager-dark-theme

You can also create a custom CSS then mount it within the NGINX Proxy Manager docker container. This I would consider to be a little bit more of an advanced method, but this would mean no matter where NGINX Proxy manager was accessed from it would display the custom theme; Unlike with the Stylish extension, where the extension must be installed for the theme to be visible. I'm honestly surprised there is no option within the GUI to provide custom CSS. Or instructions on simply mounting a CSS file within the container. Please note that the CSS for the Stylish theme I provided will only modify portions of the CSS I wanted to change. It is not a complete CSS for NGINX Proxy Manager and I would not recommend mounting it in your docker container.

NGINX Also allows for sub filters to be used when passing a webpage or server through it, which in turn can cause CSS to be loaded this way as well. If you were to pass NGINX Manager through itself, and apply a sub filter this would allow for modification of the CSS as well.

There are A LOT of ways themes/custom CSS could be implemented into this application and I would HIGHLY suggest it. Even if it's just VIA the ability to apply your own custom CSS overtop of the original CSS. User's will eventually create themes and there will be an immense variety of options. Until the develop opts to support this functionality though, I doubt we will see many themes developed for the application.

It's obvious that this is a sought after feature though. Within 24 hrs of me submitting my theme, there was thirteen separate user's whom had installed it. In such a short period of time, that screams to me others are deeply interested in a Dark Mode option.

@FroggMaster commented on GitHub (Nov 27, 2021): I created a Dark Mode theme VIA CSS which can be easily applied VIA the Stylish Extension. Stylish will allow you to toggle the theme quickly if you so choose. In addition it will allow for you to make easy/live modifications if you'd like to change the theme to your preferences. I have heavily commented my CSS to give you some understanding of the areas I've changed. You can find the Stylish theme that I created here: [https://userstyles.org/styles/220202/nginx-proxy-manager-dark-theme](https://userstyles.org/styles/220202/nginx-proxy-manager-dark-theme) You can also create a custom CSS then mount it within the NGINX Proxy Manager docker container. This I would consider to be a little bit more of an advanced method, but this would mean no matter where NGINX Proxy manager was accessed from it would display the custom theme; Unlike with the Stylish extension, where the extension must be installed for the theme to be visible. I'm honestly surprised there is no option within the GUI to provide custom CSS. Or instructions on simply mounting a CSS file within the container. Please note that the CSS for the Stylish theme I provided will only modify portions of the CSS I wanted to change. It is not a complete CSS for NGINX Proxy Manager and I would not recommend mounting it in your docker container. NGINX Also allows for sub filters to be used when passing a webpage or server through it, which in turn can cause CSS to be loaded this way as well. If you were to pass NGINX Manager through itself, and apply a sub filter this would allow for modification of the CSS as well. There are A LOT of ways themes/custom CSS could be implemented into this application and I would HIGHLY suggest it. Even if it's just VIA the ability to apply your own custom CSS overtop of the original CSS. User's will eventually create themes and there will be an immense variety of options. Until the develop opts to support this functionality though, I doubt we will see many themes developed for the application. It's obvious that this is a sought after feature though. Within 24 hrs of me submitting my theme, there was thirteen separate user's whom had installed it. In such a short period of time, that screams to me others are deeply interested in a Dark Mode option.

kerem commented

Author

Owner

@ItsNoted commented on GitHub (Dec 17, 2021):

I created a Dark Mode theme VIA CSS [...]

Installing browser plugins is not an option for me.

@ItsNoted commented on GitHub (Dec 17, 2021): > I created a Dark Mode theme VIA CSS [...] Installing browser plugins is not an option for me.

kerem commented

Author

Owner

@operinko commented on GitHub (Dec 17, 2021):

I would love to see theme-park.dev support on nginx-proxy-manager, though that seems to imply requiring linuxserver.io builds

@operinko commented on GitHub (Dec 17, 2021): I would love to see theme-park.dev support on nginx-proxy-manager, though that seems to imply requiring linuxserver.io builds

kerem commented

Author

Owner

@FroggMaster commented on GitHub (Jan 3, 2022):

I created a Dark Mode theme VIA CSS [...]

Installing browser plugins is not an option for me.

There are alternative suggestions in my post. Though, the most non-technical method would be to use an Extension.

Apply CSS VIA NGINX itself (You will need to reverse proxy NPM to do this)
Mount a new CSS file overtop of the existing CSS file VIA Docker

@FroggMaster commented on GitHub (Jan 3, 2022): > > I created a Dark Mode theme VIA CSS [...] > > Installing browser plugins is not an option for me. There are alternative suggestions in my post. Though, the most non-technical method would be to use an Extension. - Apply CSS VIA NGINX itself (You will need to reverse proxy NPM to do this) - Mount a new CSS file overtop of the existing CSS file VIA Docker

kerem commented

Author

Owner

@root9191 commented on GitHub (Jan 3, 2022):

I created a Dark Mode theme VIA CSS [...]

Installing browser plugins is not an option for me.

There are alternative suggestions in my post. Though, the most non-technical method would be to use an Extension.

Apply CSS VIA NGINX itself (You will need to reverse proxy NPM to do this)

Mount a new CSS file overtop of the existing CSS file VIA Docker

Could you explain, how i can apply the CSS in Nginx? Do i need the Advanced Tab for this?

@root9191 commented on GitHub (Jan 3, 2022): > > > I created a Dark Mode theme VIA CSS [...] > > > > Installing browser plugins is not an option for me. > > There are alternative suggestions in my post. Though, the most non-technical method would be to use an Extension. > > - Apply CSS VIA NGINX itself (You will need to reverse proxy NPM to do this) > > - Mount a new CSS file overtop of the existing CSS file VIA Docker Could you explain, how i can apply the CSS in Nginx? Do i need the Advanced Tab for this?

kerem commented

Author

Owner

@Amoenus commented on GitHub (Jan 18, 2022):

Here's my attempt to create dark theme CSS, it's very chatty but should cover almost everything
Dark Theme CSS
Comes with a dark scroll bar though ;)

@Amoenus commented on GitHub (Jan 18, 2022): Here's my attempt to create dark theme CSS, it's very chatty but should cover almost everything [Dark Theme CSS](https://gist.github.com/Amoenus/3c7ef321d83afcd046ee28a960b52977) Comes with a dark scroll bar though ;)

kerem commented

Author

Owner

@mellowism commented on GitHub (Jan 18, 2022):

Here's my attempt to create dark theme CSS, it's very chatty but should cover almost everything Dark Theme CSS Comes with a dark scroll bar though ;)

My Gravatar didn't like it, went all gray. Other than that it looks real nice!

@mellowism commented on GitHub (Jan 18, 2022): > Here's my attempt to create dark theme CSS, it's very chatty but should cover almost everything [Dark Theme CSS](https://gist.github.com/Amoenus/3c7ef321d83afcd046ee28a960b52977) Comes with a dark scroll bar though ;) My Gravatar didn't like it, went all gray. Other than that it looks real nice! ![image](https://user-images.githubusercontent.com/18271469/149956292-5c13f928-5ce6-4285-8982-608af9d84aa6.png)

kerem commented

Author

Owner

@lammersbjorn commented on GitHub (Jan 19, 2022):

Here's my attempt to create dark theme CSS, it's very chatty but should cover almost everything Dark Theme CSS Comes with a dark scroll bar though ;)

How do I use this?

@lammersbjorn commented on GitHub (Jan 19, 2022): > Here's my attempt to create dark theme CSS, it's very chatty but should cover almost everything [Dark Theme CSS](https://gist.github.com/Amoenus/3c7ef321d83afcd046ee28a960b52977) Comes with a dark scroll bar though ;) How do I use this?

kerem commented

Author

Owner

@Amoenus commented on GitHub (Jan 19, 2022):

Here's my attempt to create dark theme CSS, it's very chatty but should cover almost everything Dark Theme CSS Comes with a dark scroll bar though ;)

How do I use this?

I just put it in Stylus since Stylish had some shady things going on that I don't care enough to remember.

@Amoenus commented on GitHub (Jan 19, 2022): > > Here's my attempt to create dark theme CSS, it's very chatty but should cover almost everything [Dark Theme CSS](https://gist.github.com/Amoenus/3c7ef321d83afcd046ee28a960b52977) Comes with a dark scroll bar though ;) > > How do I use this? I just put it in [Stylus](https://add0n.com/stylus.html) since Stylish had some shady things going on that I don't care enough to remember.

kerem commented

Author

Owner

@Amoenus commented on GitHub (Jan 19, 2022):

Here's my attempt to create dark theme CSS, it's very chatty but should cover almost everything Dark Theme CSS Comes with a dark scroll bar though ;)

My Gravatar didn't like it, went all gray. Other than that it looks real nice!

Interesting. Mine seems to show fine.

Just in case I've made it against the latest v2.9.15 (at the time of writing). So maybe check your version.

But this is getting out of topic, so comment on a gist if you need any help

@Amoenus commented on GitHub (Jan 19, 2022): > > Here's my attempt to create dark theme CSS, it's very chatty but should cover almost everything [Dark Theme CSS](https://gist.github.com/Amoenus/3c7ef321d83afcd046ee28a960b52977) Comes with a dark scroll bar though ;) > > My Gravatar didn't like it, went all gray. Other than that it looks real nice! ![image](https://user-images.githubusercontent.com/18271469/149956292-5c13f928-5ce6-4285-8982-608af9d84aa6.png) Interesting. Mine seems to show fine. ![image](https://user-images.githubusercontent.com/5391396/150107831-ac68d61c-3762-4831-ab1f-8578256e12cc.png) Just in case I've made it against the latest v2.9.15 (at the time of writing). So maybe check your version. But this is getting out of topic, so comment on a gist if you need any help

kerem commented

Author

Owner

@lammersbjorn commented on GitHub (Jan 19, 2022):

Here's my attempt to create dark theme CSS, it's very chatty but should cover almost everything Dark Theme CSS Comes with a dark scroll bar though ;)

How do I use this?

I just put it in Stylus since Stylish had some shady things going on that I don't care enough to remember.

Alright

@lammersbjorn commented on GitHub (Jan 19, 2022): > > > Here's my attempt to create dark theme CSS, it's very chatty but should cover almost everything [Dark Theme CSS](https://gist.github.com/Amoenus/3c7ef321d83afcd046ee28a960b52977) Comes with a dark scroll bar though ;) > > > > > > How do I use this? > > I just put it in [Stylus](https://add0n.com/stylus.html) since Stylish had some shady things going on that I don't care enough to remember. Alright

kerem commented

Author

Owner

@root9191 commented on GitHub (Jan 21, 2022):

Is there a way to implement this custom.css via the Nginx Proxy Manager so every Device in the Network is affected?

@root9191 commented on GitHub (Jan 21, 2022): Is there a way to implement this custom.css via the Nginx Proxy Manager so every Device in the Network is affected?

kerem commented

Author

Owner

@jonasled commented on GitHub (Jan 23, 2022):

Yes, you can add the stylesheet on the server, if you place the file in frontend/scss/ and add the import in the style.scss

@jonasled commented on GitHub (Jan 23, 2022): Yes, you can add the stylesheet on the server, if you place the file in `frontend/scss/` and add the import in the `style.scss`

kerem commented

Author

Owner

@root9191 commented on GitHub (Jan 24, 2022):

can you explain that to me in a bit more detail?
so i need to a map the custom.css to the Container and then simply import the custom.css in the style.css or the main.css?

@root9191 commented on GitHub (Jan 24, 2022): can you explain that to me in a bit more detail? so i need to a map the custom.css to the Container and then simply import the custom.css in the style.css or the main.css?

kerem commented

Author

Owner

@kmanwar89 commented on GitHub (Feb 2, 2022):

Yes, you can add the stylesheet on the server, if you place the file in frontend/scss/ and add the import in the style.scss

Hi @jonasled - would you be able to provide some specific instructions on where these files can be found? Myself, and I'm sure others, are likely running nginx proxy manager via a docker container, so access to some of these core files may not be available.

Would I be correct in my (limited) understanding that we'd need to either:

Execute a bash command inside the npm docker container and drop the files directly into the frontend/scss folder you mentioned or
Make the relevant additions to the css files and re-compile the docker image?

I'm not sure what the best path forward here would be, but it sounds like many other people would like dark mode as well, so your help is appreciated!

@kmanwar89 commented on GitHub (Feb 2, 2022): > Yes, you can add the stylesheet on the server, if you place the file in `frontend/scss/` and add the import in the `style.scss` Hi @jonasled - would you be able to provide some specific instructions on where these files can be found? Myself, and I'm sure others, are likely running nginx proxy manager via a docker container, so access to some of these core files may not be available. Would I be correct in my (limited) understanding that we'd need to either: 1) Execute a bash command inside the npm docker container and drop the files directly into the _frontend/scss_ folder you mentioned or 2) Make the relevant additions to the css files and re-compile the docker image? I'm not sure what the best path forward here would be, but it sounds like many other people would like dark mode as well, so your help is appreciated!

kerem commented

Author

Owner

@jonasled commented on GitHub (Feb 2, 2022):

Changing the configuration of a running container dosn't work. You have to take the sourcecode and then place the dark.scss in frontend => scss. Afterwards you have to add @import "darkmode"; to your style.scss (in the same directory)

Afterwards you have to build the container with the following script:

echo 'Setting Version'
sed -i "s/0.0.0/${BUILD_VERSION}/" frontend/package.json
sed -i "s/0.0.0/${BUILD_VERSION}/" backend/package.json

echo 'Building Frontend ...'
bash scripts/frontend-build

echo 'Checking Syntax ...'
docker run --rm -v "$(pwd)/backend:/app" -v "$(pwd)/global:/app/global" -w /app node:latest sh -c "yarn install && yarn eslint . && rm -rf node_modules"

echo 'Docker Build ...'
docker build --pull --no-cache --compress -t "nginx-proxy-manager-dark:latest" -f docker/Dockerfile --build-arg TARGETPLATFORM=linux/amd64 --build-arg BUILDPLATFORM=linux/amd64 --build-arg BUILD_VERSION="${BUILD_VERSION}" --build-arg BUILD_COMMIT="${BUILD_COMMIT}" --build-arg BUILD_DATE="$(date '+%Y-%m-%d %T %Z')" .

@jonasled commented on GitHub (Feb 2, 2022): Changing the configuration of a running container dosn't work. You have to take the sourcecode and then place the dark.scss in frontend => scss. Afterwards you have to add `@import "darkmode";` to your style.scss (in the same directory) Afterwards you have to build the container with the following script: ```bash echo 'Setting Version' sed -i "s/0.0.0/${BUILD_VERSION}/" frontend/package.json sed -i "s/0.0.0/${BUILD_VERSION}/" backend/package.json echo 'Building Frontend ...' bash scripts/frontend-build echo 'Checking Syntax ...' docker run --rm -v "$(pwd)/backend:/app" -v "$(pwd)/global:/app/global" -w /app node:latest sh -c "yarn install && yarn eslint . && rm -rf node_modules" echo 'Docker Build ...' docker build --pull --no-cache --compress -t "nginx-proxy-manager-dark:latest" -f docker/Dockerfile --build-arg TARGETPLATFORM=linux/amd64 --build-arg BUILDPLATFORM=linux/amd64 --build-arg BUILD_VERSION="${BUILD_VERSION}" --build-arg BUILD_COMMIT="${BUILD_COMMIT}" --build-arg BUILD_DATE="$(date '+%Y-%m-%d %T %Z')" . ```

kerem commented

Author

Owner

@kmanwar89 commented on GitHub (Feb 4, 2022):

Changing the configuration of a running container dosn't work. You have to take the sourcecode and then place the dark.scss in frontend => scss. Afterwards you have to add @import "darkmode"; to your style.scss (in the same directory)

Afterwards you have to build the container with the following script:

echo 'Setting Version'
sed -i "s/0.0.0/${BUILD_VERSION}/" frontend/package.json
sed -i "s/0.0.0/${BUILD_VERSION}/" backend/package.json

echo 'Building Frontend ...'
bash scripts/frontend-build

echo 'Checking Syntax ...'
docker run --rm -v "$(pwd)/backend:/app" -v "$(pwd)/global:/app/global" -w /app node:latest sh -c "yarn install && yarn eslint . && rm -rf node_modules"

echo 'Docker Build ...'
docker build --pull --no-cache --compress -t "nginx-proxy-manager-dark:latest" -f docker/Dockerfile --build-arg TARGETPLATFORM=linux/amd64 --build-arg BUILDPLATFORM=linux/amd64 --build-arg BUILD_VERSION="${BUILD_VERSION}" --build-arg BUILD_COMMIT="${BUILD_COMMIT}" --build-arg BUILD_DATE="$(date '+%Y-%m-%d %T %Z')" .

Thanks for your help with this. If I understood your instructions correctly, then the first step would be to clone the repository for the dark mode, which would be located here.

From there, I executed both the frontend-build script and the docker run command you have listed. However, when running the final docker build command, I receive the following error:

The command '/bin/bash -o pipefail -c echo "fs.file-max = 65535" > /etc/sysctl.conf && apt-get update && apt-get install -y --no-install-recommends jq logrotate && apt-get clean && rm -rf /var/lib/apt/lists/*' returned a non-zero code: 100

For reference, I'm running this on a fresh install of Ubuntu Server 21.10. Any ideas what may be causing this? It is not an error I've encountered previously.

Here is the full output:

kadar@shadowserve:~/snap/docker/nginx-proxy-manager-dark$ docker build --pull --no-cache --compress -t "nginx-proxy-manager-dark:latest" -f docker/Dockerfile --build-arg TARGETPLATFORM=linux/amd64 --build-arg BUILDPLATFORM=linux/amd64 --build-arg BUILD_VERSION="${BUILD_VERSION}" --build-arg BUILD_COMMIT="${BUILD_COMMIT}" --build-arg BUILD_DATE="$(date '+%Y-%m-%d %T %Z')" .
Sending build context to Docker daemon  92.51MB
Step 1/22 : FROM jc21/nginx-full:node
node: Pulling from jc21/nginx-full
Digest: sha256:50210acee3db8afa1143a9064b5fc2163bd82043531d105765ea79e338ff6a58
Status: Image is up to date for jc21/nginx-full:node
 ---> d7305a5ab702
Step 2/22 : ARG TARGETPLATFORM
 ---> Running in 30a0def89ec6
Removing intermediate container 30a0def89ec6
 ---> acf51dd780d9
Step 3/22 : ARG BUILD_VERSION
 ---> Running in 527616c44226
Removing intermediate container 527616c44226
 ---> 0cd3a59afd9f
Step 4/22 : ARG BUILD_COMMIT
 ---> Running in 705e06e5febe
Removing intermediate container 705e06e5febe
 ---> 23fc763722d6
Step 5/22 : ARG BUILD_DATE
 ---> Running in b2d34378c038
Removing intermediate container b2d34378c038
 ---> 71f46d2fb6c8
Step 6/22 : ENV SUPPRESS_NO_CONFIG_WARNING=1 	S6_FIX_ATTRS_HIDDEN=1 	S6_BEHAVIOUR_IF_STAGE2_FAILS=1 	NODE_ENV=production 	NPM_BUILD_VERSION="${BUILD_VERSION}" 	NPM_BUILD_COMMIT="${BUILD_COMMIT}" 	NPM_BUILD_DATE="${BUILD_DATE}"
 ---> Running in 2d79b60a4763
Removing intermediate container 2d79b60a4763
 ---> 28245fd75157
Step 7/22 : RUN echo "fs.file-max = 65535" > /etc/sysctl.conf 	&& apt-get update 	&& apt-get install -y --no-install-recommends jq logrotate 	&& apt-get clean 	&& rm -rf /var/lib/apt/lists/*
 ---> Running in 31d59d5ab2cc
Ign:1 http://security.debian.org/debian-security stable/updates InRelease
Err:2 http://security.debian.org/debian-security stable/updates Release
  404  Not Found [IP: 151.101.66.132 80]
Get:3 http://deb.debian.org/debian stable InRelease [116 kB]
Get:4 https://deb.nodesource.com/node_15.x buster InRelease [4584 B]
Get:5 http://deb.debian.org/debian stable-updates InRelease [39.4 kB]
Get:6 http://deb.debian.org/debian stable/main amd64 Packages [8183 kB]
Get:7 https://deb.nodesource.com/node_15.x buster/main amd64 Packages [762 B]
Get:8 http://deb.debian.org/debian stable-updates/main amd64 Packages [2596 B]
Reading package lists...
E: The repository 'http://security.debian.org/debian-security stable/updates Release' does not have a Release file.
The command '/bin/bash -o pipefail -c echo "fs.file-max = 65535" > /etc/sysctl.conf 	&& apt-get update 	&& apt-get install -y --no-install-recommends jq logrotate 	&& apt-get clean 	&& rm -rf /var/lib/apt/lists/*' returned a non-zero code: 100

@kmanwar89 commented on GitHub (Feb 4, 2022): > Changing the configuration of a running container dosn't work. You have to take the sourcecode and then place the dark.scss in frontend => scss. Afterwards you have to add `@import "darkmode";` to your style.scss (in the same directory) > > Afterwards you have to build the container with the following script: > > ```shell > echo 'Setting Version' > sed -i "s/0.0.0/${BUILD_VERSION}/" frontend/package.json > sed -i "s/0.0.0/${BUILD_VERSION}/" backend/package.json > > echo 'Building Frontend ...' > bash scripts/frontend-build > > echo 'Checking Syntax ...' > docker run --rm -v "$(pwd)/backend:/app" -v "$(pwd)/global:/app/global" -w /app node:latest sh -c "yarn install && yarn eslint . && rm -rf node_modules" > > echo 'Docker Build ...' > docker build --pull --no-cache --compress -t "nginx-proxy-manager-dark:latest" -f docker/Dockerfile --build-arg TARGETPLATFORM=linux/amd64 --build-arg BUILDPLATFORM=linux/amd64 --build-arg BUILD_VERSION="${BUILD_VERSION}" --build-arg BUILD_COMMIT="${BUILD_COMMIT}" --build-arg BUILD_DATE="$(date '+%Y-%m-%d %T %Z')" . > ``` Thanks for your help with this. If I understood your instructions correctly, then the first step would be to clone the repository for the dark mode, which would be located [here](https://gitlab.jonasled.de/jonasled/nginx-proxy-manager-dark/-/tree/master). From there, I executed both the frontend-build script and the docker run command you have listed. However, when running the final docker build command, I receive the following error: ```The command '/bin/bash -o pipefail -c echo "fs.file-max = 65535" > /etc/sysctl.conf && apt-get update && apt-get install -y --no-install-recommends jq logrotate && apt-get clean && rm -rf /var/lib/apt/lists/*' returned a non-zero code: 100``` For reference, I'm running this on a fresh install of Ubuntu Server 21.10. Any ideas what may be causing this? It is not an error I've encountered previously. Here is the full output: ``` kadar@shadowserve:~/snap/docker/nginx-proxy-manager-dark$ docker build --pull --no-cache --compress -t "nginx-proxy-manager-dark:latest" -f docker/Dockerfile --build-arg TARGETPLATFORM=linux/amd64 --build-arg BUILDPLATFORM=linux/amd64 --build-arg BUILD_VERSION="${BUILD_VERSION}" --build-arg BUILD_COMMIT="${BUILD_COMMIT}" --build-arg BUILD_DATE="$(date '+%Y-%m-%d %T %Z')" . Sending build context to Docker daemon 92.51MB Step 1/22 : FROM jc21/nginx-full:node node: Pulling from jc21/nginx-full Digest: sha256:50210acee3db8afa1143a9064b5fc2163bd82043531d105765ea79e338ff6a58 Status: Image is up to date for jc21/nginx-full:node ---> d7305a5ab702 Step 2/22 : ARG TARGETPLATFORM ---> Running in 30a0def89ec6 Removing intermediate container 30a0def89ec6 ---> acf51dd780d9 Step 3/22 : ARG BUILD_VERSION ---> Running in 527616c44226 Removing intermediate container 527616c44226 ---> 0cd3a59afd9f Step 4/22 : ARG BUILD_COMMIT ---> Running in 705e06e5febe Removing intermediate container 705e06e5febe ---> 23fc763722d6 Step 5/22 : ARG BUILD_DATE ---> Running in b2d34378c038 Removing intermediate container b2d34378c038 ---> 71f46d2fb6c8 Step 6/22 : ENV SUPPRESS_NO_CONFIG_WARNING=1 S6_FIX_ATTRS_HIDDEN=1 S6_BEHAVIOUR_IF_STAGE2_FAILS=1 NODE_ENV=production NPM_BUILD_VERSION="${BUILD_VERSION}" NPM_BUILD_COMMIT="${BUILD_COMMIT}" NPM_BUILD_DATE="${BUILD_DATE}" ---> Running in 2d79b60a4763 Removing intermediate container 2d79b60a4763 ---> 28245fd75157 Step 7/22 : RUN echo "fs.file-max = 65535" > /etc/sysctl.conf && apt-get update && apt-get install -y --no-install-recommends jq logrotate && apt-get clean && rm -rf /var/lib/apt/lists/* ---> Running in 31d59d5ab2cc Ign:1 http://security.debian.org/debian-security stable/updates InRelease Err:2 http://security.debian.org/debian-security stable/updates Release 404 Not Found [IP: 151.101.66.132 80] Get:3 http://deb.debian.org/debian stable InRelease [116 kB] Get:4 https://deb.nodesource.com/node_15.x buster InRelease [4584 B] Get:5 http://deb.debian.org/debian stable-updates InRelease [39.4 kB] Get:6 http://deb.debian.org/debian stable/main amd64 Packages [8183 kB] Get:7 https://deb.nodesource.com/node_15.x buster/main amd64 Packages [762 B] Get:8 http://deb.debian.org/debian stable-updates/main amd64 Packages [2596 B] Reading package lists... E: The repository 'http://security.debian.org/debian-security stable/updates Release' does not have a Release file. The command '/bin/bash -o pipefail -c echo "fs.file-max = 65535" > /etc/sysctl.conf && apt-get update && apt-get install -y --no-install-recommends jq logrotate && apt-get clean && rm -rf /var/lib/apt/lists/*' returned a non-zero code: 100 ```

kerem commented

Author

Owner

@archef2000 commented on GitHub (Apr 25, 2022):

I tried the Theme from @Amoenus on Gist and just combined the main.css under /app/frontend/css/main.css in the docker container and the dark-theme and it all funktions.

@archef2000 commented on GitHub (Apr 25, 2022): I tried the Theme from @Amoenus on[ Gist](https://gist.github.com/Amoenus/3c7ef321d83afcd046ee28a960b52977) and just combined the main.css under /app/frontend/css/main.css in the docker container and the dark-theme and it all funktions.

kerem commented

Author

Owner

@hellblue commented on GitHub (May 4, 2022):

I use nginx proxy manager without docker and tried it. It works good and looks much better now.

I tried the Theme from @Amoenus on Gist and just combined the main.css under /app/frontend/css/main.css in the docker container and the dark-theme and it all funktions.

@hellblue commented on GitHub (May 4, 2022): I use nginx proxy manager without docker and tried it. It works good and looks much better now. > I tried the Theme from @Amoenus on[ Gist](https://gist.github.com/Amoenus/3c7ef321d83afcd046ee28a960b52977) and just combined the main.css under /app/frontend/css/main.css in the docker container and the dark-theme and it all funktions.

kerem commented

Author

Owner

@Trackhe commented on GitHub (May 16, 2022):

Please make a dark mode standard. My eyes are bleeding.

@Trackhe commented on GitHub (May 16, 2022): Please make a dark mode standard. My eyes are bleeding.

kerem commented

Author

Owner

@root9191 commented on GitHub (May 17, 2022):

I use now the Dark Theme from theme-park.dev - looks really good 😎

@root9191 commented on GitHub (May 17, 2022): I use now the Dark Theme from theme-park.dev - looks really good 😎

kerem commented

Author

Owner

@Amoenus commented on GitHub (May 19, 2022):

Nice one @root9191. I am switching to these themes as well.

For people using Stylus the cheeky way to use the theme is like this

@import url("https://theme-park.dev/css/base/nginx-proxy-manager/organizr.css");

@Amoenus commented on GitHub (May 19, 2022): Nice one @root9191. I am switching to these themes as well. For people using Stylus the cheeky way to use the theme is like this ```CSS @import url("https://theme-park.dev/css/base/nginx-proxy-manager/organizr.css"); ```

kerem commented

Author

Owner

@kmanwar89 commented on GitHub (Jul 17, 2022):

Is there any progress on this dark mode w/o the use of additional add-ons?

@kmanwar89 commented on GitHub (Jul 17, 2022): Is there any progress on this dark mode w/o the use of additional add-ons?

kerem commented

https://github.com/GilbN/theme.park/blob/develop/docker-mods/nginx-proxy-manager/root/etc/cont-init.d/98-themepark

Author

Owner

@GilbN commented on GitHub (Aug 1, 2022):

Nice one @root9191. I am switching to these themes as well.

For people using Stylus the cheeky way to use the theme is like this
@import url("https://theme-park.dev/css/base/nginx-proxy-manager/organizr.css");

I've added a script you can mount btw.
https://docs.theme-park.dev/themes/nginx-proxy-manager/#docker

@GilbN commented on GitHub (Aug 1, 2022): > Nice one @root9191. I am switching to these themes as well. > > For people using Stylus the cheeky way to use the theme is like this > > ```css > @import url("https://theme-park.dev/css/base/nginx-proxy-manager/organizr.css"); > ``` I've added a script you can mount btw. https://docs.theme-park.dev/themes/nginx-proxy-manager/#docker https://github.com/GilbN/theme.park/blob/develop/docker-mods/nginx-proxy-manager/root/etc/cont-init.d/98-themepark

kerem commented

Author

Owner

@CarloApri commented on GitHub (Aug 13, 2022):

@GilbN I'm having some troubles settings this up:
following the docs you linked I downloaded "98-themepark" from the repo, then you say to mount it like follows.

    volumes:
      - /your/save/path/98-themepark-npm:/etc/cont-init.d/99-themepark

I'm doing that in the Nging Proxy Manager's docker-compose.yml, is that correct? In the volume entry do we have to point to the script itself or to the folder containing it?
The file is "98-themepark" but it's "98-themepark-npm" in the example provided, same for the chmod +x command.

@CarloApri commented on GitHub (Aug 13, 2022): @GilbN I'm having some troubles settings this up: following the docs you linked I downloaded "98-themepark" from the repo, then you say to mount it like follows. ``` volumes: - /your/save/path/98-themepark-npm:/etc/cont-init.d/99-themepark ``` I'm doing that in the Nging Proxy Manager's docker-compose.yml, is that correct? In the volume entry do we have to point to the script itself or to the folder containing it? The file is "98-themepark" but it's "98-themepark-npm" in the example provided, same for the chmod +x command.

kerem commented

Author

Owner

@GilbN commented on GitHub (Aug 13, 2022):

@GilbN I'm having some troubles settings this up: following the docs you linked I downloaded "98-themepark" from the repo, then you say to mount it like follows.
    volumes:
      - /your/save/path/98-themepark-npm:/etc/cont-init.d/99-themepark
I'm doing that in the Nging Proxy Manager's docker-compose.yml, is that correct? In the volume entry do we have to point to the script itself or to the folder containing it? The file is "98-themepark" but it's "98-themepark-npm" in the example provided, same for the chmod +x command.

There's a bug in the script. Change APP_FILEPATH to /app/frontend

And yes, point it to the file. And the name doesn't matter.

@GilbN commented on GitHub (Aug 13, 2022): > @GilbN I'm having some troubles settings this up: following the docs you linked I downloaded "98-themepark" from the repo, then you say to mount it like follows. > > ``` > volumes: > - /your/save/path/98-themepark-npm:/etc/cont-init.d/99-themepark > ``` > > I'm doing that in the Nging Proxy Manager's docker-compose.yml, is that correct? In the volume entry do we have to point to the script itself or to the folder containing it? The file is "98-themepark" but it's "98-themepark-npm" in the example provided, same for the chmod +x command. There's a bug in the script. Change `APP_FILEPATH` to `/app/frontend` And yes, point it to the file. And the name doesn't matter.

kerem commented

Author

Owner

@cisxxc commented on GitHub (Aug 17, 2022):

@GilbN I'm having some troubles settings this up: following the docs you linked I downloaded "98-themepark" from the repo, then you say to mount it like follows.
    volumes:
      - /your/save/path/98-themepark-npm:/etc/cont-init.d/99-themepark
I'm doing that in the Nging Proxy Manager's docker-compose.yml, is that correct? In the volume entry do we have to point to the script itself or to the folder containing it? The file is "98-themepark" but it's "98-themepark-npm" in the example provided, same for the chmod +x command.
There's a bug in the script. Change APP_FILEPATH to /app/frontend

And yes, point it to the file. And the name doesn't matter.

When will the script be updated? - I see 'APP_FILEPATH' referenced serveral times throughout the script. Do I need to edit every single one and replace it with 'app/frontend'?

@cisxxc commented on GitHub (Aug 17, 2022): > > @GilbN I'm having some troubles settings this up: following the docs you linked I downloaded "98-themepark" from the repo, then you say to mount it like follows. > > ``` > > volumes: > > - /your/save/path/98-themepark-npm:/etc/cont-init.d/99-themepark > > ``` > > > > > > > > > > > > > > > > > > > > > > > > I'm doing that in the Nging Proxy Manager's docker-compose.yml, is that correct? In the volume entry do we have to point to the script itself or to the folder containing it? The file is "98-themepark" but it's "98-themepark-npm" in the example provided, same for the chmod +x command. > > There's a bug in the script. Change `APP_FILEPATH` to `/app/frontend` > > And yes, point it to the file. And the name doesn't matter. When will the script be updated? - I see 'APP_FILEPATH' referenced serveral times throughout the script. Do I need to edit every single one and replace it with 'app/frontend'?

kerem commented

Author

Owner

@GilbN commented on GitHub (Aug 18, 2022):

@GilbN I'm having some troubles settings this up: following the docs you linked I downloaded "98-themepark" from the repo, then you say to mount it like follows.
volumes:
  - /your/save/path/98-themepark-npm:/etc/cont-init.d/99-themepark
I'm doing that in the Nging Proxy Manager's docker-compose.yml, is that correct? In the volume entry do we have to point to the script itself or to the folder containing it? The file is "98-themepark" but it's "98-themepark-npm" in the example provided, same for the chmod +x command.

There's a bug in the script. Change APP_FILEPATH to /app/frontend

And yes, point it to the file. And the name doesn't matter.

When will the script be updated? - I see 'APP_FILEPATH' referenced serveral times throughout the script. Do I need to edit every single one and replace it with 'app/frontend'?

The script has been updated. Did you you try it?
https://github.com/GilbN/theme.park/blob/develop/docker-mods/nginx-proxy-manager/root/etc/cont-init.d/98-themepark

@GilbN commented on GitHub (Aug 18, 2022): > > > @GilbN I'm having some troubles settings this up: following the docs you linked I downloaded "98-themepark" from the repo, then you say to mount it like follows. > > > > ``` > > > > volumes: > > > > - /your/save/path/98-themepark-npm:/etc/cont-init.d/99-themepark > > > > ``` > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > I'm doing that in the Nging Proxy Manager's docker-compose.yml, is that correct? In the volume entry do we have to point to the script itself or to the folder containing it? The file is "98-themepark" but it's "98-themepark-npm" in the example provided, same for the chmod +x command. > > > > > > There's a bug in the script. Change `APP_FILEPATH` to `/app/frontend` > > > > > > And yes, point it to the file. And the name doesn't matter. > > > > When will the script be updated? - I see 'APP_FILEPATH' referenced serveral times throughout the script. Do I need to edit every single one and replace it with 'app/frontend'? The script has been updated. Did you you try it? https://github.com/GilbN/theme.park/blob/develop/docker-mods/nginx-proxy-manager/root/etc/cont-init.d/98-themepark

kerem commented

Author

Owner

@henkiewie commented on GitHub (Oct 28, 2022):

The script has been updated. Did you you try it? https://github.com/GilbN/theme.park/blob/develop/docker-mods/nginx-proxy-manager/root/etc/cont-init.d/98-themepark

Hi,
It worked for me. Is there also a way back?
[Edit]
Yes there is coment out the volume 😄

@henkiewie commented on GitHub (Oct 28, 2022): > The script has been updated. Did you you try it? https://github.com/GilbN/theme.park/blob/develop/docker-mods/nginx-proxy-manager/root/etc/cont-init.d/98-themepark Hi, It worked for me. Is there also a way back? [Edit] Yes there is coment out the volume 😄

kerem commented

Author

Owner

@CarloApri commented on GitHub (Mar 30, 2023):

How can I specify which theme to use (eg aquamarine)?
Here there are quite some if you scroll down

edit: found, line 45

@CarloApri commented on GitHub (Mar 30, 2023): How can I specify which theme to use (eg aquamarine)? [Here ](https://docs.theme-park.dev/themes/nginx-proxy-manager/#docker) there are quite some if you scroll down edit: found, [line 45](https://github.com/GilbN/theme.park/blob/develop/docker-mods/nginx-proxy-manager/root/etc/cont-init.d/98-themepark)

kerem commented

Author

Owner

@ozdeadmeat commented on GitHub (Jun 29, 2023):

Would be nice if they just added this functionality by default as pretty much everything else I use has a dark mode.

@ozdeadmeat commented on GitHub (Jun 29, 2023): Would be nice if they just added this functionality by default as pretty much everything else I use has a dark mode.

kerem commented

Author

Owner

@DST73 commented on GitHub (Oct 30, 2023):

Hi,
I have installed NGINX using this script from https://tteck.github.io/Proxmox/ witch creates an Container in Proxmox
is there a way to change it to dark mode on such an installation?

Thank you!

@DST73 commented on GitHub (Oct 30, 2023): Hi, I have installed NGINX using this script from https://tteck.github.io/Proxmox/ witch creates an Container in Proxmox is there a way to change it to dark mode on such an installation? Thank you!

kerem commented

Author

Owner

@SebastianGwizdala commented on GitHub (Jan 18, 2024):

+1 from me as well

@SebastianGwizdala commented on GitHub (Jan 18, 2024): +1 from me as well

kerem commented

Author

Owner

@github-actions[bot] commented on GitHub (Aug 27, 2024):

Issue is now considered stale. If you want to keep it open, please comment 👍

@github-actions[bot] commented on GitHub (Aug 27, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:

kerem commented

Author

Owner

@BluePixel4k commented on GitHub (Aug 27, 2024):

👍

@BluePixel4k commented on GitHub (Aug 27, 2024): 👍

kerem commented

Author

Owner

@zackwithak13 commented on GitHub (Aug 27, 2024):

👍🏻

@zackwithak13 commented on GitHub (Aug 27, 2024): 👍🏻

kerem commented

Author

Owner

@Cocolin67 commented on GitHub (Sep 12, 2024):

Any news yet ?

@Cocolin67 commented on GitHub (Sep 12, 2024): Any news yet ?

kerem commented

Author

Owner

@Ajes1337 commented on GitHub (Sep 22, 2024):

please add dark theme support

@Ajes1337 commented on GitHub (Sep 22, 2024): please add dark theme support

kerem commented

Author

Owner

@andmpel commented on GitHub (Oct 24, 2024):

Dark mode support please

@andmpel commented on GitHub (Oct 24, 2024): Dark mode support please

kerem commented

Author

Owner

@CarloApri commented on GitHub (Oct 24, 2024):

You can already get the dark theme:
in your docker-compose.yml for nginx proxy manager, add the following to the volumes section

    volumes:
      - ./theme/98-themepark:/etc/cont-init.d/99-themepark

in the same folder as your docker-compose.yml create a "theme" folder, and create this 98-themepark file inside it (literally copy and paste), cd theme and make it executable chmod +x 98-themepark-npm

edit line 45 if you want a different theme

@CarloApri commented on GitHub (Oct 24, 2024): You can already get the dark theme: in your docker-compose.yml for nginx proxy manager, add the following to the volumes section ``` volumes: - ./theme/98-themepark:/etc/cont-init.d/99-themepark ``` in the same folder as your docker-compose.yml create a "theme" folder, and create this [98-themepark](https://github.com/themepark-dev/theme.park/blob/develop/docker-mods/nginx-proxy-manager/root/etc/cont-init.d/98-themepark) file inside it (literally copy and paste), `cd theme` and make it executable `chmod +x 98-themepark-npm` edit line 45 if you want a [different theme](https://docs.theme-park.dev/themes/nginx-proxy-manager/) ![Screenshot 2024-10-25 001917](https://github.com/user-attachments/assets/0636a028-dbf9-4439-bf17-d509d341332b)

kerem commented

Sources:
https://docs.theme-park.dev/themes/nginx-proxy-manager/
https://docs.theme-park.dev/setup/#nginx

Author

Owner

@petrhusak commented on GitHub (Oct 25, 2024):

You can set dark mode also without bind mount:
If you are using Nginx Proxy Manager as a proxy for the Nginx Proxy Manager itself, you can set the dark mode directly in the proxy settings. Just add custom location with this settings:

proxy_set_header Accept-Encoding "";
sub_filter
   '</head>'
   '<link rel="stylesheet" type="text/css" href="https://theme-park.dev/css/base/nginx-proxy-manager/organizr.css">
   </head>';
sub_filter_once on;

It should look something like this (forward hostname nginx-proxy-manager is the name of my container):

If you want different theme, change organizr.css value. Available css themes:

aquamarine.css
hotline.css
hotpink.css
dracula.css
dark.css
organizr.css
space-gray.css
overseerr.css
plex.css
nord.css
maroon.css

@petrhusak commented on GitHub (Oct 25, 2024): You can set dark mode also without bind mount: If you are using Nginx Proxy Manager as a proxy for the Nginx Proxy Manager itself, you can set the dark mode directly in the proxy settings. Just add custom location with this settings: ``` proxy_set_header Accept-Encoding ""; sub_filter '</head>' '<link rel="stylesheet" type="text/css" href="https://theme-park.dev/css/base/nginx-proxy-manager/organizr.css"> </head>'; sub_filter_once on; ``` It should look something like this (forward hostname **nginx-proxy-manager** is the name of my container): ![npm](https://github.com/user-attachments/assets/b93104cf-d59e-4152-ad56-646153b249cb) If you want different theme, change `organizr.css` value. Available css themes: - aquamarine.css - hotline.css - hotpink.css - dracula.css - dark.css - organizr.css - space-gray.css - overseerr.css - plex.css - nord.css - maroon.css Sources: [https://docs.theme-park.dev/themes/nginx-proxy-manager/](https://docs.theme-park.dev/themes/nginx-proxy-manager/) [https://docs.theme-park.dev/setup/#nginx](https://docs.theme-park.dev/setup/#nginx)

kerem commented

Author

Owner

@AndyVRD commented on GitHub (Dec 13, 2024):

Any reason why this is not working? Running NGINX Proxy Manager in a LXC container with Proxmox. Checked the hostname and it's nginxproxymanager like I used in the css template.

@AndyVRD commented on GitHub (Dec 13, 2024): Any reason why this is not working? Running NGINX Proxy Manager in a LXC container with Proxmox. Checked the hostname and it's nginxproxymanager like I used in the css template. ![image](https://github.com/user-attachments/assets/3069cd86-2e53-403b-838d-9cf33fdb42a0)

kerem commented

Author

Owner

@shalafi99 commented on GitHub (Dec 13, 2024):

I had to do a CTRL-SHIFT-R (=reload and ignore cache) in Google Chrome to make it go into effect, after noticing it would only work right away inside an incognito/inprivate tab.

@shalafi99 commented on GitHub (Dec 13, 2024): I had to do a CTRL-SHIFT-R (=reload and ignore cache) in Google Chrome to make it go into effect, after noticing it would only work right away inside an incognito/inprivate tab.

kerem commented

Author

Owner

@RobLoach commented on GitHub (Jan 29, 2025):

Duplicate of https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4314 .

@RobLoach commented on GitHub (Jan 29, 2025): Duplicate of https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4314 .

kerem commented

Author

Owner

@tuanhm107 commented on GitHub (Apr 26, 2025):

Any reason why this is not working? Running NGINX Proxy Manager in a LXC container with Proxmox. Checked the hostname and it's nginxproxymanager like I used in the css template.

you're doing it wrong.

just use 127.0.0.1 (the host itself) in IP adress
don't adjust the URL with your host name, it's a website duh
CTRL+SHIFT+R to reload

It worked for me

@tuanhm107 commented on GitHub (Apr 26, 2025): > Any reason why this is not working? Running NGINX Proxy Manager in a LXC container with Proxmox. Checked the hostname and it's nginxproxymanager like I used in the css template. > > ![image](https://github.com/user-attachments/assets/3069cd86-2e53-403b-838d-9cf33fdb42a0) you're doing it wrong. - just use 127.0.0.1 (the host itself) in IP adress - don't adjust the URL with your host name, it's a website duh - CTRL+SHIFT+R to reload It worked for me

kerem commented

Author

Owner

@IvanCarapovic commented on GitHub (Apr 26, 2025):

The workaround with CSS is simple and works, but it would still be better/simpler to have a dropdown in settings where I can just select the appropriate. Also if you aren't using NPM to proxy to NPM, the hack won't work so...

@IvanCarapovic commented on GitHub (Apr 26, 2025): The workaround with CSS is simple and works, but it would still be better/simpler to have a dropdown in settings where I can just select the appropriate. Also if you aren't using NPM to proxy to NPM, the hack won't work so...

kerem commented

Author

Owner

@mdrxy commented on GitHub (Sep 5, 2025):

+1

@mdrxy commented on GitHub (Sep 5, 2025): +1

kerem commented

Author

Owner

@CrazyWolf13 commented on GitHub (Nov 5, 2025):

this has been implemented, please close this issue

@CrazyWolf13 commented on GitHub (Nov 5, 2025): this has been implemented, please close this issue

kerem commented

Author

Owner

@C-Fu commented on GitHub (Nov 10, 2025):

The new dark mode is epic! Hats off to the devs, I appreciate it man!

Please close this issue thanks!

@C-Fu commented on GitHub (Nov 10, 2025): The new dark mode is epic! Hats off to the devs, I appreciate it man! Please close this issue thanks!

kerem commented