Introduction#
Shiro is the front-end theme of MixSpace (community edition), and the front-end theme code is open source. Some users may modify it to better suit their needs. If you want to modify it and still deploy it to your own server using Docker images rather than Docker builds, then this article is for you.
Why not...#
Docker Build#
Docker builds consume a lot of server resources, which can be challenging for cloud servers with lower configurations (less than 2G of memory), often leading to memory overload and server crashes.
Cloud Function Deployment#
You can choose to do this when your site traffic is not very high. The free quotas provided by cloud function platforms like Vercel/Netlify are sufficient for hosting your own Shiro. However, if you want to deploy it to servers in mainland China or have higher traffic demands, the quotas from cloud function platforms may not be enough.
Choice#
Here, we choose to use the official GitHub mirror repository to store our images. In China, you can use private mirror acceleration services to pull images, such as the DockerHub mirror acceleration provided by Geekery, which allows you to pull images from private repositories.
Steps#
Fork the Repository#
First, open the official repository Innei/Shiro and fork it to your own account.
Delete Some Files#
We will directly delete the .github folder in the root directory of the repository, as you do not need to use the official workflow.
Custom Modifications#
You can start modifying the code in the repository according to your needs.
Create a New Workflow#
In the .github/workflows directory of the repository, create a new yml file with any name. The code is as follows:
name: Docker Build
on:
push:
branches:
- 'main'
jobs:
build:
runs-on: ubuntu-latest
steps:
- name: Checkout
uses: actions/checkout@v3
- name: Set up Docker Buildx
uses: docker/setup-buildx-action@v3
- name: Login to Registry
uses: docker/login-action@v3
with:
registry: ghcr.io
username: ${{ github.actor }}
password: ${{ secrets.GITHUB_TOKEN }}
- name: Build and push
uses: docker/build-push-action@v4
with:
context: .
file: ./Dockerfile
platforms: linux/amd64
push: true
tags: ghcr.io/innei/shiro:latest
You only need to modify the tag in the Build and push step from ghcr.io/innei/shiro:latest to a name you find appropriate. Note that there should be no uppercase characters. To make it easier to remember, try to use your personal GitHub username in lowercase instead of innei as the image namespace.
Save the workflow file and wait for it to complete. You should be able to find the image file in the Packages section of the repository or on your personal GitHub account homepage under Package.
Usage#
Refer to the provided pull method and use the docker pull command on the server to pull the image.
This article is synchronized and updated by Mix Space to xLog. The original link is https://www.sotkg.com/posts/site/shiro-docker-deployment