A Django + Vue reference project that focuses on developer tooling and CI/CD + IaC (by briancaffey)

Django-step-by-step Alternatives

Similar projects and alternatives to django-step-by-step

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better django-step-by-step alternative or higher similarity.

django-step-by-step reviews and mentions

Posts with mentions or reviews of django-step-by-step. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-01-22.
  • What is your development cycle when using docker and containers? What's the general flow between developing locally and running the containers to test.
    2 projects | /r/django | 22 Jan 2023
    Here's an example of a docker-compose file in my reference Django project:
  • My Infrastructure as Code Rosetta Stone - Deploying the same Django application on AWS ECS Fargate with CDK, Terraform and Pulumi
    6 projects | /r/devops | 7 Jan 2023
  • My Infrastructure as Code Rosetta Stone - Deploying the same web application on AWS ECS Fargate with CDK, Terraform and Pulumi
    8 projects | | 7 Jan 2023
    Mono repo with a sample Django micro blogging app (μblog) and frontend app (Vue SPA written with Quasar), GitHub Action workflows for infrastructure and (separate) application deployment pipelines, IaC code that consumes each of the libraries listed above, VuePress documentation site and miscellaneous items (k6 load testing scripts, Cypress tests, docker-compose, etc.):
  • Decoupling terraform ecs task definition and deployments
    2 projects | /r/Terraform | 23 Nov 2022
    By ignoring changes here you don’t have to worry about infra upgrades pushing out application updates. And you can update your app with with a separate pipeline. My code uses AWS CLI to register new task definitions. Here’s an example of my pipeline that deploy the app:
  • Scenario based question for DevOps Engineers out there
    2 projects | /r/devops | 22 Nov 2022
    Here are some other questions that would be good to ask about the infrastructure: * What AWS account will this run in? Who has access to that account? Are SSO permission sets used? * What DNS records will be used to access the frontend and the backend? Are these two services accessed via the same record URL? For example, all do you to only send* traffic to the backend and then send all other* to the Angular frontend? Or do you want to use for all API traffic and for the Angular site. What about non-prod environments? Will you use for a staging environment for a non-prod environment named alpha? * You mentioned that the team will be using Terraform heavily, how will you be splitting up your modules? When you run Terraform's apply command, does it update a single set of infrastructure for your entire application, or do you run terraform apply several times for different groups of resources, such as a networking stack (with VPC), data stack (with RDS) and application stack (for ECS resources), for example? You will probably use terraform remote state to manage these different logical components and the data dependencies they have between each other. * Another related question is how you are running pipelines for Terraform? I would use something like GitHub Actions. When a pipeline runs, you should see the output of a terraform plan stage and then the pipeline should pause for manual approval after the changes have been reviewed. This can be done with GitHub environments, for example, and other CI/CD tools can also do this. * What happens when you need to change an environment variable? This can be a complicated question. Environments that are not secrets might be stored in a terraform.tfvars file, or might be stored in environment variables in your pipeline in the form of TFVAR{name}, so this implies that changing an environment variable is an infrastructure change. You want to keep your infrastructure deployments separate from your application deployments. If you are using ECS, you probably want to use ignore_changes for the task definitions referenced by the services. This will create a new task definition, but it will not be used by the new services. When you do an application update, the service may use this new task definition with the updated environment variable. * Another question: does anyone on the team need direct access to the database? Is there a bastion host used in the infrastructure that can people can connect to the DB with via port forwarding? I hope these questions are helpful. I have thought about a lot of these and have been exploring their answers with an open source project focused on a containerized, database-backed Python web app (made with Django) that I deploy on AWS with ECS Fargate, and I have another repo with Terraform modules for deploying application infrastructure. Here's the application repo: and here is the Terraform module repo: Please let me know if you have any questions
  • Anyone has a django project with user login, Picture posting with like functionality please provide git link!
    2 projects | /r/django | 31 Oct 2022
    Hi u/Vast_Consideration34, here's the GitHub link to my open-source Django application called μblog, and it has the functionality that you described: login functionality, posts (with optional images) and likes.
  • The appropriate way to deploy full stack app on ECS
    2 projects | /r/aws | 15 Oct 2022
    Here's the application code (mono-repo that defines backend and frontend applications/Docker images):
  • Django Docker Containers and good example projects
    5 projects | /r/django | 5 Oct 2022
    Here's one of my practice projects that I use for learning and practicing deployments. It is a simple microblogging application that implements the application both using the MTV paradigm and the REST/SPA paradigm. My deployment efforts are narrowly focused on ECS Fargate, one of several ways to run containers on AWS, and I also focus on using Terraform and GitHub Actions to both build infrastructure and deploy new versions of the application. terraform-aws-django is repo that contains all of the Terraform code that is used to build the application. Happy to answer any questions about these repos!
  • Setting up ad hoc development environments for Django applications with AWS ECS, Terraform and GitHub Actions
    4 projects | | 11 Jun 2022
  • Deploying K8s with Terraform to minikube locally?
    2 projects | /r/kubernetes | 25 Dec 2021
    I have done this with pulumi before and it worked well, here’s the link:
  • A note from our sponsor - InfluxDB | 2 Oct 2023
    Manage all types of time series data in a single, purpose-built database. Run at any scale in any environment in the cloud, on-premises, or at the edge. Learn more →


Basic django-step-by-step repo stats
5 months ago
Collect and Analyze Billions of Data Points in Real Time
Manage all types of time series data in a single, purpose-built database. Run at any scale in any environment in the cloud, on-premises, or at the edge.