first agdsn version of padlist

.github/workflows/buld.yml

@@ -0,0 +1,21 @@
+name: Padlist Build and Push to GitHub Container Registry (ghcr.io)
+on: [push, workflow_dispatch]
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v2
+
+      - name: Login to GitHub Packages
+        uses: docker/login-action@v1
+        with:
+          registry: ghcr.io
+          username: ${{ github.actor }}
+          password: ${{ github.token }}
+
+      - name: Build the Docker image
+        run: docker build -t ghcr.io/agdsn/padlist:${GITHUB_REF_NAME} .
+
+      - name: Push to Github registry
+        run: docker push ghcr.io/agdsn/padlist:${GITHUB_REF_NAME}

Dockerfile

@@ -0,0 +1,80 @@
+# syntax=docker/dockerfile:1
+
+# Comments are provided throughout this file to help you get started.
+# If you need more help, visit the Dockerfile reference guide at
+# https://docs.docker.com/go/dockerfile-reference/
+
+################################################################################
+
+# Create a stage for installing app dependencies defined in Composer.
+FROM composer:lts as deps
+
+WORKDIR /app
+
+# If your composer.json file defines scripts that run during dependency installation and
+# reference your application source files, uncomment the line below to copy all the files
+# into this layer.
+# COPY . .
+
+# Download dependencies as a separate step to take advantage of Docker's caching.
+# Leverage a bind mounts to composer.json and composer.lock to avoid having to copy them
+# into this layer.
+# Leverage a cache mount to /tmp/cache so that subsequent builds don't have to re-download packages.
+RUN --mount=type=bind,source=composer.json,target=composer.json \
+    --mount=type=bind,source=composer.lock,target=composer.lock \
+    --mount=type=cache,target=/tmp/cache \
+    composer install --no-dev --no-interaction
+
+################################################################################
+
+# Create a new stage for running the application that contains the minimal
+# runtime dependencies for the application. This often uses a different base
+# image from the install or build stage where the necessary files are copied
+# from the install stage.
+#
+# The example below uses the PHP Apache image as the foundation for running the app.
+# By specifying the "8.3-apache" tag, it will also use whatever happens to be the
+# most recent version of that tag when you build your Dockerfile.
+# If reproducability is important, consider using a specific digest SHA, like
+# php@sha256:99cede493dfd88720b610eb8077c8688d3cca50003d76d1d539b0efc8cca72b4.
+FROM php:8.3-apache as final
+
+RUN apt-get update && apt-get install -y libpq-dev && docker-php-ext-install pdo pdo_pgsql
+
+# Your PHP application may require additional PHP extensions to be installed
+# manually. For detailed instructions for installing extensions can be found, see
+# https://github.com/docker-library/docs/tree/master/php#how-to-install-more-php-extensions
+# The following code blocks provide examples that you can edit and use.
+#
+# Add core PHP extensions, see
+# https://github.com/docker-library/docs/tree/master/php#php-core-extensions
+# This example adds the apt packages for the 'gd' extension's dependencies and then
+# installs the 'gd' extension. For additional tips on running apt-get, see
+# https://docs.docker.com/go/dockerfile-aptget-best-practices/
+# RUN apt-get update && apt-get install -y \
+#     libfreetype-dev \
+#     libjpeg62-turbo-dev \
+#     libpng-dev \
+# && rm -rf /var/lib/apt/lists/* \
+#     && docker-php-ext-configure gd --with-freetype --with-jpeg \
+#     && docker-php-ext-install -j$(nproc) gd
+#
+# Add PECL extensions, see
+# https://github.com/docker-library/docs/tree/master/php#pecl-extensions
+# This example adds the 'redis' and 'xdebug' extensions.
+# RUN pecl install redis-5.3.7 \
+#    && pecl install xdebug-3.2.1 \
+#    && docker-php-ext-enable redis xdebug
+
+# Use the default production configuration for PHP runtime arguments, see
+# https://github.com/docker-library/docs/tree/master/php#configuration
+RUN mv "$PHP_INI_DIR/php.ini-production" "$PHP_INI_DIR/php.ini"
+
+# Copy the app dependencies from the previous install stage.
+COPY --from=deps app/vendor/ /var/www/html/vendor
+# Copy the app files from the app directory.
+COPY src /var/www/html
+
+# Switch to a non-privileged user (defined in the base image) that the app will run under.
+# See https://docs.docker.com/go/dockerfile-user-best-practices/
+USER www-data

