Hey,

Some of you may know me for Jotty and Cr*nmaster, been quiet with my head down lately improving my apps and trying to build a searxng alternative for myself.

Whilst I have used searxng for about a year now, I have had quite a few personal gripes with it (mostly stuff I personally would prefer worked differently) so in the past few weeks I have decided to make my take on it and ran it happily locally. Since publishing the beta to my discord server I ended up building a fairly extensive tool.

Degoog is actually pretty minimal, there’s no much to it aside from a very comprehensive plugin/extension system. The idea being users can create their own engines, themes and plugins that hook into the core application and do… pretty much anything, from adding stuff to the result page (e.g. speedtests, tmdb information, ip retrieval, rss feeds embedded on the home page) to full on OIDC systems.

This is still very much in beta and I figured the best way to get it out of beta would be to publish it to a wider audience (currently some users in our discord server have been testing it fairly successfully and i’ve been on top of bug fixing).

Repo: https://github.com/fccview/degoog

Official extensions: https://github.com/fccview/fccview-degoog-extensions

Docs: https://fccview.github.io/degoog

You can install custom plugins/extensions. You can make your own repo and add it to the store page in the settings, or you can just have your own plugins locally for yourself.

Let me know what you think, and feel free to ask any questions and feel free to join our discord (link in releases page on any of my apps) for a more direct chat about things <3

  • Karna@lemmy.mlEnglish
    1·
    3 hours ago

    Note that I’m running it on a rootless docker instance, and NOT on Podman. So, the following solution might or might not work for you.

    services:
  degoog:
    image: ghcr.io/fccview/degoog:latest
    volumes:
      - ./.data:/app/data
    user: "0:0"
    ports:
      - "4444:4444"
    restart: unless-stopped

    Explanation: rootless docker works a bit different from rootful docker. user 1000 (which is you on your server/machine) will be mapped to a different UID (e.g. 32555). This is to ensure that any process in docker container can’t have access to folders/files that you have access to, in case it manages to break free of docker containerization.

    When you put user: “0:0” in a rootless docker container, it will assume your UID 1000 (which is you on your server/machine) inside docker container.

    While it solves the file permission issue, but it is NOT a recommended way.

    with user:1000:1000

    with user:0:0