Go to file
2019-04-26 21:38:26 +08:00
.circleci Try fixing CI 2019-04-07 10:23:53 +08:00
.github Update issue template 2019-04-10 12:58:39 +08:00
app Make sure tid_cape set 2019-04-26 21:38:26 +08:00
bootstrap Apply fixes from StyleCI (#11) 2019-03-02 22:58:37 +08:00
config Support OAuth2 2019-04-25 23:24:24 +08:00
database Support OAuth2 2019-04-25 23:24:24 +08:00
plugins Add an empty "plugins" directory 2018-06-28 13:31:43 +08:00
public Fix entry for IIS 2019-03-14 12:30:57 +08:00
resources Support OAuth2 2019-04-25 23:24:24 +08:00
routes Support OAuth2 2019-04-25 23:24:24 +08:00
scripts Add script for bumping version 2019-04-20 16:02:05 +08:00
storage Simplify downloading packages 2019-04-05 17:23:27 +08:00
tests Return empty string when JWT auth failed 2019-04-26 18:58:12 +08:00
.editorconfig Reformat Stylus 2019-03-17 11:19:07 +08:00
.env.example Add missing env item 2019-04-25 14:13:21 +08:00
.env.testing Support JWT authentication 2019-04-23 10:05:58 +08:00
.eslintignore Update outdated .eslintignore 2018-09-29 20:59:42 +08:00
.gitignore Support OAuth2 2019-04-25 23:24:24 +08:00
.travis.yml Add script for bumping version 2019-04-20 16:02:05 +08:00
artisan remove constant BASE_DIR 2016-11-21 21:50:24 +08:00
babel.config.js Remove "toastr" and "sweetalert2" 2019-03-25 22:01:57 +08:00
composer.json Support OAuth2 2019-04-25 23:24:24 +08:00
composer.lock Support OAuth2 2019-04-25 23:24:24 +08:00
LICENSE Relicense to MIT 2019-03-30 13:20:46 +08:00
package.json Bump version to 4.0.4 2019-04-20 16:05:12 +08:00
phpunit.xml ignore coverage of artisan commands 2019-02-28 19:14:11 +08:00
postcss.config.js Fix linting errors 2019-03-15 16:50:16 +08:00
README_EN.md Update readme [skip ci] 2019-04-22 19:29:54 +08:00
README.md Update readme [skip ci] 2019-04-22 19:29:54 +08:00
server.php Apply fixes from StyleCI (#16) 2019-03-12 17:21:29 +08:00
tsconfig.json Normalize JSON response structure 2019-04-23 11:47:45 +08:00
webpack.config.js Defer checking updates 2019-04-08 14:42:40 +08:00
yarn.lock Add script for bumping version 2019-04-20 16:02:05 +08:00

Circle CI Status Codecov Latest Stable Version PHP 7.1.8+ License

Are you puzzled by losing your custom skins in Minecraft servers runing in offline mode? Now you can easily get them back with the help of Blessing Skin!

Blessing Skin is a web application where you can upload, manage and share your custom skins & capes! Unlike modifying a resource pack, everyone in the game will see the different skins of each other (of course they should register at the same website too).

Blessing Skin is an open-source project written in PHP, which means you can deploy it freely on your own web server!

Features

  • A fully functional skin hosting service
  • Multiple player names can be owned by one user on the website
  • Share your skins and capes online with skin library!
  • Easy-to-use
    • Visual page for user/player/texture management
    • Detailed option pages
    • Many tweaks for a better UI/UX
  • Security
    • Support many secure password hash algorithms
    • Email verification for registration
    • Score system for preventing evil requests
  • Incredibly extensible
    • Plenty of plugins available
    • Integration with Authme/CrazyLogin/Discuz (available as plugin)
    • Support custom Yggdrasil API authentication (available as plugin)

Requirements

Blessing Skin has only a few system requirements. In most cases, these PHP extensions are already enabled.

  • Web server with URL rewriting enabled
  • PHP >= 7.1.8 (use v2.x branch if your server doesn't meet the requirements)
  • OpenSSL PHP Extension
  • PDO PHP Extension
  • Mbstring PHP Extension
  • Tokenizer PHP Extension
  • GD PHP Extension
  • XML PHP Extension
  • Ctype PHP Extension
  • JSON PHP Extension
  • fileinfo PHP Extension

Quick Install

  1. Download our latest release, extract to where you like to installed on.
  2. Rename .env.example to .env and configure your database information. (For windows users, just rename it to .env., and the last dot will be removed automatically)
  3. For Nginx users, add rewrite rules to your Nginx configuration
  4. Navigate to http://your-domain.com/setup in your browser. If 404 is returned, please check whether the rewrite rules works correctly.
  5. Follow the setup wizard and your website is ready-to-go.

Plugin System

Blessing Skin provides an elegant and powerful plugin system, and you can attach plenty of functions and customization to your site via installing plugins.

For more information, please refer to Wiki - Introducing plugin system.

Supporting Blessing Skin

Welcome to sponsoring Blessing Skin if this software is useful for you!

Currently you can sponsor us via 爱发电.

Sponsors


dz_paji

Backers


pppwaw

Little_Qiu

麻花

Mangocraft

Developer Install

If you'd like make some contribution on the project, please deploy it from GitHub first.

You'd better have some experience on shell operations to continue.

Please make sure you have installed the tools below:

Clone the code from GitHub and install dependencies:

git clone https://github.com/bs-community/blessing-skin-server.git
cd blessing-skin-server
composer install
yarn

Build the things!

yarn build

Congrats! You made it. Next, please refer to No.2 of Quick Install section.

Configure the Web Server

For Apache (most of the virtual hosts) and IIS users, there is already a pre-configured file for you. What you need is just to enjoy!

For Nginx users, please add the following rules to your Nginx configuration file:

location / {
    try_files $uri $uri/ /index.php?$query_string;
}

location ~ /\.env {
    deny all;
}

Mod Configuration

Please refer to Wiki - Mod Configuration.

screenshot

Internationalization

Blessing Skin supports multiple languages, while currently supporting English (en) and Simplified Chinese (zh_CN).

Of course, you can add your own language. Please check Wiki - Add other language [i18n] (Simplified Chinese only).

If you are willing to contribute your translation, welcome to join our Crowdin project.

Report Bugs

Read Wiki - FAQ and double check if your situation doesn't suit any case mentioned there before reporting.

When reporting a problem, please attach your log file (located at storage/logs/laravel.log) and the information of your server where the error occured on. You should also read this guide before reporting a problem.

MIT License

Copyright (c) 2016-present The Blessing Skin Community