personal-projects/personal-portfolio
Template
1
1
Fork 0
Code Issues 3 Pull Requests Actions Packages Projects 1 Releases Wiki Activity

Add Makefile targets for operational scripts #86

New Issue
Closed
opened 2026-01-17 21:53:47 +00:00 by lmiranda · 0 comments
lmiranda commented 2026-01-17 21:53:47 +00:00
Owner
Copy Link

Overview

Add convenient Makefile targets that wrap the new operational scripts.

Acceptance Criteria

  • Add make logs target that runs scripts/logs.sh
  • Add make run-detached target that runs scripts/run-detached.sh
  • Add make etl-toronto target that runs scripts/etl/toronto.sh
  • Include phony declarations for new targets
  • Add helpful comments/descriptions for each target

Technical Notes

Add to Makefile:

.PHONY: logs run-detached etl-toronto

## Follow docker compose logs (optionally: make logs SERVICE=web)
logs:
	./scripts/logs.sh $(SERVICE)

## Start services in detached mode with health check
run-detached:
	./scripts/run-detached.sh

## Run Toronto ETL pipeline (optionally: make etl-toronto MODE=--full)
etl-toronto:
	./scripts/etl/toronto.sh $(MODE)

Labels

  • Type/Chore
  • Priority/Medium
  • Complexity/Simple
  • Component/Infra

Phase: 3 - Operational Scripts

## Overview Add convenient Makefile targets that wrap the new operational scripts. ## Acceptance Criteria - [ ] Add `make logs` target that runs `scripts/logs.sh` - [ ] Add `make run-detached` target that runs `scripts/run-detached.sh` - [ ] Add `make etl-toronto` target that runs `scripts/etl/toronto.sh` - [ ] Include phony declarations for new targets - [ ] Add helpful comments/descriptions for each target ## Technical Notes Add to Makefile: ```makefile .PHONY: logs run-detached etl-toronto ## Follow docker compose logs (optionally: make logs SERVICE=web) logs: ./scripts/logs.sh $(SERVICE) ## Start services in detached mode with health check run-detached: ./scripts/run-detached.sh ## Run Toronto ETL pipeline (optionally: make etl-toronto MODE=--full) etl-toronto: ./scripts/etl/toronto.sh $(MODE) ``` ## Labels - Type/Chore - Priority/Medium - Complexity/Simple - Component/Infra ## Phase: 3 - Operational Scripts
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Complexity/Complex
High uncertainty or many dependencies
 Complexity/Medium
Some unknowns or dependencies
 Complexity/Simple
Straightforward, well-understood
 Effort/L
3-5 days
 Effort/M
1-2 days
 Effort/S
2-4 hours
 Effort/XL
> 1 week
 Effort/XS
< 2 hours
 Priority/Critical
Immediate attention required
 Priority/High
Important, needs attention soon
 Priority/Low
Nice to have, can wait
 Priority/Medium
Normal priority
 Type/Bug
Something isn't working
 Type/Chore
Maintenance tasks
 Type/Documentation
Documentation improvements
 Type/Feature
New feature or request
 Type/Refactor
Code refactoring without changing behavior
 Type/Test
Testing related
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
lmiranda
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: personal-projects/personal-portfolio#86
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?