Skip to content

gsmlg-dev/Foundation

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 

Repository files navigation

Foundation

semantic-release commits last commit tags license

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

  • golang

    PAC (Proxy Auto-Config) file server.

    Download:

      https://github.com/gsmlg-dev/Foundation/releases/download/pac-server-release/pac-server_linux_amd64
      https://github.com/gsmlg-dev/Foundation/releases/download/pac-server-release/pac-server_linux_arm64
      https://github.com/gsmlg-dev/Foundation/releases/download/pac-server-release/pac-server_darwin_amd64
      https://github.com/gsmlg-dev/Foundation/releases/download/pac-server-release/pac-server_darwin_arm64
      https://github.com/gsmlg-dev/Foundation/releases/download/pac-server-release/pac-server_windows_amd64
      https://github.com/gsmlg-dev/Foundation/releases/download/pac-server-release/pac-server_windows_arm64
      https://github.com/gsmlg-dev/Foundation/releases/download/pac-server-release/pac-server_freebsd_amd64
      https://github.com/gsmlg-dev/Foundation/releases/download/pac-server-release/pac-server_android_arm64
    

    Docker:

      docker.io/gsmlg/pac-server:latest
      ghcr.io/gsmlg/pac-server:latest
    

    A caddy module that build static site into caddy server.

  • docker

    My docker images

    Docker Pulls Build

    Docker Pulls Build

    • caddy Caddy reverse proxy server, multi architecture at github release. Repo Link

    Docker Pulls Build

    Docker Pulls Build

    Docker Pulls Build

    Docker Pulls Build

    Docker Pulls Build

    Docker Pulls Build

    • dell-poweredge Dell openmanage package. Use to automate manage server through iDrac base on ubuntu, not work yet. Repo Link

    Build

    Docker Pulls Build

    Docker Pulls Build

    Docker Pulls Build

    Docker Pulls Build

    Docker Pulls Build

    Docker Pulls Build

    Docker Pulls Build

    Docker Pulls Build

    Docker Pulls Build

    Docker Pulls Build

    Docker Pulls Build

    • openwrt OpenWRT, Create OpenWRT image, can not run on github actions, because action space is not enough. Repo Link

    Docker Pulls Build

    Docker Pulls Build

    Docker Pulls Build

    Docker Pulls Build

    • python My semantic-release docker image, with kanico image builder, and plugins: gitlab, git and monorepo. Repo Link

    Docker Pulls Build

    Docker Pulls Build

    Docker Pulls Build

    Docker Pulls Build

    Docker Pulls Build

    Docker Pulls Build

    Docker Pulls Build

    Docker Pulls Build

    Docker Pulls Build

    Docker Pulls Build

  • rust

    • chat Rust Chat client use http comet technique.

    Build

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