Django-step-by-step Alternatives

django-step-by-step reviews and mentions

• 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: https://github.com/briancaffey/django-step-by-step/blob/main/docker-compose.yml

• 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 | dev.to | 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.): github.com/briancaffey/django-step-by-step

• My Django blog website doesn't have a 'like' button. How can I add one?
  1 project | /r/django | 1 Jan 2023

  This project also uses a model manager to make it easy to show how many people like a post as well as if the current user likes the post or not https://github.com/briancaffey/django-step-by-step/blob/main/backend/apps/blog/managers.py.

• Need some theoretical clarity on Terraform vs AWS CDK
  1 project | /r/Terraform | 12 Dec 2022

  Here's another repo that consumes these IaC libraries and deploys them through GitHub Actions pipelines: https://github.com/briancaffey/django-step-by-step

• 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: https://github.com/briancaffey/django-step-by-step/blob/main/.github/workflows/ad_hoc_update_backend.yml

• 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 example.com/api/* traffic to the backend and then send all other example.com/* to the Angular frontend? Or do you want to use api.example.com for all API traffic and example.com for the Angular site. What about non-prod environments? Will you use alpha.example.com 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: https://github.com/briancaffey/django-step-by-step and here is the Terraform module repo: https://github.com/briancaffey/terraform-aws-django. Please let me know if you have any questions

• How do you organize your code in Vue 3 composition api?
  1 project | /r/vuejs | 9 Nov 2022

  Here is how I organize my modules for an example microblog app: https://github.com/briancaffey/django-step-by-step/tree/main/quasar-app/src/modules

• Django templates with DRF and React
  1 project | /r/django | 9 Nov 2022

  Yes, this is possible. There are different ways to do this and it will depend on how and where you host your applications. Here's an example project of mine that I run on AWS that uses some the same URL with some routes for Django template-powered views, some views for a Vue app, some views for REST API and some views for GraphQL: https://github.com/briancaffey/django-step-by-step.

• When to implement CI/CD in a brand new project?
  1 project | /r/django | 6 Nov 2022

  Here's an example of how I implement CI and CD with a Django project on AWS using GitHub Actions. I use ECS Fargate. https://github.com/briancaffey/django-step-by-step/blob/main/.github/workflows/backend_linting_and_unit_tests.yml

• A note from our sponsor - SaaSHub
  www.saashub.com | 7 Sep 2024

  SaaSHub helps you find the best software and product alternatives Learn more →