WIP: Implement Geographic Data Models and Migrations

.dokku/predeploy

@@ -0,0 +1,3 @@
+#!/bin/bash
+bundle install
+bundle exec rails db:migrate

.dokku/release.sh

@@ -0,0 +1,28 @@
+#!/bin/bash
+
+# Exit immediately if a command exits with a non-zero status.
+set -e
+
+# Ensure Sentry CLI is installed
+if ! command -v sentry-cli &> /dev/null
+then
+    echo "sentry-cli could not be found, please install it."
+    exit 1
+fi
+
+# Set the release version
+RELEASE_VERSION=$(git rev-parse --short HEAD)
+
+# Export the release version as an environment variable
+export SENTRY_RELEASE=$RELEASE_VERSION
+
+# Notify Sentry of the new release
+sentry-cli releases new $SENTRY_RELEASE
+sentry-cli releases finalize $SENTRY_RELEASE
+
+echo "Sentry release $SENTRY_RELEASE has been set."
+
+# Run any pending migrations (if needed)
+bundle exec rails db:migrate
+
+echo "Release step completed."

.dokku/web.sh

@@ -0,0 +1,6 @@
+# release.sh
+#!/bin/bash
+set -e
+
+mkdir -p spec/dummy/tmp/pids
+bash -c "rm -f spec/dummy/tmp/pids/server.pid && cd ./spec/dummy && bundle exec puma -C config/puma.rb"

.env.db.dev

@@ -0,0 +1,2 @@
+POSTGRES_USER=postgres
+POSTGRES_PASSWORD=postgres

.env.dev

@@ -0,0 +1,15 @@
+# 
+# Copy this file to `.env.dev` `cp ./.env.sample ./.env.dev`
+# 
+
+# App URLS
+ALLOWED_HOSTS='http://localhost:3000'
+APP_HOST='http://localhost:3000'
+BASE_URL='http://localhost:3000'
+
+REDIS_URL='redis://community-engine-redis:6379'
+
+# Mail config
+SMTP_PASSWORD=
+SMTP_USERNAME='apikey'
+SMTP_address='smtp.sendgrid.net'

.env.prod.sample

@@ -0,0 +1,35 @@
+ALLOWED_HOSTS=yourdomain.com
+APP_HOST=yourdomain.com
+BASE_URL=yourdomain.com
+
+DATABASE_URL=your-postgres-connection-string
+REDIS_URL=your-redis-connection-string
+
+ASSET_HOST=cdn-assets.yourdomain.com
+FOG_HOST=cdn-assets.yourdomain.com
+
+AWS_ACCESS_KEY_ID=your-aws-key-id
+AWS_SECRET_ACCESS_KEY=your-aws-secret-access-key
+
+CDN_DISTRIBUTION_ID=your-cdn-distribution-id
+
+S3_BUCKET_NAME=your-s3-bucket-name
+FOG_DIRECTORY=your-s3-bucket-name
+
+S3_REGION=your-s3-region
+FOG_REGION=your-s3-region
+
+LANG='en_US.UTF-8'
+PORT=5000
+
+RACK_ENV=production
+RAILS_ENV=production
+RAILS_LOG_LEVEL=debug
+RAILS_LOG_TO_STDOUT=true
+RAILS_SERVE_STATIC_FILES=true
+
+SENTRY_DSN=your-sentry-dsn-url
+
+SMTP_ADDRESS=your-smtp-address
+SMTP_PASSWORD=your-smtp-password
+SMTP_USERNAME=your-smtp-username

.github/workflows/rubyonrails.yml

@@ -11,11 +11,11 @@ on:
   pull_request:
     branches: [ "main" ]
 jobs:
-  test:
+  rspec:
     runs-on: ubuntu-latest
     services:
       postgres:
-        image: postgres:11-alpine
+        image: postgis/postgis:latest
         ports:
           - "5432:5432"
         env:
@@ -40,7 +40,19 @@ jobs:
       - name: Run tests
         run: rm -f spec/dummy/tmp/pids/server.pid && bundle exec rspec
 
-  lint:
+  rubocop:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v3
+      - name: Install Ruby and gems
+        uses: ruby/setup-ruby@55283cc23133118229fd3f97f9336ee23a179fcf # v1.146.0
+        with:
+          bundler-cache: true
+      - name: Lint Ruby files with Rubocop
+        run: bundle exec rubocop --parallel
+
+  security:
     runs-on: ubuntu-latest
     steps:
       - name: Checkout code
@@ -55,23 +67,3 @@ jobs:
         run: bundle exec bundler-audit --update
       - name: Security audit application code
         run: bundle exec brakeman -q -w2
