Cloud platform integration

Abierto
#1,065 0 comentarios 0 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
20/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
github-actions, python
Área
cloud, devops

Línea de trabajo

Start by reviewing the proposed GitHub Actions workflow inputs and the ASGI application deployment flow described in the issue. Clarify the cloud service, usage-based billing, deployment behavior, and admin portal requirements before implementation; done would include publishing an application and exposing its app name, resources, and cost.

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

Descripción

flag-profit priority-2-moderate type-ci
Current Situation

We have no convenient way of integrating with cloud platforms.

Proposed Actions

We should consider providing auto-configuring ReactPy as a paid cloud service. To oversimplify the design:

  1. The user will pay a usage based hosting fee
  2. We will develop GitHub actions workflow that publish a ReactPy application to the cloud
  3. The GitHub actions workflow will need the following info
    • cwd_dir : The cwd directory for us to cd into before executing commands.
    • application_path: The dotted path to my.asgi:application, which is directly provided to an ASGI webserver we auto-configure.
    • site_api_key: Unique key that tells us what user account (and site tied to the user) is being published
    • app_name: Name of the app. The user will be able to view their published apps within an admin portal, and see resources/cost for each app. If a user attempts to deploy an app with the same name as an existing one, we will overwrite the existing app.
Lenguaje dominante
Python
Estrellas
8.1k
Forks
332
Sin PR fusionados en 30 d

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

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 reactive-python/reactpy

Todos los issues de reactive-python/reactpy

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.