[ { "path": ".app_version", "content": "1.3.4\n" }, { "path": ".circleci/config.yml", "content": "version: 2.1\n\norbs:\n ruby: circleci/ruby@2.1.4\n browser-tools: circleci/browser-tools@1.4.8\n\njobs:\n test:\n docker:\n - image: cimg/ruby:3.4.6-browsers\n environment:\n RAILS_ENV: test\n CI: true\n DATABASE_HOST: localhost\n DATABASE_NAME: dawarich_test\n DATABASE_USERNAME: postgres\n DATABASE_PASSWORD: mysecretpassword\n DATABASE_PORT: 5432\n - image: cimg/postgres:13.3-postgis\n environment:\n POSTGRES_USER: postgres\n POSTGRES_DB: dawarich_test\n POSTGRES_PASSWORD: mysecretpassword\n - image: redis:7.0\n - image: selenium/standalone-chrome:latest\n name: chrome\n environment:\n START_XVFB: 'false'\n JAVA_OPTS: -Dwebdriver.chrome.whitelistedIps=\n\n steps:\n - checkout\n - browser-tools/install-chrome\n - browser-tools/install-chromedriver\n - run:\n name: Install Bundler\n command: gem install bundler\n - run:\n name: Bundle Install\n command: bundle install --jobs=4 --retry=3\n - run:\n name: Wait for Selenium Chrome\n command: |\n dockerize -wait tcp://chrome:4444 -timeout 1m\n - run:\n name: Database Setup\n command: |\n bundle exec rails db:create RAILS_ENV=test\n bundle exec rails db:schema:load RAILS_ENV=test\n # Create the queue database manually if it doesn't exist\n PGPASSWORD=mysecretpassword createdb -h localhost -U postgres dawarich_test_queue || true\n - run:\n name: Run RSpec tests\n command: bundle exec rspec\n - store_artifacts:\n path: coverage\n - store_artifacts:\n path: tmp/capybara\n\nworkflows:\n rspec:\n jobs:\n - test\n" }, { "path": ".devcontainer/Dockerfile", "content": "# Base-Image for Ruby and Node.js\nFROM ruby:3.4.6-alpine\n\nENV APP_PATH=/var/app\nENV BUNDLE_VERSION=2.5.21\nENV BUNDLE_PATH=/usr/local/bundle/gems\nENV TMP_PATH=/tmp/\nENV RAILS_LOG_TO_STDOUT=true\nENV RAILS_PORT=3000\n\n# Install dependencies for application\nRUN apk -U add --no-cache \\\n build-base \\\n git \\\n postgresql-dev \\\n postgresql-client \\\n libxml2-dev \\\n libxslt-dev \\\n nodejs \\\n yarn \\\n imagemagick \\\n tzdata \\\n less \\\n yaml-dev \\\n # gcompat for nokogiri on mac m1\n gcompat \\\n && rm -rf /var/cache/apk/* \\\n && mkdir -p $APP_PATH\n\nRUN gem update --system 3.6.2 && gem install bundler --version \"$BUNDLE_VERSION\" \\\n && rm -rf $GEM_HOME/cache/*\n\n# FIXME It would be a good idea to use a other user than root, but this lead to permission error on export and maybe more yet.\n# RUN adduser -D -h ${APP_PATH} vscode\nUSER root\n\n# Navigate to app directory\nWORKDIR $APP_PATH\n\nEXPOSE $RAILS_PORT\n\n" }, { "path": ".devcontainer/devcontainer.json", "content": "{\n \"name\": \"Ruby and Node DevContainer\",\n \"dockerComposeFile\": [\"docker-compose.yml\"],\n \"service\": \"dawarich_dev\",\n \"settings\": {\n \"terminal.integrated.defaultProfile.linux\": \"bash\"\n },\n \"extensions\": [\n \"rebornix.ruby\", // Ruby-Support\n \"esbenp.prettier-vscode\", // Prettier for JS-Formating\n \"dbaeumer.vscode-eslint\" // ESLint for JavaScript\n ],\n \"postCreateCommand\": \"yarn install && bundle config set --local path 'vendor/bundle' && bundle install --jobs 20 --retry 5\",\n \"forwardPorts\": [3000], // Redirect to Rails-App-Server\n \"remoteUser\": \"root\",\n \"workspaceFolder\": \"/var/app\"\n}\n" }, { "path": ".devcontainer/docker-compose.yml", "content": "networks:\n dawarich:\nservices:\n dawarich_dev:\n build:\n context: .\n dockerfile: Dockerfile\n container_name: dawarich_dev\n volumes:\n - dawarich_public:/var/app/public\n - dawarich_watched:/var/app/tmp/imports/watched\n - dawarich_storage:/var/app/storage\n networks:\n - dawarich\n ports:\n - 3000:3000\n - 9394:9394\n stdin_open: true\n tty: true\n environment:\n RAILS_ENV: development\n REDIS_URL: redis://dawarich_redis:6379\n DATABASE_HOST: dawarich_db\n DATABASE_USERNAME: postgres\n DATABASE_PASSWORD: password\n DATABASE_NAME: dawarich_development\n APPLICATION_HOSTS: localhost\n TIME_ZONE: Europe/London\n APPLICATION_PROTOCOL: http\n PROMETHEUS_EXPORTER_ENABLED: false\n PROMETHEUS_EXPORTER_HOST: 0.0.0.0\n PROMETHEUS_EXPORTER_PORT: 9394\n dawarich_redis:\n image: redis:7.4-alpine\n container_name: dawarich_redis\n command: redis-server\n networks:\n - dawarich\n volumes:\n - dawarich_shared:/data\n restart: always\n healthcheck:\n test: [ \"CMD\", \"redis-cli\", \"--raw\", \"incr\", \"ping\" ]\n interval: 10s\n retries: 5\n start_period: 30s\n timeout: 10s\n dawarich_db:\n image: postgis/postgis:17-3.5-alpine\n container_name: dawarich_db\n volumes:\n - dawarich_db_data:/var/lib/postgresql/data\n - dawarich_shared:/var/shared\n networks:\n - dawarich\n restart: always\n healthcheck:\n test: [ \"CMD-SHELL\", \"pg_isready -U postgres -d dawarich_development\" ]\n interval: 10s\n retries: 5\n start_period: 30s\n timeout: 10s\n environment:\n POSTGRES_USER: postgres\n POSTGRES_PASSWORD: password\nvolumes:\n dawarich_db_data:\n dawarich_shared:\n dawarich_public:\n dawarich_watched:\n dawarich_storage:\n" }, { "path": ".dockerignore", "content": "/log\n/tmp\n\n# We need directories for import and export files, but not the files themselves.\n/public/exports/*\n!/public/exports/.keep\n/public/imports/*\n!/public/imports/.keep\n\n.git/\n.github/\ndocs/\n.circleci/\n.devcontainer/\nscreenshots/\n.ruby-lsp/\n" }, { "path": ".gitattributes", "content": "# See https://git-scm.com/docs/gitattributes for more about git attribute files.\n\n# Mark the database schema as having been generated.\ndb/schema.rb linguist-generated\n\n# Mark any vendored files as having been vendored.\nvendor/* linguist-vendored\n" }, { "path": ".github/FUNDING.yml", "content": "# These are supported funding model platforms\n\ngithub: # Replace with up to 4 GitHub Sponsors-enabled usernames e.g., [user1, user2]\npatreon: freika # Replace with a single Patreon username\nopen_collective: # Replace with a single Open Collective username\nko_fi: freika\ntidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel\ncommunity_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry\nliberapay: # Replace with a single Liberapay username\nissuehunt: # Replace with a single IssueHunt username\nlfx_crowdfunding: # Replace with a single LFX Crowdfunding project-name e.g., cloud-foundry\npolar: # Replace with a single Polar username\nbuy_me_a_coffee: # Replace with a single Buy Me a Coffee username\ncustom: # Replace with up to 4 custom sponsorship URLs e.g., ['link1', 'link2']\n" }, { "path": ".github/ISSUE_TEMPLATE/bug_report.md", "content": "---\nname: Bug report\nabout: Create a report to help us improve\ntitle: ''\nlabels: ''\nassignees: ''\n\n---\n\n**BEFORE OPENING AN ISSUE, MAKE SURE YOU READ THIS: https://github.com/Freika/dawarich/issues/1382**\n\n**OS & Hardware**\nProvide your software and hardware specs\n\n**Version**\nProvide the version of Dawarich you're experiencing the problem on.\n\n**Describe the bug**\nA clear and concise description of what the bug is.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n1. Go to '...'\n2. Click on '....'\n3. Scroll down to '....'\n4. See error\n\n**Expected behavior**\nA clear and concise description of what you expected to happen.\n\n**Screenshots**\nIf applicable, add screenshots to help explain your problem.\n\n**Logs**\nIf applicable, add logs from the `dawarich_app` container to help explain your problem.\n\n**Additional context**\nAdd any other context about the problem here.\n" }, { "path": ".github/dependabot.yml", "content": "# To get started with Dependabot version updates, you'll need to specify which\n# package ecosystems to update and where the package manifests are located.\n# Please see the documentation for all configuration options:\n# https://docs.github.com/github/administering-a-repository/configuration-options-for-dependency-updates\n\nversion: 2\nupdates:\n - package-ecosystem: 'bundler'\n directory: '/'\n schedule:\n interval: 'weekly'\n" }, { "path": ".github/workflows/attach_compose.yml", "content": "name: Attach docker-compose.yml to release\n\non:\n release:\n types: [published]\n\npermissions:\n contents: write\n\njobs:\n attach-compose:\n if: ${{ !github.event.release.prerelease }}\n runs-on: ubuntu-latest\n\n steps:\n - uses: actions/checkout@v4\n\n - name: Upload docker-compose.yml to release\n env:\n GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}\n run: gh release upload \"${{ github.event.release.tag_name }}\" docker/docker-compose.yml\n" }, { "path": ".github/workflows/biome.yml", "content": "name: biome\non:\n push:\n pull_request:\njobs:\n quality:\n runs-on: ubuntu-latest\n permissions:\n contents: read\n steps:\n - name: Checkout\n uses: actions/checkout@v6\n with:\n persist-credentials: false\n fetch-depth: 0\n - name: Determine base ref\n id: base\n env:\n BASE_REF: ${{ github.base_ref }}\n EVENT_NAME: ${{ github.event_name }}\n run: |\n if [ \"$EVENT_NAME\" = \"pull_request\" ]; then\n CURRENT=$(git rev-parse --abbrev-ref HEAD)\n if [ \"$BASE_REF\" != \"$CURRENT\" ]; then\n git fetch origin \"$BASE_REF\":\"$BASE_REF\"\n fi\n echo \"ref=$BASE_REF\" >> \"$GITHUB_OUTPUT\"\n else\n echo \"ref=HEAD~1\" >> \"$GITHUB_OUTPUT\"\n fi\n - name: Setup Biome\n uses: biomejs/setup-biome@v2\n with:\n version: 2.3.11\n - name: Run Biome\n env:\n BASE: ${{ steps.base.outputs.ref }}\n run: biome ci . --reporter=github --changed --since=\"$BASE\" --no-errors-on-unmatched\n" }, { "path": ".github/workflows/build_and_push.yml", "content": "name: Docker image build and push\n\non:\n workflow_dispatch:\n inputs:\n branch:\n description: \"The branch to build the Docker image from\"\n required: false\n default: \"master\"\n release:\n types: [created]\n\npermissions: {}\n\njobs:\n prepare:\n runs-on: ubuntu-22.04\n outputs:\n version: ${{ steps.meta.outputs.version }}\n is_prerelease: ${{ steps.meta.outputs.is_prerelease }}\n platforms: ${{ steps.meta.outputs.platforms }}\n matrix: ${{ steps.meta.outputs.matrix }}\n steps:\n - name: Compute version and platforms\n id: meta\n run: |\n if [[ $GITHUB_REF == refs/tags/* ]]; then\n VERSION=${GITHUB_REF#refs/tags/}\n else\n VERSION=$GITHUB_REF_NAME\n fi\n if [ -z \"$VERSION\" ]; then\n VERSION=\"rc\"\n fi\n\n IS_PRERELEASE=\"${{ github.event.release.prerelease }}\"\n PLATFORMS=\"linux/amd64,linux/arm64,linux/arm/v7\"\n MATRIX='{\"include\":[{\"platform\":\"linux/amd64\",\"runner\":\"ubuntu-22.04\"},{\"platform\":\"linux/arm64\",\"runner\":\"ubuntu-22.04-arm\"},{\"platform\":\"linux/arm/v7\",\"runner\":\"ubuntu-22.04-arm\"}]}'\n\n echo \"version=${VERSION}\" >> $GITHUB_OUTPUT\n echo \"is_prerelease=${IS_PRERELEASE}\" >> $GITHUB_OUTPUT\n echo \"platforms=${PLATFORMS}\" >> $GITHUB_OUTPUT\n echo \"matrix=${MATRIX}\" >> $GITHUB_OUTPUT\n\n build-and-push-docker:\n permissions:\n contents: read\n needs: prepare\n strategy:\n fail-fast: false\n matrix: ${{ fromJSON(needs.prepare.outputs.matrix) }}\n runs-on: ${{ matrix.runner }}\n steps:\n - name: Checkout code\n uses: actions/checkout@v4\n with:\n ref: ${{ github.event.inputs.branch || github.ref_name }}\n\n # QEMU only needed for arm/v7 (armv7 emulated on aarch64 runner)\n - name: Set up QEMU\n if: matrix.platform == 'linux/arm/v7'\n uses: docker/setup-qemu-action@v3\n with:\n platforms: linux/arm/v7\n\n - name: Set up Docker Buildx\n uses: docker/setup-buildx-action@v3\n\n - name: Cache Docker layers\n uses: actions/cache@v4\n with:\n path: /tmp/.buildx-cache\n key: ${{ runner.os }}-${{ matrix.platform }}-buildx-${{ github.sha }}\n restore-keys: |\n ${{ runner.os }}-${{ matrix.platform }}-buildx-\n\n - name: Install dependencies\n run: npm install\n\n - name: Docker meta\n id: meta\n uses: docker/metadata-action@v5\n with:\n images: ${{ secrets.DOCKERHUB_USERNAME }}/dawarich\n\n - name: Login to Docker Hub\n uses: docker/login-action@v3.1.0\n with:\n username: ${{ secrets.DOCKERHUB_USERNAME }}\n password: ${{ secrets.DOCKERHUB_TOKEN }}\n\n - name: Prepare platform pair\n id: platform\n run: |\n PAIR=$(echo \"${{ matrix.platform }}\" | tr '/' '-')\n echo \"pair=${PAIR}\" >> \"$GITHUB_OUTPUT\"\n\n - name: Build and push by digest\n id: build\n uses: docker/build-push-action@v5\n with:\n context: .\n file: ./docker/Dockerfile\n platforms: ${{ matrix.platform }}\n outputs: type=image,name=${{ secrets.DOCKERHUB_USERNAME }}/dawarich,push-by-digest=true,name-canonical=true,push=true\n labels: ${{ steps.meta.outputs.labels }}\n cache-from: type=local,src=/tmp/.buildx-cache\n cache-to: type=local,dest=/tmp/.buildx-cache-new,mode=max\n\n - name: Rotate cache\n run: |\n rm -rf /tmp/.buildx-cache\n mv /tmp/.buildx-cache-new /tmp/.buildx-cache\n\n - name: Export digest\n run: |\n mkdir -p \"${{ runner.temp }}/digests\"\n DIGEST=\"${{ steps.build.outputs.digest }}\"\n touch \"${{ runner.temp }}/digests/${DIGEST#sha256:}\"\n\n - name: Upload digest\n uses: actions/upload-artifact@v4\n with:\n name: digest-${{ steps.platform.outputs.pair }}\n path: ${{ runner.temp }}/digests/*\n if-no-files-found: error\n retention-days: 1\n\n merge:\n permissions:\n contents: read\n needs: [prepare, build-and-push-docker]\n runs-on: ubuntu-22.04\n steps:\n - name: Checkout code\n uses: actions/checkout@v4\n with:\n ref: ${{ github.event.inputs.branch || github.ref_name }}\n\n - name: Login to Docker Hub\n uses: docker/login-action@v3.1.0\n with:\n username: ${{ secrets.DOCKERHUB_USERNAME }}\n password: ${{ secrets.DOCKERHUB_TOKEN }}\n\n - name: Set up Docker Buildx\n uses: docker/setup-buildx-action@v3\n\n - name: Download all digests\n uses: actions/download-artifact@v4\n with:\n path: ${{ runner.temp }}/digests\n pattern: digest-*\n merge-multiple: true\n\n - name: Build Docker tags\n id: docker_tags\n run: |\n IMAGE=\"${{ secrets.DOCKERHUB_USERNAME }}/dawarich\"\n VERSION=\"${{ needs.prepare.outputs.version }}\"\n IS_PRERELEASE=\"${{ needs.prepare.outputs.is_prerelease }}\"\n\n TAGS=\"${IMAGE}:${VERSION}\"\n\n if [ \"$IS_PRERELEASE\" = \"true\" ]; then\n TAGS=\"${TAGS},${IMAGE}:rc\"\n else\n TAGS=\"${TAGS},${IMAGE}:latest\"\n fi\n\n echo \"tags=${TAGS}\" >> $GITHUB_OUTPUT\n\n - name: Create manifest list and push\n working-directory: ${{ runner.temp }}/digests\n run: |\n TAGS=\"${{ steps.docker_tags.outputs.tags }}\"\n\n TAG_ARGS=\"\"\n IFS=',' read -ra TAG_LIST <<< \"$TAGS\"\n for TAG in \"${TAG_LIST[@]}\"; do\n TAG_ARGS=\"${TAG_ARGS} -t ${TAG}\"\n done\n\n SOURCES=$(printf \"${{ secrets.DOCKERHUB_USERNAME }}/dawarich@sha256:%s \" *)\n\n docker buildx imagetools create ${TAG_ARGS} ${SOURCES}\n\n - name: Inspect final image\n run: |\n TAGS=\"${{ steps.docker_tags.outputs.tags }}\"\n FIRST_TAG=\"${TAGS%%,*}\"\n docker buildx imagetools inspect \"${FIRST_TAG}\"\n" }, { "path": ".github/workflows/ci.yml", "content": "name: CI\n# Not functional at the moment\n\non:\n pull_request:\n push:\n branches: [main]\n\npermissions:\n contents: read\n\njobs:\n test:\n runs-on: ubuntu-latest\n\n services:\n postgres:\n image: postgres\n env:\n POSTGRES_USER: postgres\n POSTGRES_PASSWORD: postgres\n ports:\n - 5432:5432\n options: --health-cmd=\"pg_isready\" --health-interval=10s --health-timeout=5s --health-retries=3\n redis:\n image: redis\n ports:\n - 6379:6379\n\n steps:\n - name: Install packages\n run: sudo apt-get update && sudo apt-get install --no-install-recommends -y google-chrome-stable curl libjemalloc2 libvips postgresql-client libpq-dev\n\n - name: Checkout code\n uses: actions/checkout@v4\n\n - name: Set up Ruby\n uses: ruby/setup-ruby@v1\n with:\n ruby-version: '3.4.6'\n bundler-cache: true\n\n - name: Set up Node.js\n uses: actions/setup-node@v3\n with:\n node-version: '16' # Use the appropriate Node.js version\n\n - name: Install Node.js dependencies\n run: npm install\n\n - name: Install Ruby dependencies\n run: bundle install\n\n - name: Run bundler audit\n run: |\n gem install bundler-audit\n bundle audit --update\n\n - name: Setup database\n env:\n RAILS_ENV: test\n DATABASE_URL: postgres://postgres:postgres@localhost:5432\n REDIS_URL: redis://localhost:6379/1\n run: bin/rails db:setup\n\n - name: Run main tests (excluding system tests)\n env:\n RAILS_ENV: test\n DATABASE_URL: postgres://postgres:postgres@localhost:5432\n REDIS_URL: redis://localhost:6379/1\n run: |\n bundle exec rspec --exclude-pattern \"spec/system/**/*_spec.rb\" || (cat log/test.log && exit 1)\n\n - name: Run system tests\n env:\n RAILS_ENV: test\n DATABASE_URL: postgres://postgres:postgres@localhost:5432\n REDIS_URL: redis://localhost:6379/1\n run: |\n bundle exec rspec spec/system/ || (cat log/test.log && exit 1)\n\n - name: Keep screenshots from failed system tests\n uses: actions/upload-artifact@v4\n if: failure()\n with:\n name: screenshots\n path: ${{ github.workspace }}/tmp/capybara\n if-no-files-found: ignore\n\n - name: Upload coverage reports to Codecov\n uses: codecov/codecov-action@v4.0.1\n with:\n token: ${{ secrets.CODECOV_TOKEN }}\n" }, { "path": ".github/workflows/release_notifications.yml", "content": "name: Release Notifications\n\non:\n workflow_run:\n workflows: [\"Docker image build and push\"]\n types: [completed]\n\npermissions:\n contents: read\n\njobs:\n notify:\n runs-on: ubuntu-latest\n # Only run when build succeeded and was triggered by a release\n if: >\n github.event.workflow_run.conclusion == 'success' &&\n github.event.workflow_run.event == 'release'\n\n steps:\n - uses: actions/checkout@v4\n\n - name: Get release info\n id: version\n env:\n GH_TOKEN: ${{ github.token }}\n HEAD_BRANCH: ${{ github.event.workflow_run.head_branch }}\n REPO: ${{ github.repository }}\n run: |\n # The head_branch of a release-triggered workflow is the tag name\n TAG=\"$HEAD_BRANCH\"\n\n # Fetch release details by tag\n RELEASE_JSON=$(gh api \"repos/$REPO/releases/tags/$TAG\" 2>/dev/null || true)\n\n if [ -z \"$RELEASE_JSON\" ]; then\n echo \"Could not find release for tag $TAG, trying latest\"\n RELEASE_JSON=$(gh api \"repos/$REPO/releases/latest\")\n TAG=$(echo \"$RELEASE_JSON\" | jq -r '.tag_name')\n fi\n\n URL=$(echo \"$RELEASE_JSON\" | jq -r '.html_url')\n PRERELEASE=$(echo \"$RELEASE_JSON\" | jq -r '.prerelease')\n\n echo \"tag=$TAG\" >> $GITHUB_OUTPUT\n echo \"url=$URL\" >> $GITHUB_OUTPUT\n echo \"prerelease=$PRERELEASE\" >> $GITHUB_OUTPUT\n echo \"Release: $TAG (prerelease: $PRERELEASE)\"\n\n - name: Extract changelog for version\n if: steps.version.outputs.prerelease != 'true'\n id: changelog\n env:\n VERSION: ${{ steps.version.outputs.tag }}\n run: |\n # Remove 'v' prefix if present for matching changelog headers\n VERSION_NUM=\"${VERSION#v}\"\n\n # Extract section between this version and the next version header\n # The changelog format is: # [version] - date\n NOTES=$(sed -n \"/^# \\[$VERSION_NUM\\]/,/^# \\[/p\" CHANGELOG.md | sed '$d' | tail -n +2)\n\n # Store in output (handle multiline)\n echo \"notes<> $GITHUB_OUTPUT\n echo \"$NOTES\" >> $GITHUB_OUTPUT\n echo \"EOF\" >> $GITHUB_OUTPUT\n\n - name: Generate summary\n if: steps.version.outputs.prerelease != 'true'\n id: summary\n env:\n NOTES: ${{ steps.changelog.outputs.notes }}\n run: |\n # Count items in each section using stateful awk to properly track sections\n ADDED=$(echo \"$NOTES\" | awk '/^## Added/{f=1;next} /^## [A-Z]/{f=0} f&&/^- /{c++} END{print c+0}')\n FIXED=$(echo \"$NOTES\" | awk '/^## Fixed/{f=1;next} /^## [A-Z]/{f=0} f&&/^- /{c++} END{print c+0}')\n CHANGED=$(echo \"$NOTES\" | awk '/^## Changed/{f=1;next} /^## [A-Z]/{f=0} f&&/^- /{c++} END{print c+0}')\n REMOVED=$(echo \"$NOTES\" | awk '/^## Removed/{f=1;next} /^## [A-Z]/{f=0} f&&/^- /{c++} END{print c+0}')\n\n # Build summary line\n PARTS=\"\"\n [ \"$ADDED\" -gt 0 ] && PARTS=\"$ADDED new feature$([ \"$ADDED\" -gt 1 ] && echo 's')\"\n [ \"$FIXED\" -gt 0 ] && PARTS=\"${PARTS:+$PARTS, }$FIXED fix$([ \"$FIXED\" -gt 1 ] && echo 'es')\"\n [ \"$CHANGED\" -gt 0 ] && PARTS=\"${PARTS:+$PARTS, }$CHANGED improvement$([ \"$CHANGED\" -gt 1 ] && echo 's')\"\n [ \"$REMOVED\" -gt 0 ] && PARTS=\"${PARTS:+$PARTS, }$REMOVED removal$([ \"$REMOVED\" -gt 1 ] && echo 's')\"\n\n # Default if nothing found\n [ -z \"$PARTS\" ] && PARTS=\"various updates\"\n\n echo \"summary=$PARTS\" >> $GITHUB_OUTPUT\n\n - name: Post to Discord\n if: steps.version.outputs.prerelease != 'true'\n env:\n DISCORD_WEBHOOK: ${{ secrets.DISCORD_WEBHOOK_URL }}\n VERSION: ${{ steps.version.outputs.tag }}\n RELEASE_URL: ${{ steps.version.outputs.url }}\n SUMMARY: ${{ steps.summary.outputs.summary }}\n run: |\n # Discord embed with summary\n curl -H \"Content-Type: application/json\" \\\n -d \"{\n \\\"embeds\\\": [{\n \\\"title\\\": \\\"šŸš€ Dawarich $VERSION Released!\\\",\n \\\"url\\\": \\\"$RELEASE_URL\\\",\n \\\"color\\\": 5814783,\n \\\"description\\\": \\\"A new version of Dawarich is available!\\\\n\\\\n**This release:** $SUMMARY\\\\n\\\\n[šŸ“‹ View full changelog]($RELEASE_URL)\\\",\n \\\"footer\\\": {\n \\\"text\\\": \\\"docker pull freikin/dawarich:$VERSION\\\"\n }\n }]\n }\" \\\n \"$DISCORD_WEBHOOK\"\n\n - name: Post to Mastodon\n if: steps.version.outputs.prerelease != 'true'\n env:\n MASTODON_ACCESS_TOKEN: ${{ secrets.MASTODON_ACCESS_TOKEN }}\n VERSION: ${{ steps.version.outputs.tag }}\n RELEASE_URL: ${{ steps.version.outputs.url }}\n SUMMARY: ${{ steps.summary.outputs.summary }}\n run: |\n # Build status message using printf for proper newlines\n STATUS=$(printf '%s\\n\\n%s\\n\\n%s\\n%s\\n\\n%s' \\\n \"šŸš€ Dawarich $VERSION is out!\" \\\n \"This release: $SUMMARY\" \\\n \"šŸ“¦ docker pull freikin/dawarich:$VERSION\" \\\n \"šŸ“‹ Changelog: $RELEASE_URL\" \\\n \"#Dawarich #SelfHosted #LocationTracking #Privacy #OpenSource\")\n\n curl -X POST \\\n -H \"Authorization: Bearer $MASTODON_ACCESS_TOKEN\" \\\n -F \"status=$STATUS\" \\\n \"https://mastodon.social/api/v1/statuses\"\n" }, { "path": ".github/workflows/rubocop.yml", "content": "name: RuboCop\non:\n push:\n pull_request:\n\npermissions:\n contents: read\n\njobs:\n rubocop:\n runs-on: ubuntu-latest\n steps:\n - name: Checkout\n uses: actions/checkout@v6\n with:\n fetch-depth: 0\n - name: Determine base ref\n id: base\n env:\n BASE_REF: ${{ github.base_ref }}\n EVENT_NAME: ${{ github.event_name }}\n run: |\n if [ \"$EVENT_NAME\" = \"pull_request\" ]; then\n CURRENT=$(git rev-parse --abbrev-ref HEAD)\n if [ \"$BASE_REF\" != \"$CURRENT\" ]; then\n git fetch origin \"$BASE_REF\":\"$BASE_REF\"\n fi\n echo \"ref=$BASE_REF\" >> \"$GITHUB_OUTPUT\"\n else\n echo \"ref=HEAD~1\" >> \"$GITHUB_OUTPUT\"\n fi\n - name: Set up Ruby\n uses: ruby/setup-ruby@v1\n with:\n bundler-cache: true\n - name: Run RuboCop on changed files\n env:\n BASE: ${{ steps.base.outputs.ref }}\n run: |\n # Get list of added/modified Ruby files compared to base ref\n FILES=$(git diff --name-only --diff-filter=AM \"$BASE\"...HEAD | grep -E '\\.(rb|rake)$|^Gemfile$|^Rakefile$' | xargs)\n\n if [ -n \"$FILES\" ]; then\n bundle exec rubocop --force-exclusion --format github $FILES\n else\n echo \"No Ruby files changed.\"\n fi\n" }, { "path": ".gitignore", "content": "# See https://help.github.com/articles/ignoring-files for more about ignoring files.\n#\n# If you find yourself ignoring temporary files generated by your text editor\n# or operating system, you probably want to add a global ignore instead:\n# git config --global core.excludesfile '~/.gitignore_global'\n\n# Ignore bundler config.\n/.bundle\n\n# Ignore all logfiles and tempfiles.\n/log/*\n/tmp/*\n!/log/.keep\n!/tmp/.keep\n\n# Ignore pidfiles, but keep the directory.\n/tmp/pids/*\n!/tmp/pids/\n!/tmp/pids/.keep\n\n# Ignore uploaded files in development.\n/storage/*\n!/storage/.keep\n/tmp/storage/*\n!/tmp/storage/\n!/tmp/storage/.keep\n/tmp/imports/*\n!/tmp/imports/\n/tmp/imports/watched/*\n!/tmp/imports/watched/\n!/tmp/imports/watched/.keep\n!/tmp/imports/watched/put-your-directory-here.txt\n\n\n/public/assets\n\n# Ignore all files under /public/exports except the .keep file\n/public/exports/*\n!/public/exports/.keep\n!/public/exports/\n\n# Ignore all files under /public/imports, but keep .keep files and the watched directory\n/public/imports/*\n!/public/imports/.keep\n\n# Ignore master key for decrypting credentials and more.\n/config/master.key\n/coverage\n/node_modules\n\n!/app/assets/builds/.keep\n.DS_Store\n.env\n\n.byebug_history\n\n\n.devcontainer/.onCreateCommandMarker\n.devcontainer/.postCreateCommandMarker\n.devcontainer/.updateContentCommandMarker\n\n.vscode-server/\n.ash_history\n.cache/\n.dotnet/\n.cursorrules\n.cursormemory.md\n.serena/**/*\n\n/config/credentials/production.key\n/config/credentials/production.yml.enc\n/config/credentials/staging.key\n/config/credentials/staging.yml.enc\n\nMakefile\n\n/db/*.sqlite3\n/db/*.sqlite3-shm\n/db/*.sqlite3-wal\n\n# Playwright\nnode_modules/\n/test-results/\n/playwright-report/\n/blob-report/\n/playwright/.cache/\n/e2e/temp/\n\n.claude\n.worktrees/\n" }, { "path": ".rspec", "content": "--require spec_helper\n--profile\n" }, { "path": ".rubocop.yml", "content": "AllCops:\n NewCops: disable\n Exclude:\n - 'db/schema.rb'\nplugins: rubocop-rails\n\nStyle/Documentation:\n Enabled: false\n\nStyle/ClassAndModuleChildren:\n Enabled: false\n\nLayout/HashAlignment:\n Enabled: false\n\nMetrics/BlockLength:\n Enabled: false\n\nMetrics/MethodLength:\n Enabled: false\n\nMetrics/AbcSize:\n Enabled: false\n\nMetrics/CyclomaticComplexity:\n Enabled: false\n\nMetrics/PerceivedComplexity:\n Enabled: false\n\nMetrics/ModuleLength:\n Enabled: false\n\nMetrics/ParameterLists:\n Enabled: false\n\nMetrics/ClassLength:\n Enabled: false\n\nNaming/VariableNumber:\n Exclude:\n - 'spec/**/*'\n\nRails/UniqueValidationWithoutIndex:\n Enabled: false\n\nRails/SkipsModelValidations:\n Enabled: false\n\nRails/BulkChangeTable:\n Exclude:\n - 'db/migrate/**/*'\n\nRails/ReversibleMigration:\n Exclude:\n - 'db/migrate/**/*'\n\nRails/NotNullColumn:\n Exclude:\n - 'db/migrate/**/*'\n\nLint/ConstantDefinitionInBlock:\n Exclude:\n - 'lib/tasks/**/*'\n\nLint/UnreachableCode:\n Exclude:\n - 'db/data/**/*'\n\nRails/LexicallyScopedActionFilter:\n Enabled: false\n\nRails/OutputSafety:\n Enabled: false\n\nNaming/AccessorMethodName:\n Enabled: false\n\nNaming/PredicatePrefix:\n Enabled: false\n\nLayout/LineLength:\n Exclude:\n - 'config/initializers/devise.rb'\n" }, { "path": ".ruby-version", "content": "3.4.6\n" }, { "path": "AGENTS.md", "content": "# Repository Guidelines\n\n## Project Structure & Module Organization\nDawarich is a Rails 8 monolith. Controllers, models, jobs, services, policies, and Stimulus/Turbo JS live in `app/`, while shared POROs sit in `lib/`. Configuration, credentials, and cron/Sidekiq settings live in `config/`; API documentation assets are in `swagger/`. Database migrations and seeds live in `db/`, Docker tooling sits in `docker/`, and docs or media live in `docs/` and `screenshots/`. Runtime artifacts in `storage/`, `tmp/`, and `log/` stay untracked.\n\n## Architecture & Key Services\nThe stack pairs Rails 8 with PostgreSQL + PostGIS, Redis-backed Sidekiq, Devise/Pundit, Tailwind + DaisyUI, and Leaflet/Chartkick. Imports, exports, sharing, and trip analytics lean on PostGIS geometries plus workers, so queue anything non-trivial instead of blocking requests.\n\n## Build, Test, and Development Commands\n- `docker compose -f docker/docker-compose.yml up` ā€” launches the full stack for smoke tests.\n- `bundle exec rails db:prepare` ā€” create/migrate the PostGIS database.\n- `bundle exec bin/dev` and `bundle exec sidekiq` ā€” start the web/Vite/Tailwind stack and workers locally.\n- `make test` ā€” runs Playwright (`npx playwright test e2e --workers=1`) then `bundle exec rspec`.\n- `bundle exec rubocop` / `npx prettier --check app/javascript` ā€” enforce formatting before commits.\n\n## Coding Style & Naming Conventions\nUse two-space indentation, snake_case filenames, and CamelCase classes. Keep Stimulus controllers under `app/javascript/controllers/*_controller.ts` so names match DOM `data-controller` hooks. Prefer service objects in `app/services/` for multi-step imports/exports, and let migrations named like `202405061210_add_indexes_to_events` manage schema changes. Follow Tailwind ordering conventions and avoid bespoke CSS unless necessary.\n\n## Testing Guidelines\nRSpec mirrors the app hierarchy inside `spec/` with files suffixed `_spec.rb`; rely on FactoryBot/FFaker for data, WebMock for HTTP, and SimpleCov for coverage. Browser journeys live in `e2e/` and should use `data-testid` selectors plus seeded demo data to reset state. Run `make test` before pushing and document intentional gaps when coverage dips.\n\n## Commit & Pull Request Guidelines\nWrite short, imperative commit subjects (`Add globe_projection setting`) and include the PR/issue reference like `(#2138)` when relevant. Target `dev`, describe migrations, configs, and verification steps, and attach screenshots or curl examples for UI/API work. Link related Discussions for larger changes and request review from domain owners (imports, sharing, trips, etc.).\n\n## Security & Configuration Tips\nStart from `.env.example` or `.env.template` and store secrets in encrypted Rails credentials; never commit files from `gps-env/` or real trace data. Rotate API keys, scrub sensitive coordinates in fixtures, and use the synthetic traces in `db/seeds.rb` when demonstrating imports.\n" }, { "path": "CHANGELOG.md", "content": "# Changelog\nAll notable changes to this project will be documented in this file.\n\nThe format is based on [Keep a Changelog](http://keepachangelog.com/)\nand this project adheres to [Semantic Versioning](http://semver.org/).\n\n## [1.3.4] - 2026-03-15\n\n### Changed\n\n- Redesigned onboarding modal with two paths: \"I have data\" (inline file import) and \"Start tracking\" (app download + QR code). New users with existing location data can now start importing within 2 clicks of signing up.\n- Onboarding completion is now persisted server-side (`settings.onboarding_completed`) instead of relying solely on localStorage, preventing the modal from reappearing after browser data clears.\n- Route opacity data migration now runs as a background job instead of inline during migration, improving deployment reliability for large instances.\n\n### Fixed\n\n- Fix admin and supporter tooltip overflowing the page on narrow screens. #1449\n- Fix date navigation arrow tooltips overlapping with the navbar on map pages. #2229 #2100\n- Fix infinite loading spinner when a trip has no points in its date range. #2293\n- Fix Insights monthly digest panels disappearing when switching months. #2305\n- Fix suggested visit confirm/decline not removing the visit from the list. #2307\n- Fix Stats page reloading when clicking \"countries, cities\" link. #2270\n- Fix map base layer selection not being restored after page reload (Maps v1). #2093\n- Fix duplicate country names in stats caused by geocoder returning different spellings. #2044\n- Fix total distance display overlapping layer picker when distance is in miles. #2017\n- Fix default route opacity displaying as 6000% for new users. #1891\n- Fix shared month stats map missing hexagons from the last day of the month. #1934\n- Fix Nominatim reverse geocoder producing all places named \"Suggested place\" instead of actual place names. #2182\n- Fix IDL-crossing route segmenter returning inconsistent coordinate types. `unwrapCoordinates` now always returns a uniform array-of-arrays structure. #2038\n- Fix a migration taking too long. #2375\n- Fix family sharing not including the requesting user's own location. #2153\n- The \"Destroy\" button on the trip page is now orange. #2348\n\n## [1.3.3] - 2026-03-12\n\n### Added\n\n- Better user management with pagination, search, and filtering in the admin panel. Admins can now easily find and manage users based on email, registration date, and activity status.\n\n### Fixed\n\n- Points table now converts speed from m/s to km/h (or mph) using the user's distance unit preference. Previously raw m/s values were displayed with a \"km/h\" label. #2337\n- Digest list API (`GET /api/v1/digests`) now returns distance as a structured object with `meters`, `converted`, and `unit` fields, matching the detail endpoint. Previously it returned raw meters, causing clients to display incorrect values. **Breaking change**: the `distance` field changed from an integer to an object. #2336\n- Dead documentation links in v0.26.0 changelog entry now point to the correct URLs. #2344\n- Filter out Immich and Photoprism api keys from logs to prevent accidental exposure. #2368\n- Fix foreign key violation when deleting users with place_visits referencing visits.\n- Fix reverse geocoding job failing on points with nil timestamp or lonlat.\n- Fix unsupported archive format generating Sentry noise instead of a user-friendly notification.\n- Fix deadlock in reverse geocoding places upsert under concurrent Sidekiq workers.\n- Reduce Redis disk I/O by relaxing RDB snapshot frequency. Previously the default `save 60 10000` rule caused a snapshot every ~60 seconds due to Sidekiq polling, generating tens of terabytes of disk writes over weeks. New defaults: snapshots every 15 minutes (10+ changes) or 5 minutes (100+ changes).\n- Reduce default Sidekiq concurrency from 10 to 5 threads. Most self-hosted instances don't need 10 workers and the extra threads increase Redis polling traffic.\n- Migration bug for version skippers. #2362\n\n## [1.3.2] - 2026-03-08\n\n**Important**: Self-hosters are not limited in any way. All features remain fully available regardless of plan. The new Lite plan and related limitations apply only to Dawarich Cloud users. If you're self-hosting, you can ignore the Lite plan details below. Self-hosted instances will continue to have access to all features without any restrictions.\n\n### Added\n\n- Lite plan for Dawarich Cloud. Lite includes core tracking, map visualization (routes, points), stats, and the read API. Data view is limited to the last 12 months ā€” older data is archived but can always be exported. Pro-only features: Heatmap, Fog of War, Scratch Map, Globe View, Immich/Photoprism integrations, public stats sharing, and write API (update/delete). Lite users can still create points via the API. Self-hosted instances are unaffected ā€” all features remain fully available regardless of plan.\n- Timed layer previews for Lite users on the map. Toggling a Pro-only layer (Heatmap, Fog of War, Scratch Map) shows it for 20 seconds with a countdown, then auto-hides with an upgrade prompt.\n- Per-plan API rate limiting via `rack-attack`. Lite: 200 requests/hour, Pro: 1,000 requests/hour. Self-hosted instances are exempt. Rate-limited responses return 429 with `Retry-After` header.\n- Archival warning notifications for Lite users approaching the 12-month data window: in-app notification at 11 months, email at 11.5 months, archived confirmation at 12 months.\n- `GET /api/v1/plan` endpoint returning the user's current plan and feature availability.\n- `X-Total-Points-In-Range` and `X-Scoped-Points` response headers on the points API, allowing clients to detect when data is being windowed.\n- Branded OAuth buttons for Google and GitHub on the login page.\n\n### Changed\n\n- Numeric-only strings passed to timestamp API parameters (e.g. `start_at`, `end_at`) are now treated as Unix timestamps directly. Previously they were passed through `Time.zone.parse`, which could return unexpected results. If you were relying on the old behavior for numeric strings, update your API calls accordingly.\n- The user serializer now includes `plan` in the `subscription` object.\n\n## [1.3.1] - 2026-02-27\n\n### Changed\n\n- User deletion now being done in the background to prevent request timeouts for users with large amount of data.\n\n### Fixed\n\n- Point speed in Map V2 is now correctly calculated from m/s to km/h or mph based on user preference. #2308\n- Family members are now being loaded correctly on Map V2 when family layer is enabled. #2250\n- Photos popups on Map V2 now show the photo timestamp in user's timezone. #2310\n- Fix the issue preventing fresh app from starting. #2304\n\n## [1.3.0] - 2026-02-25\n\nThe Storage & Timeline Interaction Release\n\nThis release adds a dedicated `motion_data` column for transportation-relevant fields alongside the existing `raw_data`. Users can now set their timezone for accurate date/time display across the app. The Timeline feed in Map v2 gains richer map interaction: hovering a journey highlights its track with an animated border, clicking zooms to fit and selects it, and expanding a day shows visit markers even when the Visits layer is off. User data export/import is enhanced with a new v2 format using JSONL files and monthly splitting for large datasets, while remaining backward-compatible with the old format.\n\n### Added\n\n- Per-user timezone setting. Users can now select their timezone from Settings > General, and all dates/times across the app (including background jobs and API responses) will respect it. Defaults to the server's `TIME_ZONE` environment variable for existing users.\n- `motion_data` JSONB column on the `points` table for storing transportation-relevant fields separately from `raw_data`.\n- Background job (`DataMigrations::BackfillMotionDataJob`) to backfill `motion_data` from `raw_data` for existing points.\n- New Timeline feed in Map v2 Tools panel for browsing daily location history. Distances and speeds respect the user's distance unit preference (km/mi).\n- Clicking a track point (when \"Show Points\" is enabled) now displays point info (timestamp, battery, altitude, speed) in the track info panel instead of triggering a position update. Dragging a point still updates its position and triggers track recalculation.\n- Timeline-map interaction: hovering a journey entry in the Timeline feed now highlights the matching track on the map with the animated border and flow effect. Clicking a journey entry zooms the map to fit the track and keeps it selected. Expanding a day in the Timeline now temporarily shows visit markers for that day, even if the Visits layer is disabled.\n- AES-256-GCM encryption for raw data archives (format version 2). Set `ARCHIVE_ENCRYPTION_KEY` to use a custom key; otherwise derives from `SECRET_KEY_BASE`. Existing unencrypted archives (format version 1) are read transparently.\n- v2 export/import format with JSONL files and monthly splitting for large entities (points, visits, stats, tracks, digests). The new format streams data to avoid memory issues with large datasets, while remaining backward-compatible with v1 archives (`data.json`).\n- User data export now includes Tags, Taggings, Tracks (with embedded TrackSegments), Digests, and Raw Data Archives ā€” previously missing from export/import, meaning users who exported and re-imported would lose these entities.\n- Tracks are exported with their `original_path` serialized as WKT and `track_segments` embedded as a nested array, preserving transportation mode detection data across export/import cycles.\n- Digests get a fresh `sharing_uuid` on import for security ā€” old share links from the original user won't work for the importing user.\n- Raw Data Archives are exported with their attached gzip files, enabling full data restoration.\n- Failed imports now will have an error message shown to the user.\n- Pagination now looks nicer and more informative, indicating current page. #2279\n- Imports and exports now can be sorted by name, file size, number of points, and creation date. #2279\n- Lots of missing Swagger specs for the API endpoints have been added, improving API documentation and enabling better client generation. swagger.yaml is updated.\n\n### Changed\n\n- Transportation-relevant fields (motion, activity, action) are now stored in a dedicated `motion_data` column alongside `raw_data`, enabling efficient transportation mode detection.\n- All import sources now write both `raw_data` (full original payload) and `motion_data` (transportation-relevant fields).\n- The `STORE_GEODATA` setting now correctly controls whether geodata is written during reverse geocoding.\n- Dropped unused `idx_points_user_city` database index (304 MB) and replaced the full `reverse_geocoded_at` index (1,149 MB) with a smaller partial index covering only un-geocoded rows.\n- Selecting a track on Map v2 now always dims other tracks, regardless of whether the track has transportation mode segments.\n- Default map layers for new users changed from Routes + Heatmap to Tracks + Heatmap. Existing users' settings are unaffected.\n- Renamed the bottom-panel \"Timeline\" feature to \"Replay\" to avoid naming collision with the new Timeline feed sidebar.\n- Default value for `RAILS_ENV` in `docker-compose.yml` is now `production` instead of `development`\n\n### Fixed\n\n- Stats queries (daily distance, time of day) now correctly handle timezone conversion without double-converting from UTC.\n- Timezone validation in stats queries now properly resolves Rails timezone names to IANA identifiers.\n- Clicking on [Map] on Stats page now correctly respects the user's preferred map version (v1 or v2) instead of always linking to Map v1. #2281\n\n\n## [1.2.0] - 2026-02-15\n\n### Changed\n\n- Overall app performance in browser was improved\n- Docker images are now being built in parallel for both amd64 and arm64 architectures to speed up the build process. Thank you @rtuszik!\n\n### Added\n\n- Map v2 requires WebGL support, so if user's browser doesn't support it or it's disabled, they will see a warning message with a link to the list of supported browsers.\n- New **Insights API** (`GET /api/v1/insights`) returning year overview with totals, activity heatmap, and streak data for the mobile app.\n- New **Insights Details API** (`GET /api/v1/insights/details`) returning year-over-year comparison and travel patterns for the mobile app.\n- New **Digests API** (`GET/POST/DELETE /api/v1/digests`) allowing the mobile app to list, view, generate, and delete yearly digests. Digest generation runs asynchronously via Sidekiq and returns `202 Accepted`. Digest detail supports conditional GET (`Last-Modified` / `304 Not Modified`).\n\n### Fixed\n\n- Scratch map layer is now working again on Map v2.\n- Colored routes on Map v2 are now working correctly. Zoom in closer to see colored segments. #2254\n- Live mode on Map v2 is now working again.\n\n## [1.1.0] - 2026-02-08\n\nThe Timeline Release\n\nIn Map V2 Tools, user can now enable Timeline tool, which allows to quickly navigate through time and see how their location changed throughout the day. It can also be used to replay a trip by clicking the play button. Timeline tool always spans across 24 hours, but you can change the date by clicking on the date picker. Timeline tool is available only on Map V2.\n\n### Added\n\n- Photos are now being clustered on the Map v2 to improve performance and usability when viewing large numbers of photos.\n- City statistics thresholds are now user-configurable: \"Min Minutes in City\" and \"Max Gap Between Points\" sliders in the Map v2 Settings panel. #2207\n- New Timeline tool is added to Map V2. It allows user to quickly navigate through time and see how their location changed throughout the day. It can also be used to replay a trip by clicking the play button.\n\n### Fixed\n\n- The SSL Security Warning is now working correctly on the Immich and Photoprism integration forms.\n- Family members and Places layers are now being correctly remembered across page reloads on Map v2.\n- Immich returning 400. #2222 #2186\n- Points info on the Map V2 now shows time in 24h format and includes seconds. #2172\n- Digests not being created for years earlier than 2000. #2158\n- Tracks on Map V2 are now respecting the date filters correctly. #2196\n- Undefined method `.to_sym` for nil in Sidekiq. #2190\n- `/api/v1/stats` now works faster.\n\n### Changed\n\n- Zooming animation is disabled on Map V2 loading #2219\n- Exporting points to GPX and GeoJSON now works better and faster for large numbers of points by processing the export in chunks to reduce memory usage. #2161\n\n\n## [1.0.4] - 2026-02-01\n\n### Fixed\n\n- Wrong path helper in the navbar for Settings link. #2215 #2213\n\n\n## [1.0.3] - 2026-02-01\n\n### Fixed\n\n- Gemfile being not updated #2210\n- Excessive memory usage during visits suggestions job (thanks @nareddyt!) #2119\n\n### Added\n\n- `SMTP_STARTTLS` environment variable to enable STARTTLS for SMTP connections. Disabled by default.\n\n## [1.0.2] - 2026-01-31\n\nThe Insights, Transportation Mode Detection and Supporter Verification release\n\nQuiet a few big things in this release! It starterted with the idea of adding the Insights page. I experimented with it a bit to see what kinds charts and visualizations we can already have based on the existing data. There were some, but one of the most exciting to me would be the ability to see the Activity Breakdown: now many hours I spent walking, driving and running. Spoiler: I didn't run that much last year :) Anyway, to get that, we needed to have transportation mode detection for tracks. So naturally I went ahead and implemented that as well. Now, not only we can see the activity breakdown, but also, on the Map V2, if you click on a track (Tracks layer should enabled), you will see the transportation modes for it. That's what I wanted for Dawarich for a long time, and I'm happy it's finally here! In the map settings panel, there is now Transportation Mode Detection section, where you can configure speed thresholds for each mode. By default, they are set to reasonable values, but you can tweak them as you wish. Changing the thresholds will recalculate modes for all tracks in the background, which may take a while depending on how many tracks you have.\n\nAnother thing introduced in this release, is support verification. Almost 150 people have supported us financially on [Ko-fi](https://ko-fi.com/freika), [Patreon](https://www.patreon.com/freika) and [GitHub Sponsors](https://github.com/sponsors/Freika/), and if you're one of them, on the Settings page you can now enter your email and verify your support. Verified supporters will get a special (disableable) badge in the navbar as a token of our appreciation. Thank you so much for supporting Dawarich!\n\nAnyway, enjoy the release and don't forget to report any bugs you may find!\n\n### Added\n\n- App-level DNS cache with 5 minutes TTL to reduce DNS lookups and improve performance. #2183\n- New **Insights page** with comprehensive analytics and visualizations:\n - **Activity heatmap**: GitHub-style contribution graph showing daily activity throughout the year\n - **Activity streak**: Track your current streak and longest streak of consecutive active days\n - **Top visited locations**: See your most frequently visited places for the selected year\n - **Year comparison**: Compare stats (distance, countries, cities, active days) with previous year\n - **Activity breakdown**: Visualize your activity distribution by transportation mode\n - **Monthly digest**: Detailed monthly statistics with travel patterns\n - **Travel patterns**: Time-of-day and day-of-week activity distribution\n - **Movement wellness**: Health-related insights based on your movement data\n - **Location clusters**: Geographic clustering of your visited locations\n- **Transportation mode detection for tracks**: Tracks are now automatically segmented by transportation mode (walking, cycling, driving, etc.) with configurable speed thresholds in settings. Modes are recalculated when threshold settings change.\n- **Near real-time track generation**: Tracks are now generated within ~45 seconds of receiving new points (via OwnTracks, Overland, or the Points API) using a Redis-based debouncer. This replaces the previous 4-hour polling cycle for most cases. Daily generation job frequency reduced from every 4 hours to every 12 hours as a fallback.\n- **Track merging**: Consecutive tracks that belong to the same journey are automatically merged when the gap between them is within the configured time threshold.\n- Email preferences moved to \"General\" tab in user settings for better organization.\n\n### Fixed\n\n- Remove assets before precompilation to prevent stale assets from being served. #2187\n- undefined method 'to_sym' for nil in sidekiq #2190\n- `Tracks::BoundaryResolverJob` now uses deterministic exponential backoff instead of random delays, and stops retrying after 5 attempts to avoid infinite rescheduling.\n- Hanging Sidekiq job #2134\n\n### Changed\n\n- Daily track generation job runs every 12 hours instead of every 4 hours, since real-time generation handles most cases.\n\n\n## [1.0.1] - 2026-01-24\n\n### Added\n\n- SSL certificate verification can now be disabled for Immich and Photoprism integrations to support self-signed certificates. A prominent security warning is displayed when this option is enabled. #1645\n\n### Fixed\n\n- Photo timestamps from Immich are now correctly parsed as UTC, fixing the double timezone offset bug where times were displayed incorrectly. #1752\n- Trip photo grids now update immediately after photos are imported, instead of showing cached/stale results for up to 24 hours. #627 #988\n- Immich API responses are now validated for content-type and JSON format before parsing, providing clear diagnostic error messages when the API returns unexpected responses. #698 #1013 #1078\n- Response validator logs truncated response bodies (max 1000 chars) when JSON parsing fails, improving debugging capabilities.\n- GeoJSON formatted points now have correct timestamp parsed from `raw_data['properties']['date']` field.\n- Reduce number of iterations during cache cleaning to improve performance.\n- Version in the navbar is now correct. #2154\n- Dawarich can now be ran under a non-root user in Docker. #1159\n- Fix an error on the Trips page when trip is created but no path is yet calculated. #1426\n- Catch an error with invalid response during reverse-geocoding. #1439\n- In the Immich integration form there are now required permissions listed: `asset.read` and `asset.view`. #1730\n- A doc issue regarding suggesting new visits. #1737\n- `ALLOW_EMAIL_PASSWORD_REGISTRATION` and `OIDC_AUTO_REGISTER` env vars are now being respected correctly. #1972\n- Fog of War layer on Map V1 now properly re-appears when toggled off and on again without requiring a page refresh. #2039\n- User's `points_count` counter cache is now properly updated when creating points via OwnTracks, Overland, and generic Points API. This fixes visit suggestions not working for users using HomeAssistant or similar integrations. #2167\n- Removed redundant subscriptions to WS channel.\n- Live mode is working again on both map V1 and V2.\n\n### Changed\n\n- Map V2 is now the default map version for new users. Existing users will keep using Map V1 unless they change it in the settings.\n- Email preferences moved to dedicated \"Emails\" tab in user settings for better organization.\n\n### Removed\n\n- Tile Usage reporting feature and related prometheus metric have been removed due to low usage. #1876\n\n\n## [1.0.0] - 2026-01-20\n\nThe 1.0.0 release. Same as in 0.37.3, but with updated version number. We're aiming to provide more stable releases going forward.\n\nAll the issues that are currently open in Github will be addressed in the upcoming releases.\n\n\n## [0.37.3] - 2026-01-11\n\n### Fixed\n\n- Routes are now being drawn the very same way on Map V2 as in Map V1. #2132 #2086 #2121\n- RailsPulse performance monitoring is now disabled for self-hosted instances. It fixes poor performance on Synology. #2139 #2096\n\n### Changed\n\n- Map V2 points loading is significantly sped up.\n- Points size on Map V2 was reduced to prevent overlapping. #2122\n- Points sent from Owntracks and Overland are now being created synchronously to instantly reflect success or failure of point creation.\n\n## [0.37.2] - 2026-01-04\n\n### Fixed\n\n- Months are now correctly ordered (Jan-Dec) in the year-end digest chart instead of being sorted alphabetically.\n- Time spent in a country and city is now calculated correctly for the year-end digest email. #2104\n- Updated Trix to fix a XSS vulnerability. #2102\n- Map v2 UI no longer blocks when Immich/Photoprism integration has a bad URL or is unreachable. Added 10-second timeout to photo API requests and improved error handling to prevent UI freezing during initial load. #2085\n\n### Added\n- In Map v2 settings, you can now enable map to be rendered as a globe.\n\n## [0.37.1] - 2025-12-30\n\n### Fixed\n\n- The db migration preventing the app from starting.\n- Raw data archive verifier now allows having points deleted from the db after archiving.\n\n## [0.37.0] - 2025-12-30\n\n### Added\n\n- In the beginning of the year users will receive a year-end digest email with stats about their tracking activity during the past year. Users can opt out of receiving these emails in User Settings -> Notifications. Emails won't be sent if no email is configured in the SMTP settings or if user has no points tracked during the year.\n\n### Changed\n\n- Added and removed some indexes to improve the app performance based on the production usage data.\n\n### Changed\n\n- Deleting an import will now be processed in the background to prevent request timeouts for large imports.\n\n### Fixed\n\n- Deleting an import will no longer result in negative points count for the user.\n- Updating stats. #2022\n- Validate trip start date to be earlier than end date. #2057\n- Fog of war radius slider in map v2 settings is now being respected correctly. #2041\n- Applying changes in map v2 settings now works correctly. #2041\n- Invalidate stats cache on recalculation and other operations that change stats data.\n\n\n## [0.36.4] - 2025-12-26\n\n### Fixed\n\n- Fixed a bug preventing the app to start if a composite index on stats table already exists. #2034 #2051 #2046\n- New compiled assets will override old ones on app start to prevent serving stale assets.\n- Number of points in stats should no longer go negative when points are deleted. #2054\n- Disable Family::Invitations::CleanupJob no invitations are in the database. #2043\n- User can now enable family layer in Maps v2 and center on family members by clicking their emails. #2036\n\n\n## [0.36.3] - 2025-12-14\n\n### Added\n\n- Setting `ARCHIVE_RAW_DATA` env var to true will enable monthly raw data archiving for all users. It will look for points older than 2 months with `raw_data` column not empty and create a zip archive containing raw data files for each month. After successful archiving, raw data will be removed from the database to save space. Monthly archiving job is being run every day at 2:00 AM. Default env var value is false.\n- In map v2, user can now move points when Points layer is enabled. #2024\n- In map v2, routes are now being rendered using same logic as in map v1, route-length-wise. #2026\n\n### Fixed\n\n- Cities visited during a trip are now being calculated correctly. #547 #641 #1686 #1976\n- Points on the map are now show time in user's timezone. #580 #1035 #1682\n- Date range inputs now handle pre-epoch dates gracefully by clamping to valid PostgreSQL integer range. #685\n- Redis client now also being configured so that it could connect via unix socket. #1970\n- Importing KML files now creates points with correct timestamps. #1988\n- Importing KMZ files now works correctly.\n- Map settings are now being respected in map v2. #2012\n\n\n## [0.36.2] - 2025-12-06\n\nThe Map v2 release\n\nIn this release we're introducing Map v2 based on MapLibre GL JS. It brings better performance, smoother interactions and more features in the future. User can select between Map v1 (Leaflet) and Map v2 (MapLibre GL JS) in the Settings -> Map Settings. New map features will be added to Map v2 only.\n\n### Added\n\n- User can select between Map v1 (Leaflet) and Map v2 (MapLibre GL JS) in the User Settings.\n\n### Fixed\n\n- Heatmap and Fog of War now are moving correctly during map interactions on v2 map. #1798\n- Polyline crossing international date line now are rendered correctly on v2 map. #1162\n- Place popup tags parsing (MapLibre GL JS compatibility)\n- Stats calculation should be faster now.\n\n\n## [0.36.1] - 2025-11-29\n\n### Fixed\n\n- Exporting user data now works a lot faster and consumes less memory.\n- Fix the restart loop. #1937 #1975\n\n## [0.36.0] - 2025-11-24\n\nOIDC and KML support release\n\nSo, you want to configure your OIDC provider. If not ā€” skip to the actual changelog. You're going to need to provide at least 4 environment variables: `OIDC_CLIENT_ID`, `OIDC_CLIENT_SECRET`, `OIDC_ISSUER`, and `OIDC_REDIRECT_URI`. Then, if you want to rename the provider from \"OpenID Connect\" to something else (e.g. \"Authentik\"), set `OIDC_PROVIDER_NAME` variable as well. If you want to disable email/password registration and allow only OIDC login, set `ALLOW_EMAIL_PASSWORD_REGISTRATION` to `false`. After just 7 brand new environment variables, you'll never have to deal with passwords in Dawarich again!\n\nJokes aside, even though I'm not a fan of bloating the environment with too many variables, this is a nice addition and it will be reused in the cloud version of Dawarich as well. Thanks for waiting more than a year for this feature!\n\nTo configure your OIDC provider, set the following environment variables:\n\n```\nOIDC_CLIENT_ID=client_id_example\nOIDC_CLIENT_SECRET=client_secret_example\nOIDC_ISSUER=https://authentik.yourdomain.com/application/o/dawarich/\nOIDC_REDIRECT_URI=https://your-dawarich-url.com/users/auth/openid_connect/callback\nOIDC_AUTO_REGISTER=true # optional, default is false\nOIDC_PROVIDER_NAME=YourProviderName # optional, default is OpenID Connect\nALLOW_EMAIL_PASSWORD_REGISTRATION=false # optional, default is true\n```\n\n### Added\n\n- Support for KML file uploads. #350\n- Added a commented line in the `docker-compose.yml` file to use an alternative PostGIS image for ARM architecture.\n- User can now create a place directly from the map and add tags and notes to it. If reverse geocoding is enabled, list of nearby places will be shown as suggestions.\n- User can create and manage tags for places.\n- Visits for manually created places are being suggested automatically, just like for areas.\n- User can enable or disable places layers on the map to show/hide all or just some of their visited places based on tags.\n- User can define privacy zones around places with specific tags to hide map data within a certain radius.\n- If user has a place tagged with a tag named \"Home\" (case insensitive), and this place doesn't have a privacy zone defined, this place will be used as home location for days with no tracked data. #1659 #1575\n\n### Fixed\n\n- The map settings panel is now scrollable\n- Fixed a bug where family location sharing settings were not being updated correctly. #1940\n\n### Changed\n\n- Internal redis settings updated to implement support for connecting to Redis via unix socket. #1706\n- Implemented authentication via GitHub and Google for Dawarich Cloud.\n- Implemented OpenID Connect authentication for self-hosted Dawarich instances. #66\n\n\n## [0.35.1] - 2025-11-09\n\n### Fixed\n\n- StrongMigration issue #1931\n\n\n## [0.35.0] - 2025-11-09\n\nāš ļø Important āš ļø\n\nThe default `docker-compose.yml` file has been updated to provide sensible defaults for self-hosted production environments. This should not break existing setups, but it's recommended to review your `docker-compose.yml` file and update it accordingly.\n\nYou can now set `RAILS_ENV` environment variable to `production` to run Dawarich in production mode.\n\n### Added\n\n- Selection tool on the map now can select points that user can delete in bulk. #433\n\n### Fixed\n\n- Taiwan flag is now shown on its own instead of in combination with China flag.\n- On the registration page and other user forms, if something goes wrong, error messages are now shown to the user.\n- Leaving family, deleting family and cancelling invitations now prompt confirmation dialog to prevent accidental actions.\n- Each pending family invitation now also contains a link to share with the invitee.\n\n### Changed\n\n- Removed useless system tests and cover map functionality with Playwright e2e tests instead.\n- S3 storage now can be used in self-hosted instances as well. Set STORAGE_BACKEND environment variable to `s3` and provide `AWS_ACCESS_KEY_ID`, `AWS_SECRET_ACCESS_KEY`, `AWS_REGION`, `AWS_BUCKET` and `AWS_ENDPOINT_URL` environment variables to configure it.\n- Number of family members on self-hosted instances is no longer limited. #1918\n- Export to GPX now adds speed and course to each point if they are available.\n- `docker-compose.yml` file updated to provide sensible defaults for self-hosted production environment.\n- `.env.example` file added with default environment variables.\n- Single Dockerfile introduced so Dawarich could be run in self-hosted mode in production environment.\n\n## [0.34.2] - 2025-10-31\n\n### Fixed\n\n- Fixed a bug in UTM trackable concern. #1909\n\n## [0.34.1] - 2025-10-30\n\n### Fixed\n\n- Broken Stats page for users with no reverse geocoding enabled. #1877\n\n### Changed\n\n- Date navigation on the map page is no longer shown as floating panel. It is now part of the top navigation bar to prevent overlapping with other map controls. #1894 #1881\n\n### Added\n\n- [Dawarich Cloud] Added support for UTM parameters during user registration. UTM parameters will be stored with the user record for marketing analytics purposes.\n\n## [0.34.0] - 2025-10-10\n\nThe Family release\n\nIn this release we're introducing family features that allow users to create family groups, invite members, and share location data. Family owners can manage members, control sharing settings, and ensure secure access to shared information. Location sharing is optional and can be enabled or disabled by each member individually. Users can join only one family at a time. Location sharing settings can be set to share location for 1, 6, 12, 24 hours or permanently. Family features are now available only for self-hosted instances and will be available in the cloud in the future. When \"Family members\" layer is enabled on the map, family member markers will be updated in real-time.\n\n### Added\n\n- Users can now create family groups and invite members to join.\n\n### Fixed\n\n- Sign out button works again. #1844\n- Fixed user deletion bug where user could not be deleted due to counter cache on points.\n- Users always have default distance unit set to kilometers. #1832\n- All confirmation dialogs are now showing only once.\n\n### Changed\n\n- Minor versions of Dawarich are being built for ARM64 architecture as well again. #1840\n- Importing process for Google Maps Timeline exports, GeoJSON and geodata from photos is now significantly faster.\n- The Map page now features a full-screen map.\n\n\n## [0.33.1] - 2025-10-07\n\n### Changed\n\n- On the Trip page, instead of list of visited countries, a number of them is being shown. Clicking on it opens a modal with a list of countries visited during the trip. #1731\n\n### Fixed\n\n- `GET /api/v1/stats` endpoint now returns correct 0 instead of null if no points were tracked in the requested period.\n- User import data now being streamed instead of loaded into memory all at once. This should prevent large imports from exhausting memory or hitting IO limits while reading export archives.\n- Popup for manual visit creation now looks better in both light and dark modes. #1835\n- Fixed a bug where visit circles were not interactive on the map page. #1833\n- Fixed a bug with stats sharing settings being not filled. #1826\n- Fixed a bug where user could not be deleted due to counter cache on points. #1818\n- Introduce apt-get upgrade before installing new packages in the docker image to prevent vulnerabilities. #1793\n- Fixed time shift when creating visits manually. #1679\n- Provide default map layer if user settings are not set.\n\n## [0.33.0] - 2025-09-29\n\n### Fixed\n\n- Fix a bug where some points from Owntracks were not being processed correctly which prevented import from being created. #1745\n- Hexagons for the stats page are now being calculated a lot faster.\n- Prometheus exporter is now not being started when console is being run.\n- Stats will now properly reflect countries and cities visited after importing new points.\n- `GET /api/v1/points` will now return correct latitude and longitude values. #1502\n- Deleting an import will now trigger stats recalculation for affected months. #1789\n- Importing process should now schedule visits suggestions job a lot faster.\n- Importing GPX files that start with `