init Gitea
Build and Push ApacheOIDC Docker Image / build (push) Successful in 1m1s

This commit is contained in:
boxi committed 2026-06-28 20:24:01 +02:00
1 parent 0c7a4a71cc
commit 2facb67517
4 files changed
+53 -56

No files matched your search

+52
View File
@@ -0,0 +1,52 @@
name: Build and Push ApacheOIDC Docker Image
on:
push:
branches: [ main ]
jobs:
build:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Login to Registry
uses: docker/login-action@v2
with:
registry: gitea.tail276105.ts.net
username: ${{ secrets.REGISTRY_USER }}
password: ${{ secrets.REGISTRY_PASSWORD }}
- name: Docker imageTags
run: |
REPOSITORY_LC=$(echo "${{ gitea.repository }}" | tr '[:upper:]' '[:lower:]')
echo "versioned: gitea.tail276105.ts.net/${REPOSITORY_LC}:${GITHUB_RUN_NUMBER}"
echo "latest: gitea.tail276105.ts.net/${REPOSITORY_LC}:latest"
- name: Build Docker Image
run: |
REPOSITORY_LC=$(echo "${{ gitea.repository }}" | tr '[:upper:]' '[:lower:]')
# Build the image with the commit hash tag
export DOCKER_CLI_EXPERIMENTAL=enabled;
docker buildx create --name boxitapache || true 2>/dev/null;
docker buildx use boxitapache;
docker buildx build \
--platform linux/arm64,linux/amd64 \
--tag gitea.tail276105.ts.net/${REPOSITORY_LC}:${GITHUB_RUN_NUMBER} \
--load \
.;
# Tag the same image as "latest"
docker tag gitea.tail276105.ts.net/${REPOSITORY_LC}:${GITHUB_RUN_NUMBER} gitea.tail276105.ts.net/${REPOSITORY_LC}:latest
- name: Push Docker Images
run: |
REPOSITORY_LC=$(echo "${{ gitea.repository }}" | tr '[:upper:]' '[:lower:]')
docker push gitea.tail276105.ts.net/${REPOSITORY_LC}:${GITHUB_RUN_NUMBER}
docker push gitea.tail276105.ts.net/${REPOSITORY_LC}:latest
- name: Log out from registry
if: always()
run: docker logout gitea.tail276105.ts.net
-25
View File
@@ -1,25 +0,0 @@
# Each line represents a rule, followed by a list of members.
# These members are the default owners for all files that match the specified pattern.
# The pattern generally follows the same syntax used for .gitignore files.
# The last matching rule always wins; those that appear lower in the file take precedence over rules that appear higher up.
# Specify owners by their username, email, or role assignment in the project.
# Examples:
# Member with username "john.smith" and member with email "alex@mycompany.com"
# own any JavaScript file in repository
# *.js john.smith alex@mycompany.com
# Bob owns all files under "subdir" directory at the repository root and all its subdirectories
# /subdir/ Bob
# All members from team named "Product Team" file under root "Product Documentation" directory
# "/Product Documentation" "Product Team"
# All members who are assigned the Project Collaborator role own any file under docs/ directory
# anywhere in the repository, but not further nested files
# docs/* "Project Collaborator"
# This file itself is owned by members who are assigned the Project Admin role in this project.
CODEOWNERS "Project Admin"
``
+1
View File
@@ -2,5 +2,6 @@ FROM elasticsearch:8.6.2
MAINTAINER ich@boxi.ch MAINTAINER ich@boxi.ch
LABEL name="ElasticSearch with German dictionary" LABEL name="ElasticSearch with German dictionary"
LABEL org.opencontainers.image.source="https://gitea.tail276105.ts.net/boxi/elasticsearch"
ADD analysis /usr/share/elasticsearch/config/analysis ADD analysis /usr/share/elasticsearch/config/analysis
-31
View File
@@ -1,31 +0,0 @@
# boxit/ElasticSearch
## Getting Started
Download links:
SSH clone URL: ssh://git@git.jetbrains.space/boxi/boxit/ElasticSearch.git
HTTPS clone URL: https://git.jetbrains.space/boxi/boxit/ElasticSearch.git
These instructions will get you a copy of the project up and running on your local machine for development and testing purposes.
## Prerequisites
What things you need to install the software and how to install them.
```
Examples
```
## Deployment
Add additional notes about how to deploy this on a production system.
## Resources
Add links to external resources for this project, such as CI server, bug tracker, etc.
Reference in new issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.