chipling commited on
Commit
94c6c7e
·
verified ·
1 Parent(s): 261e135

Update README.md

Browse files
Files changed (1) hide show
  1. README.md +8 -141
README.md CHANGED
@@ -1,141 +1,8 @@
1
- # FastHost
2
-
3
- **FastHost** is an open-source, self-hosted deployment platform for Python backend apps. Think of it as your own Vercel or Replit, but tailored for FastAPI and Flask using Docker.
4
-
5
- With FastHost, you can upload a `.py` file or project archive and instantly deploy it as a running Docker container on your own machine. It’s perfect for developers, tinkerers, and teams who want full control over their Python backend deployments—no third-party cloud required.
6
-
7
- ---
8
-
9
- 🚧 **FastHost is in active development!**
10
- We welcome contributions, feedback, and ideas from the community. If you’d like to help shape FastHost, check out the issues, open a pull request, or start a discussion.
11
-
12
- #Roadmap:
13
- Phase 1: Core Deployment & Developer Experience (MVP)
14
- Goal: Establish a stable and user-friendly platform for deploying FastAPI/Flask applications via Git, with essential management tools.
15
-
16
- 1.1 Git-based Deployments (High Priority):
17
-
18
- Feature: Implement integration with Git providers (GitHub, GitLab, Bitbucket) to allow users to connect repositories.
19
-
20
- Value: Automates deployments on git push, significantly improving developer workflow and replacing manual zip uploads.
21
-
22
- Implementation: Webhooks from Git providers, repository cloning, branch selection for deployment.
23
-
24
- 1.2 Automated SSL/TLS with Custom Domains (High Priority):
25
-
26
- Feature: Allow users to add custom domains and automatically provision/renew SSL certificates using Let's Encrypt.
27
-
28
- Value: Essential for production-ready applications, building trust, and a professional appearance.
29
-
30
- Implementation: DNS validation (e.g., CNAME/TXT record instructions), ACME client integration.
31
-
32
- 1.3 Environment Variables Management:
33
-
34
- Feature: A secure UI for users to define, update, and manage environment variables for their deployed applications.
35
-
36
- Value: Separates configuration from code, crucial for different environments (dev, staging, prod) and sensitive data.
37
-
38
- Implementation: Encrypted storage of variables, injection into Docker builds/containers.
39
-
40
- 1.4 Real-time Build & Deployment Logs:
41
-
42
- Feature: Stream stdout/stderr from the build process (Docker build, dependencies installation) and deployment steps directly to the user interface.
43
-
44
- Value: Provides transparency, enabling users to debug issues during the deployment cycle.
45
-
46
- Implementation: WebSockets or SSE for log streaming.
47
-
48
- 1.5 Basic User Authentication & Project Management:
49
-
50
- Feature: Implement a secure user registration and login system. Allow users to create and manage their deployment projects.
51
-
52
- Value: Enables multi-user access and organization within the self-hosted instance.
53
-
54
- Implementation: Database for users/projects, secure password hashing, session management.
55
-
56
- Phase 2: Reliability, Observability & Scalability
57
- Goal: Enhance the platform's stability, provide critical insights into running applications, and lay the groundwork for horizontal scaling.
58
-
59
- 2.1 Application Logging & Monitoring Dashboard:
60
-
61
- Feature: Centralized access to logs generated by the running FastAPI/Flask applications (e.g., from main.py). Implement basic metrics (CPU, memory, request counts).
62
-
63
- Value: Indispensable for debugging live applications, identifying performance bottlenecks, and understanding usage patterns.
64
-
65
- Implementation: Log aggregation (e.g., filebeat, fluentd, or direct container logs), Prometheus/Grafana or simpler in-house graphing.
66
-
67
- 2.2 Deployment Rollbacks:
68
-
69
- Feature: Allow users to revert a deployed application to any previous successful deployment version.
70
-
71
- Value: A critical safety net for recovering quickly from bad deployments or unintended side effects.
72
-
73
- Implementation: Maintain historical Docker image references/tags for each deployment.
74
-
75
- 2.3 Horizontal Scaling (Basic):
76
-
77
- Feature: Enable users to define and run multiple instances of a single application.
78
-
79
- Value: Improves application availability and performance under increased load.
80
-
81
- Implementation: Integrate with NGINX (or similar) as a load balancer to distribute traffic to multiple Docker containers/instances. UI to adjust instance count.
82
-
83
- 2.4 Improved Error Handling & Notifications:
84
-
85
- Feature: Clear, actionable error messages in the UI for failed builds/deployments. Implement email or webhook notifications for critical events.
86
-
87
- Value: Reduces user frustration and keeps them informed about the status of their deployments.
88
-
89
- Phase 3: Advanced Features & Ecosystem Expansion
90
- Goal: Differentiate the platform with powerful capabilities, offering greater flexibility and catering to more complex use cases.
91
-
92
- 3.1 Persistent Storage Integration:
93
-
94
- Feature: Provide options for attaching persistent storage volumes to applications for data that needs to survive deployments (e.g., user uploads, database files).
95
-
96
- Value: Enables stateful applications, broadening the types of projects the platform can host.
97
-
98
- Implementation: Docker volumes, bind mounts, or integration with network storage solutions if applicable to the underlying infrastructure.
99
-
100
- 3.2 Custom Buildpacks/Build Steps:
101
-
102
- Feature: Allow users to define more custom build processes beyond just a Dockerfile, perhaps through a platform.yml or similar configuration.
103
-
104
- Value: Offers greater flexibility for non-standard build requirements or specialized runtimes.
105
-
106
- Implementation: Extend the build orchestration to support custom scripts or logic.
107
-
108
- 3.3 Serverless Function (Python) Support:
109
-
110
- Feature: Enable users to deploy individual Python functions as serverless endpoints without managing a full application server.
111
-
112
- Value: Caters to microservices architectures, background tasks, and event-driven workloads, similar to AWS Lambda or Google Cloud Functions.
113
-
114
- Implementation: Custom runtime environment for functions, API Gateway integration.
115
-
116
- 3.4 CLI Tool:
117
-
118
- Feature: Develop a command-line interface (CLI) for interacting with the platform (deploying, checking status, viewing logs).
119
-
120
- Value: Appeals to developers who prefer terminal-based workflows, enabling scripting and automation.
121
-
122
- Implementation: Python CLI with API calls to your platform's backend.
123
-
124
- 3.5 Webhooks for Deployment Events:
125
-
126
- Feature: Allow users to configure webhooks that trigger on deployment success, failure, or other lifecycle events.
127
-
128
- Value: Enables integration with external services (e.g., Slack notifications, CI/CD pipelines).
129
-
130
- 3.6 Comprehensive Documentation & Community:
131
-
132
- Feature: Create extensive documentation covering setup, usage, troubleshooting, and API. Foster a community around the open-source project.
133
-
134
- Value: Crucial for adoption and self-sufficiency, reducing support burden.
135
-
136
- **Contribute:**
137
- - Fork the repository
138
- - Create a feature branch
139
- - Submit a pull request
140
-
141
- Let’s build the future of Python app deployment together!
 
1
+ title: {{title}}
2
+ emoji: {{emoji}}
3
+ colorFrom: {{colorFrom}}
4
+ colorTo: {{colorTo}}
5
+ sdk: {{sdk}}
6
+ sdk_version: "{{sdkVersion}}"
7
+ app_file: app.py
8
+ pinned: false