README.Docker.md

@@ -0,0 +1,19 @@
+### Building and running your application
+
+When you're ready, start your application by running:
+`docker compose up --build`.
+
+Your application will be available at http://localhost:9000.
+
+### Deploying your application to the cloud
+
+First, build your image, e.g.: `docker build -t myapp .`.
+If your cloud uses a different CPU architecture than your development
+machine (e.g., you are on a Mac M1 and your cloud provider is amd64),
+you'll want to build the image for that platform, e.g.:
+`docker build --platform=linux/amd64 -t myapp .`.
+
+Then, push it to your registry, e.g. `docker push myregistry.com/myapp`.
+
+Consult Docker's [getting started](https://docs.docker.com/go/get-started-sharing/)
+docs for more detail on building and pushing.

compose.yaml

@@ -0,0 +1,65 @@
+# Comments are provided throughout this file to help you get started.
+# If you need more help, visit the Docker compose reference guide at
+# https://docs.docker.com/go/compose-spec-reference/
+
+# Here the instructions define your application as a service called "server".
+# This service is built from the Dockerfile in the current directory.
+# You can add other services your application may depend on here, such as a
+# database or a cache. For examples, see the Awesome Compose repository:
+# https://github.com/docker/awesome-compose
+services:
+  server:
+    build:
+      context: .
+    ports:
+      - 9000:80
+    develop:
+      watch:
+        - action: sync
+          path: ./src
+          target: /var/www/html
+    environment:
+      - HEDGEDOC_URL=
+      # Database
+      - DB_HOST=
+      - DB_NAME=
+      - DB_USER=
+      # Keycloak
+      - KEYCLOAK_AUTH_SERVER_URL=
+      - KEYCLOAK_REALM=
+      - KEYCLOAK_CLIENT_ID=
+      - KEYCLOAK_CLIENT_SECRET=
+      - KEYCLOAK_REDIRECT_URI=
+# The commented out section below is an example of how to define a PostgreSQL
+# database that your application can use. `depends_on` tells Docker Compose to
+# start the database before your application. The `db-data` volume persists the
+# database data between container restarts. The `db-password` secret is used
+# to set the database password. You must create `db/password.txt` and add
+# a password of your choosing to it before running `docker-compose up`.
+#     depends_on:
+#       db:
+#         condition: service_healthy
+#   db:
+#     image: postgres
+#     restart: always
+#     user: postgres
+#     secrets:
+#       - db-password
+#     volumes:
+#       - db-data:/var/lib/postgresql/data
+#     environment:
+#       - POSTGRES_DB=example
+#       - POSTGRES_PASSWORD_FILE=/run/secrets/db-password
+#     expose:
+#       - 5432
+#     healthcheck:
+#       test: [ "CMD", "pg_isready" ]
+#       interval: 10s
+#       timeout: 5s
+#       retries: 5
+# volumes:
+#   db-data:
+# secrets:
+#   db-password:
+#     file: db/password.txt
+

composer.json

@@ -1,5 +1,6 @@
 {
     "require": {
-        "league/oauth2-client": "^2.7"
+        "league/oauth2-client": "^2.7",
+        "stevenmaguire/oauth2-keycloak": "^5.1"
     }
 }

src/.htaccess

@@ -0,0 +1 @@
+RedirectMatch 403 /vendor(/.*|$)