Add selenium to devcontainer

[adamoutler]

This commit adds selenium to the post-create command. Add chromium chromium-chromedriver to devcontainer dockerfile. This will enable unit tests which require browser automation in the future.

Summary by CodeRabbit

• Chores
  • Enhanced development container with chromium and chromedriver for browser automation capabilities.
  • Updated development environment dependencies to include selenium for testing automation.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

The devcontainer configuration is updated to add Selenium and Chromium tooling for browser-based testing. System packages (chromium, chromium-chromedriver) are installed via the main Dockerfile, while Selenium is added to Python dependencies through devcontainer.json, with redundant installation removed from the resources Dockerfile.

Changes

Cohort / File(s)	Summary
Devcontainer Dependencies .devcontainer/Dockerfile, .devcontainer/devcontainer.json, .devcontainer/resources/devcontainer-Dockerfile	Added chromium and chromium-chromedriver system packages to main Dockerfile. Added selenium to pip requirements in devcontainer.json. Removed redundant selenium pip installation from resources Dockerfile, consolidating dependency management.

Poem

🐰 A rabbit hops through dev containers bright,
With Selenium and Chrome ready to test each sight,
From pip to apk, dependencies align,
Browser automation tools now perfectly shine! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Add selenium to devcontainer' accurately summarizes the main changes: adding Selenium to devcontainer configurations including pip requirements and supporting browser automation tools.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

.devcontainer/devcontainer.json (1)

50-50: Consider pinning the Selenium version for reproducibility.

While the addition of Selenium enables browser automation testing, note that none of the pip packages in this command have pinned versions (pytest, docker, debugpy, selenium). For consistency and reproducibility across developer environments, consider pinning versions for all packages—for example, selenium==4.27.1.

Regarding ChromeDriver compatibility: Selenium 4.11+ includes Selenium Manager, which automatically manages matching ChromeDriver versions, so compatibility is generally handled automatically if a recent Selenium version is installed. However, explicitly pinning versions provides better control and reproducibility.

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 95413d5 and 934b849.

📒 Files selected for processing (3)

• .devcontainer/Dockerfile
• .devcontainer/devcontainer.json
• .devcontainer/resources/devcontainer-Dockerfile

💤 Files with no reviewable changes (1)

• .devcontainer/resources/devcontainer-Dockerfile

🧰 Additional context used

🧠 Learnings (10)

📓 Common learnings

Learnt from: adamoutler
Repo: jokob-sk/NetAlertX PR: 1184
File: .devcontainer/Dockerfile:82-92
Timestamp: 2025-09-20T14:08:44.152Z
Learning: In devcontainer builds, source repository files are not available during the Docker build phase. The source code gets mounted into the container after it's built and started, so COPY commands referencing source files will fail. Configuration files need to be handled at runtime (e.g., in setup scripts) rather than during the build stage.

Learnt from: adamoutler
Repo: jokob-sk/NetAlertX PR: 1184
File: .devcontainer/Dockerfile:18-19
Timestamp: 2025-09-20T03:01:19.912Z
Learning: In the NetAlertX repository, .devcontainer/Dockerfile is auto-generated and should not be reviewed directly. Review comments about dependencies and build steps should be directed at the root Dockerfile where the actual source commands are located.

Learnt from: adamoutler
Repo: jokob-sk/NetAlertX PR: 1184
File: .devcontainer/devcontainer.json:5-8
Timestamp: 2025-09-20T02:56:24.501Z
Learning: In the NetAlertX devcontainer setup, the final .devcontainer/Dockerfile is generated by combining the root Dockerfile with .devcontainer/resources/devcontainer-Dockerfile using the generate-dockerfile.sh script. The devcontainer.json should reference the generated file, not the root Dockerfile.

📚 Learning: 2025-09-20T03:01:19.912Z

Learnt from: adamoutler
Repo: jokob-sk/NetAlertX PR: 1184
File: .devcontainer/Dockerfile:18-19
Timestamp: 2025-09-20T03:01:19.912Z
Learning: In the NetAlertX repository, .devcontainer/Dockerfile is auto-generated and should not be reviewed directly. Review comments about dependencies and build steps should be directed at the root Dockerfile where the actual source commands are located.

Applied to files:

• .devcontainer/devcontainer.json
• .devcontainer/Dockerfile

📚 Learning: 2025-09-20T14:13:33.635Z

Learnt from: adamoutler
Repo: jokob-sk/NetAlertX PR: 1184
File: .devcontainer/Dockerfile:11-16
Timestamp: 2025-09-20T14:13:33.635Z
Learning: In the NetAlertX repository with Alpine 3.22 base image, the `python -m venv` command works correctly in the devcontainer setup, likely due to symlink creation in the root Dockerfile that makes `python` available as an alias to `python3`.

