Compare commits

...

5 Commits

Author SHA1 Message Date
8d33f2bae3 NO-ISSUE Merged from release/0.1 (#52)
All checks were successful
Frontend CI / build (push) Successful in 1m29s
Reviewed-on: #52
2025-02-01 13:34:52 +08:00
0e022012fe Merge branch 'main' of git.squidspirit.com:squid/blog into release/0.1
All checks were successful
PR Title Check / pr-title-check (pull_request) Successful in 13s
Frontend CI / build (push) Successful in 1m25s
2025-02-01 13:32:08 +08:00
c5b1f0703e BLOG-53 Update license and readme (#54)
All checks were successful
Frontend CI / build (push) Successful in 1m27s
### Description

Update license so that anyone should remove my personal information before deployment.

### Package Changes

_No response_

### Screenshots

_No response_

### Reference

Resolves #53

### Checklist

- [x] A milestone is set
- [x] The related issuse has been linked to this branch

Reviewed-on: #54
Reviewed-by: zoe <zoe@noreply.localhost>
Co-authored-by: SquidSpirit <squid@squidspirit.com>
Co-committed-by: SquidSpirit <squid@squidspirit.com>
2025-02-01 13:29:19 +08:00
93f1bee0ae NO-ISSUE Upgrade version to 0.1.1 (#42)
All checks were successful
Frontend CI / build (push) Successful in 1m26s
Deployment / frontend-deployment (release) Successful in 2m3s
PR Title Check / pr-title-check (pull_request) Successful in 13s
### Description

As the title.

### Package Changes

_No response_

### Screenshots

_No response_

### Reference

_No issue_

### Checklist

- [x] A milestone is set
- [ ] The related issuse has been linked to this branch

Reviewed-on: #42
Reviewed-by: zoe <zoe@noreply.localhost>
Co-authored-by: SquidSpirit <squid@squidspirit.com>
Co-committed-by: SquidSpirit <squid@squidspirit.com>
2025-01-28 13:30:27 +08:00
f8cf40a3dc BLOG-36 Fix workflow buildx failed to push (#38)
All checks were successful
Frontend CI / build (push) Successful in 1m34s
### Description

- As the title.

### Package Changes

_No response_

### Screenshots

_No response_

### Reference

- Resolves #36
- Solution: https://stackoverflow.com/questions/75131872/error-failed-to-solve-failed-commit-on-ref-unexpected-status-400-bad-reques
- Docker document: https://docs.docker.com/build/ci/github-actions/attestations/#max-level-provenance
  > Note that adding attestations to an image means you must push the image to a registry directly, as opposed to loading the image to the local image store of the runner. This is because the local image store doesn't support loading images with attestations.

### Checklist

- [x] A milestone is set
- [x] The related issuse has been linked to this branch

Reviewed-on: #38
Reviewed-by: zoe <zoe@noreply.localhost>
Co-authored-by: SquidSpirit <squid@squidspirit.com>
Co-committed-by: SquidSpirit <squid@squidspirit.com>
2025-01-28 13:23:46 +08:00
5 changed files with 16 additions and 21 deletions

View File

@ -17,7 +17,7 @@ jobs:
- name: Set up Docker Buildx - name: Set up Docker Buildx
uses: docker/setup-buildx-action@v3 uses: docker/setup-buildx-action@v3
- name: Build image and push to registry - name: Login to registry
uses: docker/login-action@v3 uses: docker/login-action@v3
with: with:
registry: ${{ vars.REGISTRY }} registry: ${{ vars.REGISTRY }}
@ -28,6 +28,7 @@ jobs:
uses: docker/build-push-action@v6 uses: docker/build-push-action@v6
with: with:
push: true push: true
provenance: false
context: ./frontend context: ./frontend
tags: | tags: |
${{ vars.REGISTRY }}/${{ vars.IMAGE_REPO_FRONTEND }}:latest ${{ vars.REGISTRY }}/${{ vars.IMAGE_REPO_FRONTEND }}:latest

19
LICENSE
View File

@ -1,19 +0,0 @@
Copyright (c) 2025 SquidSpirit
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR
OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE
OR OTHER DEALINGS IN THE SOFTWARE.

9
LICENSE.md Normal file
View File

@ -0,0 +1,9 @@
# Copyright (c) 2025 SquidSpirit
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
Notwithstanding the above, modification and deployment of the Software are explicitly permitted, provided that all instances of "SquidSpirit", the original website URL (if applicable), and any other identifying information related to the original author are replaced with the user's own information. The modified Software may then be deployed without the requirement to attribute the original author (SquidSpirit). However, the modified Software must still retain this MIT License, including this clause.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

View File

@ -10,3 +10,7 @@ Despite Next.js being a full-stack framework, I still decided to adopt a separat
As for the more detailed development approach, I plan to use Clean Architecture for the overall structure and ATDD for testing. Of course, such a small project may not necessarily require such complex design patterns, but I want to give myself an opportunity to practice them. As for the more detailed development approach, I plan to use Clean Architecture for the overall structure and ATDD for testing. Of course, such a small project may not necessarily require such complex design patterns, but I want to give myself an opportunity to practice them.
These will allow me to become more proficient in these modern development practices and leave a lot of flexibility and room for adjustments in the future. These will allow me to become more proficient in these modern development practices and leave a lot of flexibility and room for adjustments in the future.
## License
This project uses a combination of the [MIT License and a custom license](./LICENSE.md). Based on the MIT License, anyone is permitted to use the code. However, before deploying the code, they must first replace any information belonging to "me" or any content that could identify "me," such as logos, names, and "about me" sections.

View File

@ -1,6 +1,6 @@
{ {
"name": "squidspirit-blog", "name": "squidspirit-blog",
"version": "0.1.0", "version": "0.1.1",
"private": true, "private": true,
"license": "MIT", "license": "MIT",
"scripts": { "scripts": {