Proposal: Streamlining Deployments on Akash Network from GitHub/GitLab/Bitbucket [Phase 2]

[HoomanDgtl]

Background

Following the success of Phase 1, which introduced automatic deployments for popular JavaScript frameworks from GitHub onto Akash, we aim to expand the network's capabilities. Phase 2 will position Akash to offer more streamlined deployment options comparable to competitors like Vercel and Netlify. This phase focuses on supporting additional frameworks, making deployment accessible to developers using Go, Python, Ruby, and WordPress.

Current Achievements (Phase 1 Recap)

Phase 1 successfully provided developers with a seamless, automated deployment experience similar to Vercel. It supports deploying applications from GitHub, GitLab, and BitBucket repositories directly onto the Akash Network.

Frameworks Currently Supported:

• JavaScript Frameworks: React, Vue.js, Next.js, Angular, Ember.js
• Static Site Generators: Gatsby.js, Nuxt.js, Astro, VitePress, 11ty.js
• Full-stack Frameworks: Remix, Vite, Express.js

Phase 1 Implementation Details:

• PR merged: feature: Enable Deployment from Git Repositories to Akash Network console#417
• Proposal: https://www.mintscan.io/akash/proposals/258/
• Current Status: Live at click here

The console's launch has already simplified deployment for hundreds of developers, creating a strong foundation for expansion.

Phase 2 Objective

Our goal is to expand support to new technology stacks, including Go frameworks, Python frameworks, Ruby on Rails, and WordPress. This expansion will attract a wider range of developers and projects, enhancing the Akash Network's utility and appeal.

Proposed New Features

1. Go Web Frameworks

   • Gin
   • Echo
   • Beego
   • Buffalo
   • Fiber

2. Python Frameworks

   • Django
   • Flask
   • FastAPI

3. Ruby Framework

   • Ruby on Rails

4. CMS Platform

   • WordPress

Implementation Plan

1. Framework Analysis & Integration

• Research Build Requirements
• Environment Setup
• Automation Development
• CI/CD Configuration

2. Testing & Quality Assurance

• Comprehensive test suite development
• Security testing
• Cross-platform compatibility validation

3. Documentation & User Support

• Technical documentation for all frameworks
• User guides and tutorials
• Best practices and troubleshooting guides

4. GUI Integration

• Console interface updates
• Streamlined framework selection
• Enhanced user feedback mechanisms

Detailed Timeline

Month 1: Framework Analysis & Initial Development

Week 1-2

• Project infrastructure setup
• Go frameworks integration (Gin, Echo)
• Python frameworks research
• Testing environment configuration
• Beego and Fiber implementation
• Docker configurations for FastAPI and Django

Week 3-4

• Ruby on Rails integration
• WordPress deployment templates
• Initial framework testing
• Complete Go framework integration
• Django and FastAPI deployment finalization
• Console UI design drafting

Month 2: Integration Completion & Testing

Week 5-6

• Python framework integration completion
• Performance testing
• Ruby on Rails automation testing
• WordPress compatibility testing
• Security assessments

Week 7-8

• Cross-framework integration testing
• Pipeline optimization
• Final integration testing
• Compatibility validation

Month 3: Documentation, Console Integration & Launch

Week 9-10

• Technical documentation writing
• User guide creation
• Console interface updates
• Tutorial development

Week 11-12

• UI/UX updates and integration completion
• Security and performance testing
• Quality assurance
• Launch and feedback collection

Budget Breakdown

1. Development & Integration

Go Frameworks: $13,000 (130 hrs)

• Framework setup: 50 hrs
• Scalable shell script: 20 hrs
• Feature development: 40 hrs
• Debugging & optimization: 20 hrs

Python Frameworks: $12,500 (125 hrs)

• Framework setup: 45 hrs
• Scalable shell script: 20 hrs
• API integration: 40 hrs
• Unit testing: 20 hrs

Ruby on Rails: $9,000 (90 hrs)

• Backend development: 30 hrs
• Scalable shell script: 20 hrs
• Database integration: 20 hrs
• Deployment testing: 20 hrs

WordPress: $8,500 (85 hrs)

• Theme customization: 20 hrs
• Scalable shell script: 20 hrs
• Plugin development: 25 hrs
• Content migration: 20 hrs

2. Documentation & Console Integration

Technical Documentation: $8,000 (80 hrs)

• Akash docs updates: 40 hrs
• Framework guides: 20 hrs
• Developer notes: 20 hrs

UI Updates & Integration: $5,000 (50 hrs)

• UI design revisions: 20 hrs
• Console integration: 30 hrs

Tutorials: $4,000 (40 hrs)

• Guide creation: 30 hrs
• Tutorial videos: 10 hrs

3. Quality Assurance

Testing: $6,000 (60 hrs)

• Manual testing: 30 hrs
• Automated testing: 20 hrs
• Cross-environment testing: 10 hrs

Deployment Optimization: $4,000 (40 hrs)

• Deployment scripts: 20 hrs
• Performance tuning: 20 hrs

Total Breakdown

• Development & Integration: $43,000 (430 hrs)
• Documentation & UI Enhancements: $17,000 (170 hrs)
• Quality Assurance: $10,000 (100 hrs)

