4

Fuck these apache2 and nginx configuration that fucking make my life miserable. Why can\'t I fucking edit the files inside /var/www/html? Fuck that. Why can\'t I access a subdirectory inside it? Fuck! In Node.js, you can fire up your server pretty easily. Then you tell us that JavaScript sucks? Fuck me dead.

Comments
  • 7
    ..... it's very simple... if you know what you're doimg, just like anything, can't just pick it up and expect to know how to use it
  • 3
    Just look which permissions you need with ls -l and add your user to the group.
  • 2
    Node is easy because you run a single command with low setup.

    Apache needs a bit more love and needs to be setup for the environment your trying to create.

    Without knowing in context what your setting Apache up for. It sounds like you have root ownership of the /HTML folder and accessing it with a user account that’s not permitted. You can set up groups or give ownership to your user.
  • 0
    Just do it in Node 😄
    LAMP's dead, the new king is MEAN
  • 3
    @Froot LAMP is definetly not dead mate
  • 1
    @ScribeOfGoD Actually you're probably right, it's still twitching 😆
  • 4
    @Froot
    LAMP > every other crap.
    Apache configs are easy, I dont get why people think that is it hard.

    Also, running node on port 80 and 443, good luck.
  • 1
    Back when I had a LAMP stack, I chownd the /var/www/ directory to my user
  • 0
    @Linux What's the problem with running node on port 80 and 443?

    And lamp is defenately not better than everything else 😆 It's the A and P in LAMP that are straight from the 90s
  • 0
    @Froot
    Because you need root privileges.
  • 0
    Caddyserver is love, Caddyserver is life.
  • 0
    Thanks guys! It\'s really that easy. But I'm not developing for PHP lol. I'm just not relieved until it's working on my machine. OCD.
  • 0
    @nikolatesla
    Impossible to help without seeing the vhost.
  • 0
    @Linux Well either don't host on 80/443 or give it root privileges. I usually prefer to not host on 80/443 because I don't really want my web server to have root access. Not even Apache, scratch that, especially Apache
  • 1
    @Froot
    Apache does not have root access lol.
    Sorry to say that, but you are doing it wrong in this case.
  • 0
    @Linux Hmm ok. Good to know. But how does it get to use port 80 then? I'm just curious at this point
  • 0
    @Froot
    I use apache2 as a ReverseProxy. Then you can easily set up SSL too.
    You will not notice any performance difference, because Apache does not serve any content itself, just proxies shit. So you will still keep the node performance.
  • 1
    @Linux Well. Yeah 😄
    I thought you were taking about having Apache serve PHP like in the good old 90s. I have no problem with Apache as a reverse proxy tho I would rather use nginx.

    Tho I'm still curious how a program can get access to port 80 without root privileges
  • 0
    @Froot
    Thats how you do it m8 :)
  • 1
    @Linux I still don't get it but I'll go Google a bit and educate myself 😄

    Anyhow, as long as there's no PHP being served directly from Apache or preferably no PHP at all, I'm fine with it 😆
  • 0
    @Froot
    I never use Apache with libphp. Only fpm ;)
Add Comment