ngxson/portainer-ce-without-annoying

A drop-in replacement for portainer/portainer-ce, without annoying UI elements or tracking script

portainer-ce-without-annoying

This is a drop-in replacement for portainer/portainer-ce, without annoying UI elements.

portainer-ce-without-annoying is NOT a fork of portainer-ce. It is just an overlay script / proxy to inject styles / scripts, allow removing DOM elements.

Before		After
	==>
	==>
	==>

Bonus: tracking script is also removed. See this issue

How to use

If you already have portainer-ce installation, just replace portainer/portainer-ce:latest with ngxson/portainer-ce-without-annoying:latest

For example, if you use the command from the official installation guide, the command will be:

docker volume create portainer_data
docker run -d \
  -p 8000:8000 -p 9443:9443 \
  --name portainer \
  --restart=always \
  -v /var/run/docker.sock:/var/run/docker.sock \
  -v portainer_data:/data \
  ngxson/portainer-ce-without-annoying:latest

Alternatively, you can use this docker-compose.yml

portainer-ce-without-annoying's Issues

Block tracker

Hi! Awesome work, this really helps.

I see my adblocker blocking https://cdn.matomo.cloud/portainer-ce.matomo.cloud/matomo.js.

Can we make it a setting that it somehow does not include this JS when tracking is disabled?

Again, awesome job!

Can there be a toggle for the old interface??

I hate the new interface. Can there be a toggle for the old flat interface. The new ones too weird looking .

Why is it double the size of official?

see

Latest tag stuck at 2.19.0 for me

Latest tag stuck at 2.19.0 for me,changing docker compose file to point directly at 2.19.1 works though.

Authentication - OAuth - Apply button not visible

Under authentication settings, choosing OAuth, the save button under Actions does not appear.

Use github actions or other CI/CD pipeline for automatic updates and transparency.

First of all, love you for creating this project!

As far as I understand, you are using the build_and_push.sh script locally to update the docker image for this project on your docker hub, right?

I would like to suggest to setup a small CI/CD pipeline using github actions (or drone or similar) to automate this process.
Some reasons, that would be helpful:

• Less work for you (duh) :)
• Automatic updates every time portainer is updated. Even in times where you might not be immediately able to run the script.
• Transparency for the build process. While I trust you and could check the image itself before pulling, having the log and output of the buildprocess available for all to see on github actions (or a public drone page) allows user to see at a glance that no security flaws have been introduced with the modified image, which I think is important for an integral backbone to ones digital infrastructure, like portainer is.
• Automatic upversioning to preserve old tags and always updating the "latest" tag.
• Automatic release on github releases (helps people who watch the repo to be notified of new versions to update).
• Automatic release to both Github container repo and dockerhub, since the anti consumer behaviour of dockerhub, means, an alternative container repo could be more reliable.

Here is some ideas for the implementation (using Github actions):

• Watch for new releases of the portainer-ce docker hub, or github repo to trigger new builds in this repo.
  • Potentially limit automatic updates to a "beta" tag instead of the "latest" tag, if you want more manual control.
• Just copy the portainer-ce version number for ease of use and backwards compatibility.
• Watch for pushes to this repos main branch using the "release" or similar github tag to trigger rebuilt and replacement of current image version to introduce new features (in case some more important stuff is added later).
• Automatically replace the latest tag on the container repo with your newest build.
• Push to both ghcr and docker hub.

If you need any help with that, I would love to point you in the right direction and/or make a small PR :)

(not an issue, just for upload screeshots)

Before		After
	==>
	==>
	==>

Cannot use -H command line option

Using the -H command line option does not seem to work.

node: bad option: -H

Without this, you can't use a socket-proxy

Docker hub image for ARM64 and ARMv7

Maybe someone need that for their single board computer. Also, ARM64 servers are getting cheap.