cleanup Legacy files

This commit is contained in:
Thomas Boksberger committed 2026-06-29 07:37:25 +02:00
1 parent 77da3822ba
commit 69815e3ff5
3 files changed
-72

No files matched your search

-17
View File
@@ -1,17 +0,0 @@
job("Docker") {
host("Build and push a Docker image") {
shellScript {
content = """
export DOCKER_CLI_EXPERIMENTAL=enabled;
docker buildx create --name boxitkeycloak || true 2>/dev/null;
docker buildx use boxitkeycloak;
docker buildx build \
--platform linux/arm64,linux/amd64 \
--tag boxi.registry.jetbrains.space/p/boxit/containers/boxit-keycloak:0.0.${"$"}JB_SPACE_EXECUTION_NUMBER \
--push \
.;
""".trimIndent()
}
}
}
-24
View File
@@ -1,24 +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"
-31
View File
@@ -1,31 +0,0 @@
# boxit/Keycloak
## Getting Started
Download links:
SSH clone URL: ssh://git@git.jetbrains.space/boxi/boxit/Keycloak.git
HTTPS clone URL: https://git.jetbrains.space/boxi/boxit/Keycloak.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.