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?
It seems like you've got this under control, if you want help or have specific questions, let me know what I can do for you!
#### About Dosu
This response is meant to be useful and save you time. It is **not meant to be a precise solution**, but rather a starting point for your own research.
Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.
If you want to continue the conversation, start your reply with @dosu-bot.
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?
Have you read the Code of Conduct?