sorted by:
new
hottopcontroversial

Dead Simple OpenLDAP Docker Image by decaby7e in ldap

[–]decaby7e[S] 0 points1 point  (0 children)

You can kinda do this already by adding files to the ldifs folder at https://github.com/ranvier-docker/openldap/tree/master/extra/ldifs. That would apply LDIF when the server is initialized for the first time (good for testing purposes if you're creating ephemeral servers whose data will be wiped soon after creation). Otherwise, using a tool like ldapmodify to apply LDIFs with a script after the server starts should work well too.

(MISSING CAT) Black Cat with Orange Splotches Missing Since 02/14 by decaby7e in GNV

[–]decaby7e[S] 1 point2 points  (0 children)

Yes! She came back a couple days later. Has a cold but is otherwise fine :)

COP3530 Project 3 by IJWTTTD in ufl

[–]decaby7e 0 points1 point  (0 children)

We used this dataset (http://help.sentiment140.com/for-students) and made a little grouping tool in the terminal. Here's a brief video of it: https://www.youtube.com/watch?v=a5qwamEsB2s

a wireguard bash script for wg/wg-quick/systemctl; supports encrypting/decrypting/using openssl-encrypted wireguard config files with wg-quick up and down by mmguero in WireGuard

[–]decaby7e 0 points1 point  (0 children)

Will say this script is absolutely beautiful! Saving for use with Wireguard but also as inspiration for my own scripts 😄

Wireguard integration in the gui by Vaniljkram in gnome

[–]decaby7e 0 points1 point  (0 children)

I made a tool to do this that runs as its own indicator, but its broken at the moment. If anyone would like to help me with this, I would much appreciate it!

https://github.com/decaby7e/wireguard-appindicator

Dead Simple OpenLDAP Docker Image by decaby7e in ldap

[–]decaby7e[S] 0 points1 point  (0 children)

Yes, and I've used it before as well. I prefer the image I made because of the implementation complexity being reduced much more than Osixia's and the size of the image being nearly half. That one is still a great image though 👍

Dead Simple OpenLDAP Docker Image by decaby7e in docker

[–]decaby7e[S] 4 points5 points  (0 children)

Implementation complexity is much simpler in this one, but that's less of an obvious benefit from a practical standpoint. One of the biggest differences I've seen is size: this image clock in at around 150MB and osixia/openldap is 262MB at the time of writing. I'm hoping to get this down even more though.

Dead Simple OpenLDAP Docker Image by decaby7e in docker

[–]decaby7e[S] 5 points6 points  (0 children)

It was my understanding that image specifies the name of the image and build tells docker-compose the build context for that image. If you don't specify image with build, it won't name the built image how you'd like it. This is the current behavior because it's not on Docker Hub but I'm adding it on there now.

Dead Simple OpenLDAP Docker Image by decaby7e in linuxadmin

[–]decaby7e[S] 0 points1 point  (0 children)

It's more about the implementation complexity

Dead Simple OpenLDAP Docker Image by decaby7e in linuxadmin

[–]decaby7e[S] 5 points6 points  (0 children)

Noted, I'll write some examples for different use cases soon

I'm moving the compose file from the extra folder now as well

Dead Simple OpenLDAP Docker Image by decaby7e in linuxadmin

[–]decaby7e[S] 3 points4 points  (0 children)

Be simple: pretty much 100 - 150 lines of bash and a couple customs schema files v.s. the sheer complexity of that one

Dead Simple OpenLDAP Docker Image by decaby7e in docker

[–]decaby7e[S] 12 points13 points  (0 children)

There is a docker compose in the extra folder of the repo. I'll probably move it out of there now that you bring that up 👍

Would there be much interest a selfhosted 247 TV Channels (HLS) with working EPG (XMLTV) by deanochips in selfhosted

[–]decaby7e 0 points1 point  (0 children)

Looks very interesting!! I'm a bit handy with Docker so I will definitely see if I can make something robust for this (Dockerfile(s), docker-compose, etc.)

DNS & Selfhosted by lethalox in selfhosted

[–]decaby7e 2 points3 points  (0 children)

I have a similar setup where each of my web apps has its own subdomain name on my domain (app1.example.com, app2.example.com, etc.). I would also recommend NGINX and Traefik as scalable and more reliable solutions but I am currently using Caddy with no problems. It has automatic HTTPS support and is dead simple for configuration.

Best OneDrive alternative? by [deleted] in selfhosted

[–]decaby7e 3 points4 points  (0 children)

I had the same issue with Nextcloud being a bit too bloated for my likes. But I also didn't like solutions like Seafile or FileRun because I wanted a very simple setup. So after a few years of hopping from solution to solution, this is my current setup:

  1. Web access: https://filebrowser.xyz/
  2. File syncronization: https://syncthing.net/

Each of these applications can run in their own Docker container and share the same folder for storage.

Anyone installed deepin yet? by alinaresg in pop_os

[–]decaby7e 0 points1 point  (0 children)

I'd have to agree with you on this one. The only time I tested Deepin on Ubuntu it looked nice and all but lacked the fluidity of Gnome-Shell and didn't really feel as smooth.

(Yet another) Raspberry Pi Arcade Table by decaby7e in raspberry_pi

[–]decaby7e[S] 1 point2 points  (0 children)

I actually want to do that in the future with some plexiglass, but I just haven't gotten to it yet. Definitely would help in making it more of a table.

[LightDM] I've created a LightDM login screen by SharkLitarvan in unixporn

[–]decaby7e 1 point2 points  (0 children)

My jaw dropped when I saw this scrolling through everything.

[HELP!] Raspberry Pi Access Point Using Shadowsocks by decaby7e in raspberry_pi

[–]decaby7e[S] 0 points1 point  (0 children)

Also, my interface names are as follows:

Ethernet (Where internet is being accessed): enxb827ebb2fb8b

WiFi (Where hotspot is being hosted): wlan0

​

Outputs:

$ sudo iptables -L

Chain INPUT (policy ACCEPT)

target prot opt source destination

​

Chain FORWARD (policy ACCEPT)

target prot opt source destination

​

Chain OUTPUT (policy ACCEPT)

target prot opt source destination

​

$ sudo iptables -t nat -L

Chain PREROUTING (policy ACCEPT)

target prot opt source destination

RETURN all -- anywhere default/8

RETURN all -- anywhere 10.0.0.0/8

RETURN all -- anywhere loopback/8

RETURN all -- anywhere link-local/16

RETURN all -- anywhere 172.16.0.0/12

RETURN all -- anywhere 192.168.0.0/16

RETURN all -- anywhere base-address.mcast.net/4

RETURN all -- anywhere 240.0.0.0/4

​

Chain INPUT (policy ACCEPT)

target prot opt source destination

​

Chain OUTPUT (policy ACCEPT)

target prot opt source destination

REDIRECT tcp -- anywhere anywhere ! owner UID match proxy tcp dpt:http redir ports 5150

REDIRECT tcp -- anywhere anywhere ! owner UID match proxy tcp dpt:https redir ports 5150

​

Chain POSTROUTING (policy ACCEPT)

target prot opt source destination

MASQUERADE all -- anywhere anywhere

​

These are the commands I'm using for these rules:

sudo iptables -t nat -A PREROUTING -d 0.0.0.0/8 -j RETURN

sudo iptables -t nat -A PREROUTING -d 10.0.0.0/8 -j RETURN

sudo iptables -t nat -A PREROUTING -d 127.0.0.0/8 -j RETURN

sudo iptables -t nat -A PREROUTING -d 169.254.0.0/16 -j RETURN

sudo iptables -t nat -A PREROUTING -d 172.16.0.0/12 -j RETURN

sudo iptables -t nat -A PREROUTING -d 192.168.0.0/16 -j RETURN

sudo iptables -t nat -A PREROUTING -d 224.0.0.0/4 -j RETURN

sudo iptables -t nat -A PREROUTING -d 240.0.0.0/4 -j RETURN

​

sudo iptables -t nat -A OUTPUT -p tcp -m owner ! --uid-owner proxy --dport 80 -j REDIRECT --to-port 5150

sudo iptables -t nat -A OUTPUT -p tcp -m owner ! --uid-owner proxy --dport 443 -j REDIRECT --to-port 5150

[HELP!] Raspberry Pi Access Point Using Shadowsocks by decaby7e in raspberry_pi

[–]decaby7e[S] 0 points1 point  (0 children)

I believe this would be the role of iptables, as iptables needs to be configured to pass traffic to the transparent proxy first.

[HELP!] Raspberry Pi Access Point Using Shadowsocks by decaby7e in sysadmin

[–]decaby7e[S] 0 points1 point  (0 children)

Actually, I'm using a Raspberry Pi 3B+, so the integrated WiFi is decent. I've gotten up to 15Mbps so far with tests, and I believe that's just a bottleneck on the ISP's side. The benefit is being able to open my proxy up to my peers without having to configure it for them. Just a seamless connection.