Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Nginx maps feel wrong to me.

Bot and agent blacklisting and country blocking is pain in the ass.

Simple Variable Usage both environment or json/config ones and Configuration Includes will help a lot.



The current config looks like this:

    interface project_config {
        domain_default: string;
        path: {
            storage: string;
            web_root: string;
        };
        redirect_domain: {
            [key:string]: [string, number];
        };
        redirect_internal: {
            [key:string]: store_string;
        };
        service_port: {
            open: number;
            secure: number;
        };
    }
Any domain not in the "redirect_domain" list is an alias for services on the server. The "default_domain" can receive priority features unspecified domains cannot. Domains listed in the "redirect_domain" list are pushed into the proxy. The [string, number] portion of the "redirect_domain" list allows for identification of host and port. If the host is not specified the server's local IP is the default.

What kind of variables would you have in mind to push into the server? Knowing what kinds of such features are desirable might lead me to think about supporting them in a variety of ways.

I do not have a block list feature yet, but I will write that. I could block by IP address on the socket, HTTP host header, HTTP referrer header.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: