Foundation
My software foundation.
This repo will include all my public software, scripts, configs and CI system.
What is this repo?
My github repo aggregation.
I've manage too many repositories, that I have to combine them to one so that I can manage them easily.
Repos
-
GeoIP2 server
PAC (Proxy Auto-Config) file server.
A caddy module that build static site into caddy server.
-
My docker images
- baidupcs-go Baidu Cloud Disk conmandline tools. Repo Link
- code-server VS Code Server edition, download and change to use zsh, base on ubuntu. Repo Link
- dell-openmanage Dell openmanage package. Use to automate manage server through iDrac base on centos 7. Repo Link
- dell-poweredge Dell openmanage package. Use to automate manage server through iDrac base on ubuntu, not work yet. Repo Link
- editor-server My cloud editor, base on my code-server, add a lot of usefull support. Repo Link
- go-ethereum Golang implementation of the Ethereum. Repo Link
- log-forwarder Forward log to couchdb. Repo Link
- meshcentral MeshCentral controll computers anywhere. Repo Link
- openwrt OpenWRT, Create OpenWRT image, can not run on github actions, because action space is not enough. Repo Link
- zerotier-ui Zerotier One management ui. Repo Link
-
- chat Rust Chat client use http comet technique.
-
- mirror Mirror, phone app, a magic mirror.
Use sementic release
If a dir is develop by me, can use @gsmlg/semantic-release-action, like so:
- name: 🚀 Release
uses: gsmlg/semantic-release-action@v3
with:
release_name: <Release name>
working-directory: <Project directory>
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
and also need to add a .release.yaml
file in directory like so:
extends: "semantic-release-monorepo"
repositoryUrl: https://github.com/gsmlg-dev/Foundation.git
plugins:
- '@semantic-release/commit-analyzer'
- '@semantic-release/release-notes-generator'
- '@semantic-release/github'
- - "@semantic-release/exec"
- "prepareCmd" : "echo ${nextRelease.version}"
"publishCmd" : "echo pubhlish <name> ${nextRelease.version}"
branches:
- +([0-9])?(.{+([0-9]),x}).x
- main
- next
- next-major
- {name: 'beta', prerelease: true}
- {name: 'alpha', prerelease: true}
Commit Message Type
Must be one of the following:
- feat: A new feature
- fix: A bug fix
- docs: Documentation only changes
- style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
- refactor: A code change that neither fixes a bug nor adds a feature
- perf: A code change that improves performance
- test: Adding missing or correcting existing tests
- chore: Changes to the build process or auxiliary tools and libraries such as documentation generation