Go to file
2019-09-12 19:06:18 +08:00
.circleci Increase PHP version requirement 2019-08-09 22:56:54 +08:00
.github Fix YAML indentation 2019-09-11 23:34:42 +08:00
app Clean up .env files 2019-09-12 19:06:18 +08:00
bootstrap Update policy of checking environment 2019-09-10 21:10:27 +08:00
config Add GitHub Actions (#97) 2019-09-11 23:32:56 +08:00
database Add update script 2019-09-07 10:37:30 +08:00
plugins Add an empty "plugins" directory 2018-06-28 13:31:43 +08:00
public Update policy of checking environment 2019-09-10 21:10:27 +08:00
resources Tweak l10n 2019-09-08 19:39:26 +08:00
routes Add support of customizing UI text 2019-09-08 18:57:19 +08:00
scripts Use another JSON file for publishing preview 2019-09-12 18:55:18 +08:00
storage Switch to another translations loader 2019-09-06 18:52:34 +08:00
tests Clean up .env files 2019-09-12 19:06:18 +08:00
.editorconfig Update release script 2019-08-01 14:38:26 +08:00
.env.example Clean up .env files 2019-09-12 19:06:18 +08:00
.env.testing Clean up .env files 2019-09-12 19:06:18 +08:00
.eslintignore Fix linting errors 2019-07-12 22:41:44 +08:00
.gitignore Refactor setup 2019-09-06 23:53:47 +08:00
artisan
azure-pipelines.yml Tweak CI trigger 2019-08-09 16:29:00 +08:00
babel.config.js Remove "toastr" and "sweetalert2" 2019-03-25 22:01:57 +08:00
composer.json Upgrade dependencies 2019-09-12 18:55:44 +08:00
composer.lock Upgrade dependencies 2019-09-12 18:55:44 +08:00
LICENSE Relicense to MIT 2019-03-30 13:20:46 +08:00
package.json Load front-end i18n text at back-end 2019-09-07 17:18:58 +08:00
phpunit.xml Add tests for artisan commands 2019-08-09 15:36:13 +08:00
postcss.config.js Fix linting errors 2019-03-15 16:50:16 +08:00
README_EN.md Decrease PHP version requirement to 7.2.0 2019-08-28 17:36:20 +08:00
README.md Decrease PHP version requirement to 7.2.0 2019-08-28 17:36:20 +08:00
server.php Apply fixes from StyleCI (#16) 2019-03-12 17:21:29 +08:00
tsconfig.json Make some scripts cross-platform 2019-05-07 17:04:45 +08:00
webpack.config.js Load front-end i18n text at back-end 2019-09-07 17:18:58 +08:00
yarn.lock Load front-end i18n text at back-end 2019-09-07 17:18:58 +08:00

Circle CI Status Codecov Latest Stable Version PHP 7.2.0+ 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 (Nginx or Apache)
  • PHP >= 7.2.0 (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
  • zip 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.

Supporting Blessing Skin

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

Currently you can sponsor us via 爱发电.

Sponsors


hyx5020

dz_paji

ExDragine

Akkariin

星域联盟_晓夜

Backers


爱发电用户_4ft3

pppwaw

Little_Qiu

麻花

Mangocraft

Andy_Chuck

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) 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 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 Add other language [i18n] (Simplified Chinese only).

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

Report Bugs

Read 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