flyteorg/flyte

[Core feature] Simplify the local development environment for flyteconsole

Open

#5,099 opened on Mar 25, 2024

View on GitHub
 (6 comments) (1 reaction) (1 assignee)Python (378 forks)batch import
backloggeddocumentationenhancementgood first issuehacktoberfestui

Repository metrics

Stars
 (3,705 stars)
PR merge metrics
 (Avg merge 3d 8h) (116 merged PRs in 30d)

Description

Motivation: Why do you think this is important?

The setup guide of flyteconsole says that we need to generate an SSL certificate and set domain name routing rules in /etc/hosts, which is way too complex for frontend development. For the frontend development, we don't need SSL because we can use HTTP instead of HTTPS. We don't need a custom domain name except that the backend has the multi-tenancy feature. However, as far as I know, Flyte does not have the multi-tenancy feature now.

Goal: What should the final outcome look like, ideally?

Simplify the local development environment for flyteconsole to remove SSL and domain name related stuffs.

Describe alternatives you've considered

N/A

Propose: Link/Inline OR Additional context

No response

Are you sure this issue hasn't been raised already?

  • Yes

Have you read the Code of Conduct?

  • Yes

Contributor guide

Research direction
Review the current setup guide for flyteconsole, identify SSL and domain name configuration steps, and propose changes to use HTTP and remove custom domain requirements.
Tech stack
None
Domain
frontend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75