J3RN/minecraft-site
Watch
1
0
Fork
You've already forked minecraft-site
 0
mirror of https://github.com/J3RN/minecraft-site synced 2026-08-31 19:10:19 +00:00
Code Issues Projects Releases Packages Wiki Activity
No description
7 commits 1 branch 0 tags 31 KiB
  • Ruby 82.9%
  • HTML 17.1%
Find a file
Exact
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Jonathan Arnett fea0b92023 Added Dotenv for dev, error display in view 
OMG! He totally added his `.env` file to the repo!

HIS SECRETS ARE BELONG TO EVERYONE

RAIN DOWN THE HACKS!

Well, no. The only thing in the `.env` file is a relative path for
testing and because I'm lazy.
2014-12-21 18:53:34 -05:00
views Added Dotenv for dev, error display in view 2014-12-21 18:53:34 -05:00
.env Added Dotenv for dev, error display in view 2014-12-21 18:53:34 -05:00
.gitignore Ignored some directories, unicorn config++ 2014-12-20 23:40:47 +00:00
config.ru Added Dotenv for dev, error display in view 2014-12-21 18:53:34 -05:00
Gemfile Added Dotenv for dev, error display in view 2014-12-21 18:53:34 -05:00
Gemfile.lock Added Dotenv for dev, error display in view 2014-12-21 18:53:34 -05:00
README.md Added README 2014-12-20 14:41:27 -05:00
server.rb Added Dotenv for dev, error display in view 2014-12-21 18:53:34 -05:00
unicorn.rb Ignored some directories, unicorn config++ 2014-12-20 23:40:47 +00:00

README.md

Minecraft Site

This site showcases the stats for the players on a Minecraft server, and maybe someday more!

Current functionality

Current, the site simply displays:

  • Number of deaths
  • Number of deaths to hostile mobs for each mob (e.g. "Times killed by Skeleton")
  • Number of kills of hostile mobs for each mob (e.g. "Skeletons killed")

Setup

Unfinished: I still need to look into how to properly deploy Sinatra apps

All you need to do is set an environment variable to point to the Minecraft stats directory:

export STATS_PATH=/home/j3rn/minecraft/world/stats

Contributing

Contributions are welcome! Simply follow the guide below.

  1. Fork the repository
  2. Create a topic branch
  3. Commit your changes to the topic branch
  4. Open a pull-request from your topic branch to the master branch