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

"Syerjchep.org" is the name of this website. The name is from the group, mostly from the clans sections of these forums. The word has been around for a while, and well, I just decided to call the website that. Anyway, it is a website which I intended to contain many Blockland related features and services. Currently it has:

  • A place to upload saves, they will be added to a list, and the server will automatically take the brickcount, and description from the file, and display it along with who uploaded it, and when they did. I also plan to attempt to make a program which can automatically take a save and generate an image of it, much like the main blockland server list website.

  • A brick add-on maker, which can make bricks, even print bricks or bricks that are water. You just go to the website, choose the settings of the brick you want, and submit, and the server generates the download for you right there.

  • A rating blocklanders site, where you can 'rate' other accounts, and they can rate you.

  • Cross server chat, though a secondary server I will host, that allows cross server chat, though an add-on, without port forwarding.

  • Server info images like Zack0Wack0's except a server addon will be required to transmit more data than just what's on the master server.

  • Links, that with the use of a client add-on, will change to let people join what server you're in from out of game.

  • Online handled version of image to brick software.

Green = Done.
Yellow = More to add later.
Red = Not started.

Link:
http://syerjchep.org

And yes I realize it's really bland.
I'm just testing core features here, not worried about formatting yet.

Note: The hosting is still being stabalized, and the webserver (that I made myself) is being improved. Both these should increase uptime and speed. If the server is down or if you've forgetting your password, just reply to this thread or pm me.
« Last Edit: May 18, 2011, 09:55:26 PM by DrenDran »

Awesome, thank you.

Awesome, thank you.
So far I've gotten a good handful of requests.
Did you try to make a brick?
Did it work?

So far I've gotten a good handful of requests.
Did you try to make a brick?
Did it work?

Gonna try, I hope it gonna work..

EDIT: It work perfectly! Very nice! Thanks you again!!
« Last Edit: April 22, 2011, 12:39:30 PM by MrLoL »

Gonna try, I hope it gonna work..
Someone just made a 3x5x6 brick?
Was that you?
Did it work alright?

Now we need a print maker.

Now we need a print maker.
Quote from: website
Print brick making still needs to be ported to the website.
In other words, I made a print brick maker, and it worked.
But I need to finish transferring the code.

Good luck.
Ever need me just hit me up.

This is a little neat site.
I love the print thing only thing is which side is which it'd be cool if you could make it generate a picture.

Like where it's going.

The webserver is about to be updated to handle the creation of print bricks, and to log page requests, and to transfer images.

EDIT: Update complete, print bricks work now, http://syerjchep.org/syjsandhelp.png transfers alright, and the main page has a link to a page request log.
« Last Edit: April 22, 2011, 05:00:37 PM by DrenDran »

Why do you want to reinvent the wheel, instead of using a tested (and probably more bug-free) server like Apache or nginx?

Why do you want to reinvent the wheel, instead of using a tested (and probably more bug-free) server like Apache or nginx?
I know C++ very, very well, but I havn't done anything major with PHP for years.
Not to mention things like creating a zip file based on input are a hell of a lot easier in C++ from what I've seen.
Also, this will allow me to sync. up stuff with a blockland server if I host one later on.
That, and the server will also need to be a server on another port for the cross server chat I hope to implement.

EDIT: asdf the server closed/crashed, I put it right back up again, but it makes be worry that I have more work to do
« Last Edit: April 22, 2011, 05:17:07 PM by DrenDran »

I know C++ very, very well, but I havn't done anything major with PHP for years.
Not to mention things like creating a zip file based on input are a hell of a lot easier in C++ from what I've seen.
Also, this will allow me to sync. up stuff with a blockland server if I host one later on.
That, and the server will also need to be a server on another port for the cross server chat I hope to implement.
You should generally have the chat server in another process for performance reasons.
Also, you could still make the server-sided stuff in C++ by writing it as a module (or by using FastCGI) for the web server of your choice.
This gives you the cache, compression, etc of the web server but you could still make the rest in the language of your choice (C++).
Oh, and you *COULD* use regular CGI, but that is crap. Period.
Also, it's not a good idea to mix the webserver and the scripts in the same codebase, since if you make one runtime error in a page, the whole webserver application will probably go down, requiring a manual restart. Yes, I know you *COULD* work around that, but getting decent error handling, etc is probably gonna take more work than integrating it into the ecosystem of an existing web server.

Or, better yet, learn Django.
« Last Edit: April 22, 2011, 05:28:08 PM by DontCare4Free »

You should generally have the chat server in another process for performance reasons.
Also, you could still make the server-sided stuff in C++ by writing it as a module (or by using FastCGI) for the web server of your choice.
This gives you the cache, compression, etc of the web server but you could still make the rest in the language of your choice (C++).
Oh, and you *COULD* use regular CGI, but that is crap. Period.
Also, it's not a good idea to mix the webserver and the scripts in the same codebase, since if you make one runtime error in a page, the whole webserver application will probably go down, requiring a manual restart. Yes, I know you *COULD* work around that, but getting decent error handling, etc is probably gonna take more work than integrating it into the ecosystem of an existing web server.

Or, better yet, learn Django.
True, but I've already made the webserver.
And it worked fine up and till the last update.
Now I need to find out what's causing the crashes.