amnotbananaama / harmoniacraft-website Goto Github PK

The Problem

Currently, the list of approved client mods is contained in the approved-mods.html page, and is rendered like this:.

/approved-mods

This approach has two major problems:

• It's difficult to work with. If I want to approve a mod, I have to add it to a very, very long list, write HTML code, etc.
• It limits who can approve mods to just me, because no one else can edit the website at the moment.

Suggestion

It would be much easier and more convenient if the page used an external list of approved mods. This could be a JSON file, an API, etc.

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

Currently donating has a lot of issues, and things we don't like:

• Paypal fees are steep :(
• Donations are too manual
  • I have to check my email, tell other staff, figure out who donated, and give them their perks.
• Donations are/can be random amounts of money
• Donation process is ugly