Go to file
2019-02-17 22:49:02 +08:00
.github Update links 2018-11-25 15:12:53 +08:00
app fix tests 2019-02-17 20:12:42 +08:00
bootstrap Move entrypoint to "public" dir 2018-10-19 21:32:15 +08:00
config fix 2019-02-16 21:24:28 +08:00
database Fix update script 2018-08-22 10:21:05 +08:00
plugins Add an empty "plugins" directory 2018-06-28 13:31:43 +08:00
public Move .htaccess 2018-10-20 10:41:40 +00:00
resources Fix favicon 2018-10-19 22:23:47 +08:00
routes Restrict PluginController access to super admin only 2018-08-21 09:05:29 +08:00
scripts add build artifacts 2019-02-17 21:39:06 +08:00
storage Add certificate and user agent config for http requests 2018-08-17 22:55:59 +08:00
tests fix test finally () 2019-02-17 21:23:07 +08:00
.browserslistrc Update Babel config 2018-09-24 10:36:08 +08:00
.editorconfig Get ready for using Vue.js 2018-07-25 15:32:08 +08:00
.env.example Update .env files 2018-07-20 15:14:10 +08:00
.env.testing Update .env files 2018-07-20 15:14:10 +08:00
.eslintignore Update outdated .eslintignore 2018-09-29 20:59:42 +08:00
.eslintrc.yml Reduce global variables pollution 2018-09-09 09:28:05 +08:00
.gitignore update .gitignore 2019-02-17 08:44:47 +08:00
artisan remove constant BASE_DIR 2016-11-21 21:50:24 +08:00
azure-pipelines.yml allow fails when download cached deps 2019-02-17 22:49:02 +08:00
babel.config.js Update Babel config 2018-09-24 10:36:08 +08:00
composer.json Upgrade to Laravel 5.7 2018-09-06 16:26:03 +08:00
composer.lock update php deps 2019-02-16 21:12:06 +08:00
LICENSE change the License to GPL v3 2016-07-23 17:54:52 +08:00
package.json update junit output 2019-02-16 17:47:33 +08:00
phpunit.xml Ignore cipher-related files 2018-07-22 11:33:09 +08:00
postcss.config.js Use PostCSS 2018-07-30 09:45:01 +08:00
README_EN.md Update links 2018-11-25 15:12:53 +08:00
README.md Update links 2018-11-25 15:12:53 +08:00
web.config Update URI processing of web servers 2018-08-16 18:01:16 +08:00
webpack.config.js Modify path of front-end resources 2018-10-19 21:42:14 +08:00
yarn.lock output test result in ci 2019-02-16 17:31:21 +08:00
zip.txt fix generating artifacts 2019-02-17 22:14:22 +08:00

Travis Building Status Codecov Latest Stable Version PHP 7.1.3+ License Twitter Follow

NOTE: The code of the current branch is of Blessing Skin v4.

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! Here is a live demo.

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 (available as plugin)
    • Score system for preventing evil requests
  • Incredibly extensible
    • Plenty of plugins available
    • Integration with Authme/CrazyLogin/Discuz
    • Support custom Yggdrasil API authentication

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.3 (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.

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

Report Problems

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.

Copyright 2016-2018 printempw and contributors.

Blessing Skin is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License version 3.

Exception: Any plugin developed for Blessing Skin, is not required to adopt GPLv3 License nor release its source code, provided no source code from Blessing Skin is contained in the plugin.