Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Discussion] Website Server Software #1

Open
amnotbananaama opened this issue Sep 30, 2021 · 0 comments
Open

[Discussion] Website Server Software #1

amnotbananaama opened this issue Sep 30, 2021 · 0 comments

Comments

@amnotbananaama
Copy link
Owner

Currently, the HarmoniaCraft website runs as a Node.js program. This was done to capitalize on two big advantages, namely:

  • Allowing me to program the website quickly. Javascript is currently the only language I am proficient in, so I couldn't have done this another way.
  • Portability and ease of making changes to the server. The current codebase is under 90 lines, and that number includes comments and other nonessential features.

However, I am no longer the only person working on the website. Additionally, it's important to plan for the future, and make sure the website can handle larger traffic if necessary. With that in mind, here are the options I can think of:

Option 1: Stick with Node.js

This is obviously the path of least resistance. However it is not future proof, and may not mesh well with other ideas or contributors.

Option 2: Switch to Python

This has the advantage of being a language you are more familiar with, which is important especially since you will be a huge help thank you!!

However, I don't know Python at all, and I've struggled to learn. I tried to write a simple web server mimicking index.js and failed miserably. I couldn't figure out how to make a page, eg. /donate point to the donate.html file.

Option 3: Switch to another language

There are many, many more programming languages commonly used by web servers. Php, Go, Java, C++, Ruby, etc are just a few of the most popular.

However, this would make the repository/build process a lot more complicated.

Option 4: Switch to a standalone application

There are plenty of standalone web server applications. These include Apache, NGNIX, Lighttpd and others.

The only downside to these is that they are big and complicated and scary

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant