bluelion

joined 1 month ago
[–] bluelion 2 points 1 day ago (4 children)

Do people actually eat pasta for breakfast?

[–] bluelion 1 points 5 days ago

Feren OS, a linux distro focused in customization. Started as a Linux Mint derivative, is now based on Ubuntu and/or Debian (I'm not really sure)

[–] bluelion 3 points 1 week ago* (last edited 1 week ago)

Before anything, you'll want to create a folder for the unix socket: mkdir /var/run/ytproxy and chown it to your reverse proxy's user and group.

The Docker files:

compose.yml


services:
  piped-frontend:
    image: 1337kavin/piped-frontend:latest
    container_name: piped-frontend
    environment:
      BACKEND_HOSTNAME: $API_ENDPOINT
    depends_on:
      - piped
    restart: unless-stopped
    networks:
      - proxy

  piped-proxy:
    image: 1337kavin/piped-proxy:latest
    container_name: piped-proxy
    environment:
      - UDS=1
    volumes:
      - /var/run/ytproxy:/app/socket  # unix socket location
    user: 1000:1000
    restart: unless-stopped
    networks:
      - proxy

  piped:
    image: 1337kavin/piped:latest
    container_name: piped-backend
    volumes:
      - ./piped/config/config.properties:/app/config.properties:ro
    depends_on:
      - piped-db
    restart: unless-stopped
    networks:
      - backend_piped
      - proxy

  piped-db:
    image: pgautoupgrade/pgautoupgrade:16-alpine
    container_name: piped-db
    environment:
      - POSTGRES_DB=$DB_NAME
      - POSTGRES_USER=$DB_USER
      - POSTGRES_PASSWORD=$DB_PASS
    volumes:
      - ./piped/pgdb:/var/lib/postgresql/data
    restart: unless-stopped
    networks:
      - backend_piped

networks:
  backend_piped:

  proxy:
    external: true

.env


API_ENDPOINT=  # no scheme prefix (ex. pipedapi.domain.example)
DB_NAME=
DB_USER=
DB_PASS=

To configure the reverse proxy (I use nginx), you can use Piped's recommended files with your domains. The linked repo also contains a template for the required config.properties.

Let me know if you run into issues, I'll be glad to help 🙂

[–] bluelion 9 points 1 week ago (4 children)

I use a private Piped instance

[–] bluelion 5 points 1 week ago

surely one of the games of all time

[–] bluelion 45 points 1 week ago (5 children)
  • a hello world doesn't need libraries in Java
  • installing JDK takes at most 5 steps, depending on the OS
  • a nullpointerexception is more likely the developper's fault (unassigned value, calling a function on a null object)
  • IntelliJ is easy to install and modern (granted, other IDEs are very ancient)
  • developping GUI apps is a PITA, no matter the ecosystem (generally)

The rest is more or less spot on (no idea about concurrency issues though)

[–] bluelion 5 points 1 week ago

We all have our own opinions :)

Can you give more details about mesh hubs? A quick search only returns stuff related to wifi.

[–] bluelion 1 points 1 week ago (2 children)

None of those work on Android, which is where I'll probably be the most active.

I've seen weechat recommended elsewhere too, I'll probably use it as desktop client.

[–] bluelion 1 points 1 week ago

The Lounge is how I got into IRC and it's very good! However, the web UI isn't that great on mobile, which led me to check out Android IRC apps and bouncers to sync everything across clients.

 

I've been enjoying chatting on IRC and was wondering if anyone has any relevant experience with any bouncers?

I tried setting up ZNC but could not get any clients to work with it.

I finally settled on soju with goguma as client, but since no up-to-date Docker container existed, I had to create my own Dockerfile for that.

For now, it's only available on my LAN (proxied through nginx), and am uncertain if exposing it externally is a good idea (I already have a VPN, but prefer to expose services if it's safe to do so).

[–] bluelion 22 points 2 weeks ago

Anon turns his whole family vegan because he's too nervous

[–] bluelion 39 points 3 weeks ago (7 children)

I heard grass tastes allright if you sprinkle some oil and salt on it. Never tried it myself, though.

view more: next ›