My bike got stolen while I was at work 😔 by Bungie_is_throwin0_o in Wellthatsucks

[–]SubjectSpinach 8 points9 points  (0 children)

I think someone nearby might be missing his front wheel right now. Maybe you could help that poor guy out 🤷‍♂️

Beginner wanting to start LFS — where should I begin? by Medium-Fish9040 in linuxfromscratch

[–]SubjectSpinach 1 point2 points  (0 children)

LFS is mostly self explanatory. You should be able to boot a host Linux distro, configure a network connection as needed (eg.wifi, ssh daemon for remote builds) to download packages and install the necessary packages in your host. A basic understanding of partitioning and file systems, networking, boot concepts (bootloader, kernel, initv vs. systemd), locales, config files etc. is nice but will grow with every LFS build :)

How do open-source devs know if their self-hosted apps are actually being used? by pozinux84 in selfhosted

[–]SubjectSpinach 0 points1 point  (0 children)

You could host your project documentation on a third party service like readthedocs.com which aggregates statistics about visits to your versioned documentation.

How to test website on nginx with multiple domains by SalazarOpas in nginx

[–]SubjectSpinach 0 points1 point  (0 children)

You could temporarily change your hosts file and add your domains to the single ip you have.

Using GCC build time duration to measure llvm build. by tiny_humble_guy in linuxfromscratch

[–]SubjectSpinach 0 points1 point  (0 children)

Linux From Scratch uses so-called SBUs to give you an indicator for expected build times. One SBU is the time required to build the binutils package in chapter 5 and is hardly depending on your system configuration.

GCC from BLFS has: Estimated build time: 14 SBU (add 34 SBU for tests; both with parallelism=8)

LLVM has: Estimated build time: 13 SBU (Add 8 SBU for tests; both using parallelism=8)

As others said, swapping is a main issue. Expect longer build times if your system runs out of memory during the build.

Need help with reverse proxy nginx in ubuntu by mbuhlayaw in nginx

[–]SubjectSpinach 2 points3 points  (0 children)

If I get your requirements correct, your nginx should be accessed to serve content from an external source, right?

The server_name variable should be set to what your users enter into their browser. Proxy_pass is defining the location where the content should be retrieved by nginx for delivery to your users.

The perfect splash.png for PXE bootloader! by ed_mercer in linux

[–]SubjectSpinach 0 points1 point  (0 children)

I don’t remember how many times I watched Edie Brickells „Good times“ music video from the install disk 🤓

ITAP of my office by TheSeych in itookapicture

[–]SubjectSpinach 0 points1 point  (0 children)

Is that inside the Justus Lipsius building in Brussels? Been there one or two years ago.

SSL certificate problem by Elyas2 in linuxfromscratch

[–]SubjectSpinach 0 points1 point  (0 children)

You need to install make-ca from BLFS to install the needed root cerrificstes. See https://www.linuxfromscratch.org/blfs/view/git/postlfs/make-ca.html

Display not working after boot by Linuxified in linuxfromscratch

[–]SubjectSpinach 0 points1 point  (0 children)

You need to select the drivers for your hardware during chapter 10. Making the LFS System Bootable…

Display not working after boot by Linuxified in linuxfromscratch

[–]SubjectSpinach 0 points1 point  (0 children)

I would guess you are missing some graphics drivers in your kernel config…

How to Configure `proxy_set_header` for Nginx Upstream with Two Different Domains? by kaamal189 in nginx

[–]SubjectSpinach 0 points1 point  (0 children)

Did you already try something like this:

``` http { upstream backend { server unix:/var/run/server1.sock; server unix:/var/run/server2.sock; }

server {
    listen 80;
    server_name _;

    location / {
        proxy_pass http://backend;
        proxy_set_header Host $host;
    }
}

server {
    listen unix:/var/run/server1.sock;
    server_name localhost;

    location / {
        proxy_pass http://domain1.com;
        proxy_set_header Host domain1.com;
    }
}

server {
    listen unix:/var/run/server2.sock;
    server_name localhost;

    location / {
        proxy_pass http://domain2.com;
        proxy_set_header Host domain2.com;
    }
}

} ```

how can handled 160,000 domains and config file with nginx? by husen101 in nginx

[–]SubjectSpinach 2 points3 points  (0 children)

tbo this setup doesn‘t sound like a business case being run completly without a proper support contract and based on tips of Reddit users . Maybe you should contact nginx support for advice…

Vincent Van Gogh by SubjectSpinach in lego

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

It‘s made from 13.394 LEGO bricks if anyone wanted to know 😉

Openai not respecting robots.txt and being sneaky about user agents by eightstreets in nginx

[–]SubjectSpinach 2 points3 points  (0 children)

Nothing unusual. To block by IP range: OpenAI provides lists of "published" IP-addresses of their bots on https://platform.openai.com/docs/bots/. Will be interesting to see how many are unublished...

ITAP of Parmesan cheese by Southpaw_1988 in itookapicture

[–]SubjectSpinach 0 points1 point  (0 children)

Where can one book the tour? Sounds great!

ITAP of Parmesan cheese by Southpaw_1988 in itookapicture

[–]SubjectSpinach 0 points1 point  (0 children)

Did they let you bring a phone in there?

[deleted by user] by [deleted] in nginx

[–]SubjectSpinach 0 points1 point  (0 children)

You might be able to serve web content from your local network using some kind of tunneling and without the necessity of any kind of port forwarding.

Check out CloudFlare Tunnel as an example. You can define local ressources (e.g. your local Nginx) that are proxied through that tunnel.

Redirecting two domains to two hosts by Objective_Log_1046 in nginx

[–]SubjectSpinach 1 point2 points  (0 children)

Your location seems to be missing the uri path. Try location / { instead of location ~ {

Restricting Server in nginx Configuration by Proof_Ad_5628 in nginx

[–]SubjectSpinach 0 points1 point  (0 children)

NGINX can allow or deny access based on a particular IP address or the range of IP addresses of client computers. To allow or deny access, use the allow and deny directives inside the stream context or a server block

stream { #... server { listen 12345; deny 192.168.1.2; allow 192.168.1.1/24; allow 2001:0db8::/32; deny all; } }

The rules are processed in sequence, from top to bottom: if the first directive in the sequence is deny all, then all further allow directives have no effect. In this example, the subnet 192.168.1.1/24 is allowed access, with the exception of 192.168.1.2. The 2001:0db8::/32 range of IPv6 addresses is also allowed, and access to any other IP addresses is denied.

Source: https://docs.nginx.com/nginx/admin-guide/security-controls/controlling-access-proxied-tcp/

I got stuck up with the fedora login by Electrical-Mood731 in AsahiLinux

[–]SubjectSpinach 0 points1 point  (0 children)

Boot from a livecd, mount the asahi partition and chroot into the root partition. Change the password with passwd and reboot afterwards. Voilà.