Skip to content

Commit 3a2c4b6

Browse files
committed
feat: [#28] Infrastructure preparation for Phase 4.7 staging deployment
- Rename hetzner.env to hetzner-staging.env for staging account isolation - Fix markdownlint MD013 line-length violations in documentation - Ensure all CI tests pass before staging deployment execution Addresses staging environment preparation requirements for Issue #28 Phase 4.7 implementation with proper account separation.
1 parent cdb7476 commit 3a2c4b6

File tree

5 files changed

+16
-6
lines changed

5 files changed

+16
-6
lines changed

.yamllint-ci.yml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,7 @@ extends: default
22

33
ignore: |
44
application/storage/
5+
application/config
56
67
rules:
78
line-length:

Makefile

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,9 @@
1313
ENVIRONMENT_TYPE ?= development
1414
ENVIRONMENT_FILE ?= development-libvirt
1515

16+
# Test directories
17+
INFRA_TESTS_DIR = infrastructure/tests
18+
1619
# Default target - show help when no target specified
1720
.DEFAULT_GOAL := help
1821

docs/guides/staging-deployment-testing-guide.md

Lines changed: 8 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,13 @@
11
# Staging Deployment Testing Guide
22

3-
**Purpose**: Manual testing of staging environment deployments on remote cloud providers to validate functionality before production deployment.
3+
**Purpose**: Manual testing of staging environment deployments on remote cloud
4+
providers to validate functionality before production deployment.
45

56
## Overview
67

7-
This guide provides a comprehensive template for manually testing staging deployments. Staging environment testing offers unique advantages over local development and E2E testing:
8+
This guide provides a comprehensive template for manually testing staging
9+
deployments. Staging environment testing offers unique advantages over local
10+
development and E2E testing:
811

912
### Benefits of Staging Testing
1013

@@ -507,4 +510,6 @@ After successful staging testing:
507510

508511
---
509512

510-
**Note**: This guide provides a comprehensive template for staging deployment testing. For specific test session tracking, use the session documentation template in `docs/testing/manual-sessions/`.
513+
**Note**: This guide provides a comprehensive template for staging deployment
514+
testing. For specific test session tracking, use the session documentation
515+
template in `docs/testing/manual-sessions/`.

docs/testing/manual-sessions/2025-01-08-issue-28-phase-4-7-staging.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,10 +9,12 @@
99

1010
## Session Overview
1111

12-
**Objective**: Complete Issue #28 Phase 4.7 manual deployment testing for staging environment
12+
**Objective**: Complete Issue #28 Phase 4.7 manual deployment testing for
13+
staging environment
1314
**Duration**: In progress
1415
**Status**: PENDING - Ready to Execute
15-
**Documentation Reference**: [Issue #28](../../issues/28-phase-4-hetzner-infrastructure-implementation.md)
16+
**Documentation Reference**:
17+
[Issue #28](../../issues/28-phase-4-hetzner-infrastructure-implementation.md)
1618
Phase 4.7
1719

1820
## Context

infrastructure/config/templates/application/prometheus.yml.tpl

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,4 +31,3 @@ scrape_configs:
3131
params:
3232
token: ['${TRACKER_ADMIN_TOKEN}']
3333
format: ['prometheus']
34-

0 commit comments

Comments
 (0)