Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Improve beginner experience on free tier

Abierto
  • ¿Algo no está bien?
#17 5 comentarios 3 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
38/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
django, python
Área
cloud, devops, tooling

Línea de trabajo

No se indican archivos, pruebas ni puntos de entrada. Empieza por localizar el comando de despliegue y la integración con PythonAnywhere; después, determina cómo representaría una opción --free-tier las tres restricciones indicadas y cómo emitiría advertencias. Se considera terminado cuando el alcance y el comportamiento de las comprobaciones previas al despliegue estén definidos y cubiertos por pruebas adecuadas.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

While working with PythonAnywhere during the Djangonaut Space program, I identified several constraints in the free tier that can introduce friction for first-time Django deployments.

The primary issue is not the limitations themselves, but that they are often only discovered at runtime, making it difficult for users to distinguish between platform constraints and application-level misconfiguration.

Deployment Issues Identified

1. Custom domains are not supported

Many deployment guides assume the ability to configure a custom domain (e.g. myapp.com) via DNS. On the free tier, applications are restricted to the default *.pythonanywhere.com subdomain.

Impact:
Users may attempt DNS configuration and interpret the failure as incorrect DNS records, SSL misconfiguration, or application routing issues, rather than a platform limitation.

2. Restricted outbound network access

Applications that depend on outbound HTTP requests (e.g. third-party APIs) may fail or behave inconsistently due to network restrictions on the free tier.

Impact:
From the application perspective, these failures can resemble standard runtime errors (timeouts, connection errors), making it non-obvious that the root cause is environment-level network policy rather than application logic.

3. No support for persistent background workers

Free tier environments do not support always-on processes (e.g. Celery workers, long-running jobs, or persistent task queues).

Impact:
Functionality that depends on asynchronous or background execution may not run as expected after deployment, even if it works correctly in a local development environment. Failures are often silent or indirect, making diagnosis difficult for new users.

Proposed Direction (Tooling Integration)

As part of my work with Django Simple Deploy, I’ve been exploring a mechanism to surface these constraints earlier in the deployment process.

The idea is to introduce a --free-tier flag that:

  • Detects or assumes a constrained hosting environment
  • Performs pre-deployment checks against known platform limitations
  • Emits warnings for unsupported or restricted features

Example warnings:

  • “Custom domain configuration is not supported on the free tier; default subdomain will be used.”
  • “Outbound network access may be restricted; external API calls could fail at runtime.”
  • “Persistent background workers are not available; asynchronous tasks may not execute.”

This approach helps catch potential issues before deployment instead of at runtime, making things clearer and easier to debug, especially for beginners. I’d be interested to hear your thoughts on this.

Lenguaje dominante
Python
Estrellas
10
Forks
5
Sin PR fusionados en 30 d

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de caktus/dsd-pythonanywhere

Todos los issues de caktus/dsd-pythonanywhere

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.