Author Topic: Syerjchep --- img2brick soon --- quick rate --- tracking --- more stuff!  (Read 21076 times)

Anyway, I've implemented zack0's style to the homepage.
Thing is, I had to make a handful of changes to let it work okay with the stuffty server, and even now, every time I reload it, there will always be about two images missing.
It's kind of annoying, so I guess I'm at the point where I'm going to implement some sort of extenuating security mode where I log everything the server does for me.

That lighter green is too light for white text
I take that back. I was on a CRT, could hardly even see the text.

Looks fine on my laptop's screen.

Anyway, I've implemented zack0's style to the homepage.
Thing is, I had to make a handful of changes to let it work okay with the stuffty server, and even now, every time I reload it, there will always be about two images missing.
It's kind of annoying, so I guess I'm at the point where I'm going to implement some sort of extenuating security mode where I log everything the server does for me.
How about putting it behind a reverse nginx proxy?
That way nginx can cache the "cacheable" files, and nginx can serve the static files for you.

snip

That is so very inapplicable when it comes to web design. By that logic, all websites should be entirely modifiyable for anyone. Oh wait. That's a terrible idea.

You must really have been high or something to not think that one out. I mean, you DO realize that an opinion from a couple hundred years ago may not really apply to a technology that was invented long after the death of the speaker?

EDIT: Server must be down or I can't reach it or something...

That is so very inapplicable when it comes to web design. By that logic, all websites should be entirely modifiyable for anyone. Oh wait. That's a terrible idea.
No, I didn't say that. It doesn't fit on "corporate" websites, etc, but this is clearly a community/utility website. It would fit pretty well on a community website.
You must really have been high or something to not think that one out. I mean, you DO realize that an opinion from a couple hundred years ago may not really apply to a technology that was invented long after the death of the speaker?
That is completely irrelevant.

How about putting it behind a reverse nginx proxy?
That way nginx can cache the "cacheable" files, and nginx can serve the static files for you.
Eh, seems to complicated.
Anyway, I've decided to stop the process of closing sockets due to inactivity, hoping, that since all the crashes happen after a socket is closed for inactivity, this will just stop crashes.

Eh, seems to complicated.
Anyway, I've decided to stop the process of closing sockets due to inactivity, hoping, that since all the crashes happen after a socket is closed for inactivity, this will just stop crashes.
Complicated‽‽
But since you are so lazy, here we go:
Code: (nginx.conf) [Select]
http {
    server {
        location / {
            proxy_pass             http://localhost:8080;
            proxy_set_header       Host $host;
        }
    }
}
Was that so hard?

Complicated‽‽
But since you are so lazy, here we go:
Code: (nginx.conf) [Select]
http {
    server {
        location / {
            proxy_pass             http://localhost:8080;
            proxy_set_header       Host $host;
        }
    }
}
Was that so hard?
Setting up, basically a second webserver, would be more than just coping a few lines of text.

Setting up, basically a second webserver, would be more than just coping a few lines of text.
Provided that you run debian or a derivative of it (Ubuntu, etc) it should be as simple as running this in the console:
Code: [Select]
sudo apt-get install nginxIf you use RedHat/Fedora/etc you run this as root:
Code: [Select]
yum install nginxIf you use Windows then you download a zip file and extract it.
If you use Mac OS X then you install another operating system as it is crap anyway.

Anyway, I've implemented zack0's style to the homepage.
Did you read readme.txt? I had instructions for the comment page and the other pages too.

Did you read readme.txt? I had instructions for the comment page and the other pages too.
Anyway, you should really use a templating system.

ITT: People who don't know anything about webservers. The further this thread goes, the more I cringe ...

That is so very inapplicable when it comes to web design. By that logic, all websites should be entirely modifiyable for anyone. Oh wait. That's a terrible idea.

You must really have been high or something to not think that one out. I mean, you DO realize that an opinion from a couple hundred years ago may not really apply to a technology that was invented long after the death of the speaker?

EDIT: Server must be down or I can't reach it or something...
You quoted the wrong thing.

Did you read readme.txt? I had instructions for the comment page and the other pages too.
That's coming soon.
ITT: People who don't know anything about webservers. The further this thread goes, the more I cringe ...
I just have to ask, are you referring to me too?
Because not only did I make a webserver which works, I also know the technicals of all its problems, and plan to eventually fix them all.