actions
cdk-django
Our great sponsors
actions | cdk-django | |
---|---|---|
1 | 10 | |
25 | 46 | |
- | - | |
1.5 | 5.1 | |
about 1 year ago | 5 days ago | |
TypeScript | TypeScript | |
Mozilla Public License 2.0 | MIT License |
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.
actions
-
Is there Open API Documentation for the REST API Server?
I'm doing my own troubleshooting. (https://github.com/Pluralith/actions/issues/10)
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.
What are some alternatives?
web-extension-boilerplate - The web extension boilerplate help to set up project quickly using typescript, jest, webpack, githook, prettier and github actions
aws-cdk - The AWS Cloud Development Kit is a framework for defining cloud infrastructure in code
nextjs-prisma-boilerplate - Full stack boilerplate with Next.js, Prisma, Tailwind, TypeScript, Docker, Postgres, documentation, frontend and backend unit and integration tests with Jest, Cypress end-to-end tests, Github Actions CI/CD workflows, and production deployment with Traefik and Docker.
pulumi-quickstart - Pulumi best practices
preview-environments - Quickly create temporary preview environments
knboard - Kanban boards with React & Django.
ctk - Visual composer for container based workloads
django-step-by-step - A Django + Vue reference project that focuses on developer tooling and CI/CD + IaC
ecs-fargate-ci-cd-pipeline - Repository from exanubes.com for Fargate App with a SSL Certificate
cdk-constructs - A collection of higher-level reusable cdk constructs
terraform-aws-django - Terraform modules for deploying Django applications on AWS using ECS Fargate
djazure - The Django on Azure Template automates the deployment of a Django application to Azure through custom management commands, Terraform, and GitHub Actions.