Cloud platform integration

Open
#1,065 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
github-actions, python
Domain
cloud, devops

Research direction

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.

Written by the indexing model from the issue text.

Description

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.
Dominant language
Python
Stars
8.1k
Forks
332
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from reactive-python/reactpy

All issues in reactive-python/reactpy

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.