homelab-optimized/docs/services/individual/pi.alert.md

Pi.Alert

🟢 Other Service

📋 Service Overview

Property	Value
Service Name	pi.alert
Host	anubis
Category	Other
Difficulty	🟢
Docker Image	jokobsk/pi.alert:latest
Compose File	anubis/pialert.yml
Directory	anubis

🎯 Purpose

pi.alert is a specialized service that provides specific functionality for the homelab infrastructure.

🚀 Quick Start

Prerequisites

• Docker and Docker Compose installed
• Basic understanding of REDACTED_APP_PASSWORD
• Access to the host system (anubis)

Deployment

# Navigate to service directory
cd anubis

# Start the service
docker-compose up -d

# Check service status
docker-compose ps

# View logs
docker-compose logs -f pi.alert

🔧 Configuration

Docker Compose Configuration

container_name: Pi.Alert
cpu_shares: 768
environment:
  PORT: 17811
  TZ: America/Los_Angeles
healthcheck:
  test: curl -f http://localhost:17811/ || exit 1
image: jokobsk/pi.alert:latest
mem_limit: 2g
network_mode: host
restart: on-failure:5
security_opt:
- no-new-privileges:true
volumes:
- /home/vish/docker/pialert/config:/home/pi/pialert/config:rw
- /home/vish/docker/pialert/db:/home/pi/pialert/db:rw
- /home/vish/docker/pialert/logs:/home/pi/pialert/front/log:rw

Environment Variables

Variable	Value	Description
TZ	America/Los_Angeles	Timezone setting
PORT	17811	Configuration variable

Port Mappings

No ports exposed.

Volume Mappings

Host Path	Container Path	Type	Purpose
/home/vish/docker/pialert/config	/home/pi/pialert/config	bind	Configuration files
/home/vish/docker/pialert/db	/home/pi/pialert/db	bind	Database files
/home/vish/docker/pialert/logs	/home/pi/pialert/front/log	bind	Data storage

🌐 Access Information

This service does not expose any web interfaces.

🔒 Security Considerations

• ✅ Security options configured
• ⚠️ Consider running as non-root user

📊 Resource Requirements

No resource limits configured

Recommended Resources

• Minimum RAM: 512MB
• Recommended RAM: 1GB+
• CPU: 1 core minimum
• Storage: Varies by usage

Resource Monitoring

Monitor resource usage with:

docker stats

🔍 Health Monitoring

✅ Health check configured Test Command: curl -f http://localhost:17811/ || exit 1

Manual Health Checks

# Check container health
docker inspect --format='{{.State.Health.Status}}' CONTAINER_NAME

# View health check logs
docker inspect --format='{{range .State.Health.Log}}{{.Output}}{{end}}' CONTAINER_NAME

🚨 Troubleshooting

Common Issues

Service won't start

• Check Docker logs: docker-compose logs service-name
• Verify port availability: netstat -tulpn | grep PORT
• Check file permissions on mounted volumes

Can't access web interface

• Verify service is running: docker-compose ps
• Check firewall settings
• Confirm correct port mapping

Performance issues

• Monitor resource usage: docker stats
• Check available disk space: df -h
• Review service logs for errors

Useful Commands

# Check service status
docker-compose ps

# View real-time logs
docker-compose logs -f pi.alert

# Restart service
docker-compose restart pi.alert

# Update service
docker-compose pull pi.alert
docker-compose up -d pi.alert

# Access service shell
docker-compose exec pi.alert /bin/bash
# or
docker-compose exec pi.alert /bin/sh

📚 Additional Resources

• Official Documentation: Check the official docs for pi.alert
• Docker Hub: jokobsk/pi.alert:latest
• Community Forums: Search for community discussions and solutions
• GitHub Issues: Check the project's GitHub for known issues

🔗 Related Services

Other services in the other category on anubis

---

This documentation is auto-generated from the Docker Compose configuration. For the most up-to-date information, refer to the official documentation and the actual compose file.

Last Updated: 2025-11-17
Configuration Source: anubis/pialert.yml