cdk-django
copilot-cli
cdk-django | copilot-cli | |
---|---|---|
10 | 51 | |
46 | 3,332 | |
- | 1.1% | |
5.1 | 9.5 | |
6 days ago | 6 days ago | |
TypeScript | Go | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
cdk-django
-
My Infrastructure as Code Rosetta Stone - Deploying the same Django application on AWS ECS Fargate with CDK, Terraform and Pulumi
cdk-django
-
My Infrastructure as Code Rosetta Stone - Deploying the same web application on AWS ECS Fargate with CDK, Terraform and Pulumi
CDK Construct Library: github.com/briancaffey/cdk-django
-
Django AWS CDK deployment
- Another aspect of my approach that I prefer over the other one is using a high-level construct that you publish and then consume in your project. This requires that you write a construct in TypeScript and then publish it to npm or PyPI. I'm working on a construct library for deploying Django apps with CDK called djagno-cdk, and one of the constructs in it uses ECS Fargate: https://github.com/briancaffey/django-cdk/blob/main/src/django-ecs.ts. Ideally you don't have everything in a single construct though, so I like how Mariano is doing that in his project. My Terraform project does a better job at separating layers of the application, so I need to apply that same principle to django-cdk when I get around to working on that project again.
-
My approach to building ad hoc developer environments using AWS ECS, Terraform and GitHub Actions (article link and diagram description in comments)
Sure. My IaC journey actually started out with CloudFormation, and I learned a lot from this reference project: aws-samples/ecs-refarch-cloudformation. Then I picked up CDK when that became available and migrated a project from CloudFormation to CDK. It sounded like a nicer way to handle stacks in a familiar language with lots great one-liners and utility functions and constructs, and it definitely is. I have a similar project written in CDK that is an application/framework-first (Django) approach to learning and doing IaC that you can find here: https://github.com/briancaffey/django-cdk. This implements both ECS and EKS, but my attempts at learning EKS sort of fizzled out for now as I don't have the need to use it, and for the task at hand (running a monolithic Django application on AWS) I think ECS makes a LOT more sense.
-
Basic questions about Django app deployment on AWS
I have an example of doing this here, and I posted about this earlier on this sub https://www.reddit.com/r/django/comments/rj7sj2/deploying_django_applications_to_a_singlenode/
-
Deploying Django applications to a single-node docker swarm cluster on EC2 with AWS Cloud Development Kit (CDK) and GitHub Actions (description, repo links + full article in comments)
I'm not sure what you mean by "architecture", and I'm not sure what is wrong with trying to save money while learning how to do IaC and CI/CD. My thinking is that I can use some of what I learned here in a more robust setup of a Django app that uses ECS, I'm working on that here: https://github.com/briancaffey/django-cdk/blob/main/src/django-ecs.ts.
-
Any examples of custom ecs constructs which builds on the top of ecs patterns
Here is on that Iām working on: https://github.com/briancaffey/django-cdk
-
Ask r/kubernetes: What are you working on this week?
Here's a link to the repo: https://github.com/briancaffey/django-cdk. This library currently offers high level constructs for EKS as well as ECS. I have previously used ECS for most of the containerized web apps I have worked with, so I'm hoping to use this as a way to compare the two orchestration tools for my use case and gather some best practices. This project includes a companion repo that is included as a git submodule that I have been to do live tests/deployments using my construct library.
copilot-cli
-
Use AWS Graviton processors on AWS Fargate with Copilot
AWS Copilot CLI is an open source command line interface for running containers on AWS App Runner, Amazon Elastic Container Service (ECS), and AWS Fargate.
-
AI Chatbot powered by Amazon Bedrock šš¤
sudo curl -Lo /usr/local/bin/copilot https://github.com/aws/copilot-cli/releases/latest/download/copilot-linux && sudo chmod +x /usr/local/bin/copilot
-
Launch HN: Nullstone (YC W22) ā An easier way to deploy and manage cloud apps
Check out AWS Copilot CLI: https://aws.github.io/copilot-cli/
This is by far the best way to deploy compute into AWS in containerized workloads.
The abstraction you want is Jobs: ttps://aws.github.io/copilot-cli/docs/concepts/jobs/
Building this any other way on AWS would require provisioning multiple artifacts. The Copilot Jobs abstraction basically encapsulates the provisioning of those artifacts into one repeatable pattern.
- Support of Lambda web adapter on AWS Copilot
-
AWS ECS Basics and Tips
AWS Copilot CLI is a tool that lets you deploy production-ready, scalable services on AWS from a Dockerfile in one command.
-
Need some help understanding pulling git code to ECS.
and here is the copilot page if you are interested https://aws.github.io/copilot-cli/
- AWS Copilot CLI
-
What is your production environment?
For larger high availability required things, AWS ECS with RDS, ElastiCache, CloudFront, S3, etc.. Really like Copilot for deployment/env/secret/sidecar management (probably needs a rename now): https://aws.github.io/copilot-cli/
-
Heroku Status ā Dashboard/API Offline
We are spending about 60% less. Workload has actually lessened since AWS is so much more stable. Getting to a similar DX as Heroku was quite the lift, but once it's done, it's done. These days we generally only have outages when we screw something up ourselves. I recommend https://github.com/aws/copilot-cli for starting out on ECS.
-
Deploying on ECS
I'd recommend checking out AWS Copilot (https://aws.github.io/copilot-cli/)
What are some alternatives?
aws-cdk - The AWS Cloud Development Kit is a framework for defining cloud infrastructure in code
TabNine - AI Code Completions
pulumi-quickstart - Pulumi best practices
terraform-cdk - Define infrastructure resources using programming constructs and provision them using HashiCorp Terraform
preview-environments - Quickly create temporary preview environments
terraforming - Export existing AWS resources to Terraform style (tf, tfstate) / No longer actively maintained
knboard - Kanban boards with React & Django.
awesome-cdk - A collection of awesome things related to the AWS Cloud Development Kit (CDK)
actions - A collection of GitHub Actions to run Pluralith in CI and automate infrastructure documentation generation
terraform - Terraform enables you to safely and predictably create, change, and improve infrastructure. It is a source-available tool that codifies APIs into declarative configuration files that can be shared amongst team members, treated as code, edited, reviewed, and versioned.
ctk - Visual composer for container based workloads
Pulumi - Pulumi - Infrastructure as Code in any programming language. Build infrastructure intuitively on any cloud using familiar languages š