Applied to files:

• .devcontainer/devcontainer.json
• .devcontainer/Dockerfile

📚 Learning: 2025-09-20T02:56:24.501Z

Learnt from: adamoutler
Repo: jokob-sk/NetAlertX PR: 1184
File: .devcontainer/devcontainer.json:5-8
Timestamp: 2025-09-20T02:56:24.501Z
Learning: In the NetAlertX devcontainer setup, the final .devcontainer/Dockerfile is generated by combining the root Dockerfile with .devcontainer/resources/devcontainer-Dockerfile using the generate-dockerfile.sh script. The devcontainer.json should reference the generated file, not the root Dockerfile.

Applied to files:

• .devcontainer/Dockerfile

📚 Learning: 2025-09-20T14:08:44.152Z

Learnt from: adamoutler
Repo: jokob-sk/NetAlertX PR: 1184
File: .devcontainer/Dockerfile:82-92
Timestamp: 2025-09-20T14:08:44.152Z
Learning: In devcontainer builds, source repository files are not available during the Docker build phase. The source code gets mounted into the container after it's built and started, so COPY commands referencing source files will fail. Configuration files need to be handled at runtime (e.g., in setup scripts) rather than during the build stage.

Applied to files:

• .devcontainer/Dockerfile

📚 Learning: 2025-11-24T00:56:58.733Z

Learnt from: adamoutler
Repo: jokob-sk/NetAlertX PR: 1304
File: .hadolint.yaml:1-2
Timestamp: 2025-11-24T00:56:58.733Z
Learning: In the NetAlertX repository, the .hadolint.yaml config file is intentionally configured to only globally ignore DL3018 (Alpine package pinning). Rules DL3006 (explicit image tagging) and SC2114 (deleting system directories) are handled via inline `# hadolint ignore` directives in specific Dockerfiles where needed, rather than being globally ignored, to ensure new Dockerfiles are still checked for these rules.

Applied to files:

• .devcontainer/Dockerfile

📚 Learning: 2025-09-20T14:09:29.159Z

Learnt from: adamoutler
Repo: jokob-sk/NetAlertX PR: 1184
File: .devcontainer/scripts/setup.sh:103-116
Timestamp: 2025-09-20T14:09:29.159Z
Learning: In NetAlertX devcontainer setup, the netalertx user has write permissions to /var/log/nginx/ directory as it's explicitly chowned to netalertx:www-data in the Dockerfile, so setup.sh can write to nginx log files without sudo.

Applied to files:

• .devcontainer/Dockerfile

📚 Learning: 2025-10-26T17:09:18.621Z

Learnt from: adamoutler
Repo: jokob-sk/NetAlertX PR: 1235
File: .devcontainer/scripts/setup.sh:146-148
Timestamp: 2025-10-26T17:09:18.621Z
Learning: In `.devcontainer/scripts/setup.sh` and other devcontainer setup scripts for NetAlertX, chmod 666 on /var/run/docker.sock is acceptable because devcontainer environments are single-user development contexts where convenience can take priority over strict permission hardening.

Applied to files:

• .devcontainer/Dockerfile

📚 Learning: 2025-09-20T14:08:48.256Z

Learnt from: adamoutler
Repo: jokob-sk/NetAlertX PR: 1184
File: .devcontainer/scripts/setup.sh:90-96
Timestamp: 2025-09-20T14:08:48.256Z
Learning: In the NetAlertX devcontainer setup, the setup.sh script intentionally removes user_notifications.json from the API directory during development environment initialization to prevent notification clutter that accumulates during container launches and development work.

Applied to files:

• .devcontainer/Dockerfile

📚 Learning: 2025-09-20T14:13:33.635Z

Learnt from: adamoutler
Repo: jokob-sk/NetAlertX PR: 1184
File: .devcontainer/Dockerfile:11-16
Timestamp: 2025-09-20T14:13:33.635Z
Learning: In the NetAlertX devcontainer setup, the `python -m venv /opt/venv` command works successfully on Alpine 3.22 despite the typical Alpine behavior of not providing a /usr/bin/python symlink by default. The build completes successfully and pytest runs without issues.

Applied to files:

• .devcontainer/Dockerfile

🔇 Additional comments (1)

.devcontainer/Dockerfile (1)

1-312: Note: This file is auto-generated.

As noted in the file header and per project conventions, .devcontainer/Dockerfile is auto-generated by .devcontainer/scripts/generate-configs.sh from the root Dockerfile and .devcontainer/resources/devcontainer-Dockerfile.

The chromium packages added at line 284 should be reviewed in their source location (likely .devcontainer/resources/devcontainer-Dockerfile).

Based on learnings.