Grand Total: $70,000

Benefits

1. Expanded User Base

   • Support for Go, Python, Ruby, and WordPress
   • Broader developer attraction
   • Increased project diversity

2. Enhanced Versatility

   • Support for diverse use cases
   • Comprehensive framework coverage
   • Improved deployment options

3. Competitive Advantage

   • Feature parity with centralized platforms
   • Unique decentralized benefits
   • Enhanced developer experience

Phase 2 will establish Akash Network as a comprehensive platform for decentralized deployments, offering developers across various ecosystems a powerful, versatile solution for their deployment needs.

[rodri-r]

Thanks for sharing. Looks interesting. I have one doubt though:

You mention Console Integration, yet you also mention UI design.

Not sure if this will be a different UI/platform or/and if it will be merged into Console somehow?

[HoomanDgtl]

Hi @rodri-r,

Thank you for reviewing the proposal!

Yes, it will indeed be implemented directly on the console. By "UI design and integration," we mean building and configuring the pipeline within the console, which will require some adjustments and careful integration into the 'deployment from VCS' feature. This feature recently went live on the console as part of the Phase 1 implementation.

I hope this addresses your questions.

Thanks!

[piber-dev]

hello @HoomanDgtl - thanks for writing this proposal! phase 1 of this proposal was truly a great addition to console. is there a repository we can take a look at to see the previous integration clearly, or is it just the PR with dozens of commits? for the documentation/content creation, is it possible to get this approved to be paid out by the community bounties budget? i feel like $12000 total and $100/hr for docs and videos is a lot when there is no marketing involved in this budget. there are plenty of users able to do it for $30/hr through different special interest and working groups.

[HoomanDgtl]

yes sure @piber-dev

here are the details:

1. PR merged into console (this is for 'frontend + Oauth' execution): feature: Enable Deployment from Git Repositories to Akash Network console#417
2. Infra PR (migrated everything to Akash controlled docker, this is the backend that is handling everything): console js/ts build and deploy scripts and workflow awesome-akash#614
3. Current Status: Live at click here

There is no dedicated repository as the implementation has been done directly on the console repo, Pr has been shared above.

thanks

[baktun14]

Hey guys, thanks for putting up this proposal.

Quick questions:

1. Has there been any feedback from users in phase 1? Ideally we would like to have some in order to properly priotize and plan how to improve this feature.
2. How did you come up with the list of frameworks/languages to add in this proposal? Do we need to do them all at once?
3. How did you come up with 100$ hourly rate? I think this rate is high and also I agree with @piber-dev, it shouldn't be the same rate for all the tasks that you plan on doing.

Thanks

[HoomanDgtl]

1. We have received some positive feedback from community members on Discord, and this has become one of the most highlighted features in the console. Streamlining deployment to Akash directly from GitHub offers immense benefits in terms of usage, growth, and developer exposure. This can further be validated by the evident popularity of competitors like Netlify, render and Vercel.

2. We studied competitors and recent programming trends to determine which languages to support (open to more suggestions). Python and Go have emerged as highly demanded languages due to the boom in AI agent wrapper development. Additionally, WordPress is widely utilized because of its extensive library support across multiple areas. We have already established the foundation and achieved success with the initial version, which was the most challenging part. Implementing the proposed enhancements should not pose any issues. At this point, splitting the proposal further would only lead to unnecessary delays and multiple on-chain proposals, especially since we have already demonstrated our expertise in Phase 1 of the deployment.

3. Regarding the budget, I would like to emphasize that an initiative of this scope requires a comprehensive approach, involving extensive ideation and thoughtful implementation tailored to Akash's unique decentralized infrastructure. A 100 usd/hr cost is a reasonable and mid-standard ask for such an implementation, as it involves a combination of multiple skills aimed at delivering production-level, high-quality results, rather than quick prototypes.

We are open to further feedback on this.

[cloud-j-luna]

Thank you for submitting this proposal, it's getting interesting 👍🏻

Couple questions I have:

1. Have you considered to put effort in developing a way to add further support to languages/technologies in the future instead of adding them as part of proposals? This way it would avoid the need to open new proposals to support new tech stacks. Tech stacks could then be added more easily by the community and funded by bounties reducing the time-to-market. With ~330 hours you proposed for integrating new languages/technologies I believe you’ll be able to develop a way to import these with minimal effort, enhancing the feature’s delivery rate. It could also reduce monopolisation over this process.

2. I had questions regarding the proposed rates but these were already asked so I’ll keep an eye on those threads.

3. Regarding documentation/video tutorials. These can be scoped to other SIGs (with exception of technical documentation which makes sense to be as part of the development). Currently there are existing initiatives to develop video content for Akash Console related features/usage, which could be extended to include this as part of that existing budget and process to optimize resources.

4. I see you propose spending more time manual testing than developing automated testing. I believe a big portion of this should be assigned to quality automated testing because I don’t expect you to be manually testing these for regressions in future releases.

5. UI Updates & Integration: $5,000 (50 hrs)


   What specifically do these include? Is there really a need for further integrations? Isn’t this feature already fully integrated? What is missing?