Ready for production

.envrc

@@ -0,0 +1,3 @@
+source_url "https://raw.githubusercontent.com/cachix/devenv/95f329d49a8a5289d31e0982652f7058a189bfca/direnvrc" "sha256-d+8cBpDfDBj41inrADaJt+bDWhOktwslgoP5YiGJ1v0="
+
+use devenv

.github/renovate.json

@@ -9,6 +9,7 @@
   "dependencyDashboard": true,
   "automerge": true,
   "automergeType": "pr",
+  "pinDigests": true,
   "packageRules": [
     {
       "matchDepTypes": [

.github/workflows/documentation.yml

@@ -14,18 +14,18 @@ on:
 
 jobs:
   deploy:
-    runs-on: ubuntu-latest
+    runs-on: self-hosted
     steps:
       - name: Check out repository
-        uses: actions/checkout@v3
+        uses: actions/checkout@f43a0e5ff2bd294095638e18286ca9a3d1956744 # v3
 
-      - uses: actions/setup-python@v5
+      - uses: actions/setup-python@0b93645e9fea7318ecaed2b359559ac225c90a2b # v5
         with:
           python-version: 3.x
 
       - run: echo "cache_id=$(date --utc '+%V')" >> $GITHUB_ENV
 
-      - uses: actions/cache@v4
+      - uses: actions/cache@1bd1e32a3bdc45362d1e726936510720a7c30a57 # v4
         with:
           key: mkdocs-material-${{ env.cache_id }}
           path: .cache
@@ -42,13 +42,19 @@ jobs:
       # Deploy with pr-preview only on PRs
       - name: Deploy preview
         if: github.event_name == 'pull_request'
-        uses: rossjrw/pr-preview-action@v1
+        uses: rossjrw/pr-preview-action@430e3dfc1de8a8ae77e77d862d25676ef9db55d1 # v1
         with:
+          token: ${{ secrets.DEPLOY_TOKEN }}
+          custom-url: 4ctf.4ts.fr
           source-dir: ./docs/site
 
-      # Deploy to GitHub Pages only when the main branch
-      - name: Deploy to GitHub Pages
-        run : |
-          cd docs
-          mkdocs gh-deploy --force
+      - name: Deploy preview directory
         if: github.ref == 'refs/heads/main' && github.event_name == 'push'
+        uses: JamesIves/github-pages-deploy-action@15de0f09300eea763baee31dff6c6184995c5f6a # v4.7.2
+        with:
+          token: ${{ secrets.DEPLOY_TOKEN }}
+          folder: ./docs/site
+          commit-message: Deploy production site 🚀
+          clean: true
+          clean-exclude: .gitignore
+          force: false

.github/workflows/golang-unit-tests.yml

@@ -0,0 +1,30 @@
+name: Go Unit Tests
+
+on:
+  push:
+    branches:
+      - '*'
+  pull_request:
+    branches:
+      - '*'
+
+jobs:
+  test:
+    runs-on: self-hosted
+
+    steps:
+    - name: Checkout code
+      uses: actions/checkout@f43a0e5ff2bd294095638e18286ca9a3d1956744 # v3
+
+    - name: Set up Go
+      uses: actions/setup-go@93397bea11091df50f3d7e59dc26a7711a8bcfbe # v4
+      with:
+        go-version: '1.23.3'
+
+    - name: Install dependencies
+      working-directory: ./back
+      run: go get -v -t -d ./...
+
+    - name: Run unit tests
+      working-directory: ./back
+      run: go test ./... -v

.github/workflows/semantic-release.yml

@@ -8,11 +8,11 @@ on:
 
 jobs:
   release:
-    runs-on: ubuntu-latest
+    runs-on: self-hosted
 
     steps:
       - name: Check out repository
-        uses: actions/checkout@v3
+        uses: actions/checkout@f43a0e5ff2bd294095638e18286ca9a3d1956744 # v3
         with:
           fetch-depth: 0  # Required for Semantic Release to access full git history
 
@@ -26,7 +26,7 @@ jobs:
           ssh-keyscan github.com >> ~/.ssh/known_hosts
 
       - name: Set up Node.js
-        uses: actions/setup-node@v3
+        uses: actions/setup-node@1a4442cacd436585916779262731d5b162bc6ec7 # v3
         with:
           node-version: '20'  # Use the latest Node.js version here
 

.gitignore

@@ -1,2 +1,19 @@
 # Semantic Release
-node_modules
+node_modules
+
+# Devenv
+.devenv*
+devenv.local.nix
+
+# direnv
+.direnv
+
+# pre-commit
+.pre-commit-config.yaml
+
+# tmp
+tmp/
+
+# env
+.env
+config.yaml

.gitmodules

@@ -0,0 +1,3 @@
+[submodule "back/templates/sqlboiler"]
+	path = back/templates/sqlboiler
+	url = https://github.com/volatiletech/sqlboiler

CODE_OF_CONDUCT.md

@@ -0,0 +1,79 @@
+# Code of Conduct
+
+We are committed to creating an inclusive and welcoming environment for everyone involved in the 4CTF project. By participating in this project, you agree to abide by the following Code of Conduct.
+
+---
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming community, we pledge to:
+
+- Be respectful and inclusive in all interactions.
+- Avoid harassment or discrimination of any kind.
+- Value different perspectives and experiences.
+- Accept constructive criticism graciously.
+- Demonstrate empathy and kindness toward others.
+
+---
+
+## Our Standards
+
+Examples of behavior that contribute to a positive environment include:
+
+- Using welcoming and inclusive language.
+- Being respectful of differing opinions, viewpoints, and experiences.
+- Gracefully accepting constructive criticism.
+- Focusing on what is best for the community.
+- Showing empathy and care toward other participants.
+
+Examples of unacceptable behavior include:
+
+- The use of sexualized language or imagery and unwelcome sexual attention or advances.
+- Trolling, insulting or derogatory comments, and personal or political attacks.
+- Public or private harassment.
+- Publishing others’ private information, such as physical or electronic addresses, without explicit permission.
+- Other conduct that could reasonably be considered inappropriate in a professional setting.
+
+---
+
+## Scope
+
+This Code of Conduct applies both within project spaces (e.g., the repository, issue trackers, and pull requests) and in public spaces when an individual is representing the project or its community.
+
+---
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the project maintainers via email at **[insert email address]**. All complaints will be reviewed and investigated promptly and fairly.
+
+Project maintainers are obligated to maintain confidentiality regarding the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+---
+
+## Enforcement Guidelines
+
+Maintainers will follow these Community Impact Guidelines to determine the consequences for any action they deem in violation of this Code of Conduct:
+
+1. **Correction**  
+   *Community Impact*: A single minor issue.  
+   *Consequence*: A private, written warning with guidance on improving behavior.
+
+2. **Warning**  
+   *Community Impact*: A sustained pattern of inappropriate behavior.  
+   *Consequence*: A warning and temporary restrictions from community interactions.
+
+3. **Temporary Ban**  
+   *Community Impact*: A serious violation or repeated warnings.  
+   *Consequence*: Temporary ban from participation in the project.
+
+4. **Permanent Ban**  
+   *Community Impact*: Severe or repeated violations.  
+   *Consequence*: Permanent removal from the project community.
+
+---
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant, version 2.1](https://www.contributor-covenant.org/version/2/1/code_of_conduct.html).
+
+For further details, see the [Contributor Covenant FAQ](https://www.contributor-covenant.org/faq/).

CONTRIBUTING.md

@@ -0,0 +1,88 @@
+# Contributing to 4CTF
+
+We welcome contributions to the 4CTF project! To ensure a smooth process for everyone, please follow the guidelines below.
+
+## Table of Contents
+
+- [Contributing to 4CTF](#contributing-to-4ctf)
+  - [Table of Contents](#table-of-contents)
+  - [Code of Conduct](#code-of-conduct)
+  - [How Can I Contribute?](#how-can-i-contribute)
+    - [Reporting Bugs](#reporting-bugs)
+    - [Suggesting Features](#suggesting-features)
+    - [Submitting Code](#submitting-code)
+  - [Pull Request Guidelines](#pull-request-guidelines)
+  - [Commit Messages](#commit-messages)
+    - [Examples](#examples)
+    - [Common Types](#common-types)
+
+---
+
+## Code of Conduct
+
+By participating in this project, you agree to abide by our [Code of Conduct](CODE_OF_CONDUCT.md). Be respectful and collaborative!
+
+---
+
+## How Can I Contribute?
+
+### Reporting Bugs
+
+1. Search for existing issues before submitting a new one.
+2. Provide detailed steps to reproduce the bug, your environment, and any relevant logs.
+
+### Suggesting Features
+
+1. Open an issue with a clear and descriptive title.
+2. Explain the problem and how the feature would address it.
+
+### Submitting Code
+
+1. Fork the repository and clone your fork.
+2. Create a new branch from `develop`.
+3. Make your changes.
+4. Open a pull request (PR) targeting the `develop` branch.
+
+---
+
+## Pull Request Guidelines
+
+1. **Target Branch**: All PRs must point to the `develop` branch. Changes are merged into `main` only for releases.
+2. **Branch Naming**: Use descriptive branch names, e.g., `feature/add-something` or `bugfix/fix-issue`.
+3. **Description**: Include a clear description of your changes and link to related issues if applicable.
+4. **Tests**: Ensure your code is covered by tests if possible.
+5. **Review Process**: Wait for at least one approval from a maintainer before merging.
+
+---
+
+## Commit Messages
+
+We follow the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) specification. Please structure your commit messages as follows:
+
+```a
+<type>[optional scope]: <description>
+
+[optional body]
+
+[optional footer(s)]
+```
+
+### Examples
+
+- `feat(api): add endpoint for user registration`
+- `fix(ui): resolve button alignment issue on mobile`
+- `docs(readme): update contributing section`
+
+### Common Types
+
+- `feat`: A new feature
+- `fix`: A bug fix
+- `docs`: Documentation changes
+- `style`: Code style changes (formatting, no code logic changes)
+- `refactor`: Code refactoring (neither fixes a bug nor adds a feature)
+- `test`: Adding or updating tests
+- `chore`: Maintenance tasks (e.g., updating dependencies)
+
+---
+
+Thank you for contributing to 4CTF! 🎉

back/.air.toml

@@ -0,0 +1,49 @@
+root = "."
+testdata_dir = "testdata"
+tmp_dir = "tmp"
+
+[build]
+  bin = "/bin/bash -c 'source refresh-env && bin/server serve'"
+  cmd = "go build -ldflags '-s -w' -o bin/server main.go"
+  delay = 1000
+  exclude_dir = ["assets", "tmp", "vendor", "testdata", "node_modules", "models", "venv"]
+  exclude_file = []
+  exclude_regex = ["_test.go", "_templ.go"]
+  exclude_unchanged = true
+  follow_symlink = false
+  full_bin = ""
+  include_dir = []
+  include_ext = ["go", "tpl", "tmpl", "html", "templ", "env"]
+  include_file = []
+  kill_delay = "0s"
+  log = "build-errors.log"
+  poll = false
+  poll_interval = 0
+  post_cmd = []
+  rerun = false
+  rerun_delay = 500
+  send_interrupt = false
+  stop_on_error = false
+
+[color]
+  app = ""
+  build = "yellow"
+  main = "magenta"
+  runner = "green"
+  watcher = "cyan"
+
+[log]
+  main_only = false
+  time = false
+
+[misc]
+  clean_on_exit = false
+
+[proxy]
+  app_port = 0
+  enabled = false
+  proxy_port = 0
+
+[screen]
+  clear_on_rebuild = false
+  keep_scroll = true

back/.env.example

@@ -0,0 +1,11 @@
+MYSQL_USER=rtyop
+MYSQL_PASSWORD=rtyop
+MYSQL_DATABASE=rtyop
+MYSQL_PORT=3306
+MYSQL_HOST=127.0.0.1
+MYSQL_SCHEMA_FILE=sql/schema.sql
+MYSQL_MIGRATIONS_FOLDER=sql/migrations
+
+DATABASE_URL=mysql://rtyop:rtyop@127.0.0.1:3306/rtyop
+DBMATE_MIGRATIONS_DIR=sql/migrations
+DBMATE_SCHEMA_FILE=sql/schema.sql