-      - name: Lint Ruby files
-        run: bundle exec rubocop --parallel
-
-
-  # lint:
-  #   runs-on: ubuntu-latest
-  #   steps:
-  #     - name: Checkout code
-  #       uses: actions/checkout@v3
-  #     - name: Install Ruby and gems
-  #       uses: ruby/setup-ruby@55283cc23133118229fd3f97f9336ee23a179fcf # v1.146.0
-  #       with:
-  #         bundler-cache: true
-  #     # Add or replace any other lints here
-  #     - name: Security audit dependencies
-  #       run: bin/bundler-audit --update
-  #     - name: Security audit application code
-  #       run: bin/brakeman -q -w2
-  #     - name: Lint Ruby files
-  #       run: bin/rubocop --parallel

.gitignore

@@ -52,4 +52,7 @@ node_modules/
 
 spec/dummy/storage/og/9g/og9gmixuxfbx1sl5rgk6brbjmvms
 spec/dummy/storage/va/ri/variants/og9gmixuxfbx1sl5rgk6brbjmvms/6e7b83b26e6f33c216f6d559f3b939a455b14b656f2fc1797c3cfcef371301b5
-spec/dummy/storage/*
+spec/dummy/storage/*
+
+.env.prod
+spec/dummy/config/master.key

CODE_OF_CONDUCT.md

@@ -0,0 +1,128 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+[email protected].
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior,  harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.

Dockerfile

@@ -1,20 +1,87 @@
+# This Dockerfile is only used for the production deployment using dokku.
+# When pushed to dokku via git, it detects this Dockerfile and automatically chooses Docker build
 
-FROM ruby:3.2
+# Stage 1: Build environment
+FROM ruby:3.2.2 AS builder
 
+# Define build-time variables
+ARG AWS_ACCESS_KEY_ID
+ARG AWS_SECRET_ACCESS_KEY
+ARG FOG_DIRECTORY
+ARG FOG_HOST
+ARG FOG_REGION
+ARG ASSET_HOST
+ARG CDN_DISTRIBUTION_ID
+
+# Set environment variables for asset precompilation
+ENV AWS_ACCESS_KEY_ID=${AWS_ACCESS_KEY_ID}
+ENV AWS_SECRET_ACCESS_KEY=${AWS_SECRET_ACCESS_KEY}
+ENV FOG_DIRECTORY=${FOG_DIRECTORY}
+ENV FOG_HOST=${FOG_HOST}
+ENV FOG_REGION=${FOG_REGION}
+ENV ASSET_HOST=${ASSET_HOST}
+ENV CDN_DISTRIBUTION_ID=${CDN_DISTRIBUTION_ID}
+
+# Install dependencies
+RUN apt-get update -qq \
+  && apt-get install -y --no-install-recommends \
+    build-essential \
+    postgresql-client \
+    libpq-dev \
+    nodejs \
+    libssl-dev \
+    apt-transport-https \
+    ca-certificates \
+    libvips42 \
+    curl
+
+# Set working directory
+WORKDIR /community-engine
+
+# Copy Gemfile and Gemfile.lock
+COPY Gemfile Gemfile.lock better_together.gemspec ./
+
+COPY lib lib
+
+# Install bundler and gems
+RUN gem uninstall bundler \
+  && gem install bundler:2.4.13 \
+  && bundle install --jobs 4 --retry 3
+
+# Copy the rest of the application code
+COPY . .
+
+# Precompile assets and sync to S3
+RUN bundle exec rake app:assets:precompile
+RUN bundle exec rake app:assets:sync
+
+# Stage 2: Runtime environment
+FROM ruby:3.2.2
+
+# Install runtime dependencies
 RUN apt-get update -qq \
-  && apt-get install -y build-essential postgresql-client libpq-dev nodejs libssl-dev apt-transport-https ca-certificates libvips42
+  && apt-get install -y --no-install-recommends \
+    libpq-dev \
+    nodejs \
+    libssl-dev \
+    libvips42 \
+    curl \
+  && curl -sL https://sentry.io/get-cli/ | bash \
+  && rm -rf /var/lib/apt/lists/*
 
-RUN curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | apt-key add - \
-  && echo "deb https://dl.yarnpkg.com/debian/ stable main" | tee /etc/apt/sources.list.d/yarn.list
+# Set working directory
+WORKDIR /community-engine
 
-RUN apt-get update -qq && apt-get install -y yarn
+# Copy the application code from the build stage
+COPY --from=builder /community-engine /community-engine
 
-RUN mkdir /btc
-WORKDIR /btc
-COPY Gemfile /btc/Gemfile
-COPY Gemfile.lock /btc/Gemfile.lock
+# Create and set permissions for spec/dummy/tmp/pids directory
+RUN mkdir -p spec/dummy/tmp/pids
+RUN chmod -R 755 spec/dummy/tmp
 
-RUN gem uninstall bundler
-RUN gem install bundler:2.4.13
+# Set environment variables
+ENV RAILS_ENV=production
+ENV RACK_ENV=production
 
-COPY . /btc
+# Run the application
+CMD ["./spec/dummy","bundle", "exec", "puma", "-C", "config/puma.rb"]