Re: Django deployments

https://www.youtube.com/watch?v=_MbZSSXdM8s I have deployed multiple Django applications on same server using nginx and gunicorn, above video was really helpful On Thu, Nov 18, 2021 at 2:04 AM Elango Venkat wrote: > Hi all, can anyone help me on the below or suggestions pls. > I need to

Re: Django deployments

I you use wamp, you have apache, so just must set other site in your setting of apache. Dios L@s Bendiga Saludos, [image: --] daniel.bojorge [image: http://]about.me/daniel.bojorge [image: snake]*Curso Desarrollo Web con Python usando Django

Django deployments

Hi all, can anyone help me on the below or suggestions pls. I need to deploy two django projects in my local server.. one project I have deployed with wamp & mod wsgi port 8060 Any way to add config to have other project in port 80 -- You received this message because you are subscribed to the

Re: Django Microsoft Authentication Backend not succeeding on new deployments

On Fri, Jan 29, 2021 at 08:58:48AM -0800, Larry Martell wrote: > We finally found the issue - I said we had the same version of all the > python packages but we did not - the new system had 2.0.1 version of > pyjwt. When we downgraded to 1.7.1 it started working again. The > requirements file for

Re: Django Microsoft Authentication Backend not succeeding on new deployments

On Sat, Jan 23, 2021 at 7:41 PM Ryan Nowakowski wrote: > > On Sat, Jan 23, 2021 at 11:05:14AM -0800, Larry Martell wrote: > > On Sat, Jan 23, 2021 at 8:14 AM Ryan Nowakowski wrote: > > > > > > A couple of places to look: > > > > > > 1. Different domains on the new boxes? You'll need to add the

Re: Django Microsoft Authentication Backend not succeeding on new deployments

On Sat, Jan 23, 2021 at 11:05:14AM -0800, Larry Martell wrote: > On Sat, Jan 23, 2021 at 8:14 AM Ryan Nowakowski wrote: > > > > A couple of places to look: > > > > 1. Different domains on the new boxes? You'll need to add the new callback > > urls on the Microsoft side. > > 2. Different version

Re: Django Microsoft Authentication Backend not succeeding on new deployments

On Sat, Jan 23, 2021 at 8:14 AM Ryan Nowakowski wrote: > > A couple of places to look: > > 1. Different domains on the new boxes? You'll need to add the new callback > urls on the Microsoft side. > 2. Different version of Python on the new boxes? Same domain name, same version of python and all

Re: Django Microsoft Authentication Backend not succeeding on new deployments

A couple of places to look: 1. Different domains on the new boxes? You'll need to add the new callback urls on the Microsoft side. 2. Different version of Python on the new boxes? On January 22, 2021 2:51:30 PM CST, Larry Martell wrote: >I have an app deployed in many places and it uses

Django Microsoft Authentication Backend not succeeding on new deployments

I have an app deployed in many places and it uses Django Microsoft Authentication Backend. Starting yesterday when we deploy the app the auth is now not working. We get back Failed to authenticate you for an unknown reason. Please try again later. We can see in the azure logs that the login was

Re: Production deployments and Version Control for DJango projects

Hi, After some review we decided to go with Jenkins for continuous integration and deployment. Our development server was deployed on Ubuntu 18.x with Postgres DB and Python 3 virtual environment, DJango and GIT. Now we are planning to setup Jenkins server on the same dev. server so that we

Re: Production deployments and Version Control for DJango projects

Hi , Try Jenkins also for Continuous Integration (CI) Regards Jegatheeswaran sundaravadivel On Sun, 19 Apr 2020 at 22:23, Ram wrote: > Thank you, all. We started with GIT hub and planning to add > ansible-playbook later in our development phase. > > Best regards > ~Ram > > On Sat, Feb 15, 2020

Re: Production deployments and Version Control for DJango projects

Thank you, all. We started with GIT hub and planning to add ansible-playbook later in our development phase. Best regards ~Ram On Sat, Feb 15, 2020 at 2:55 AM Kasper Laudrup wrote: > Hi Aldian, > > On 15/02/2020 05.57, Aldian Fazrihady wrote: > > Try ansible-playbook > > > > That's exactly

Re: Production deployments and Version Control for DJango projects

Hi Aldian, On 15/02/2020 05.57, Aldian Fazrihady wrote: Try ansible-playbook That's exactly what Ansible was designed for, so I agree that this would be the obvious route to go. No reason not to use git for source control and then Ansible to automate the deployment. Kind regards,

Re: Production deployments and Version Control for DJango projects

Hi Sam, On 15/02/2020 05.58, Sam Hefer wrote: Bitbucket is great if you don’t like Git env. It has a great interface. Bitbucket is more or less a web frontend to git, so it can hardly be regarded as an alternative to git. But I agree that the git command line interface isn't exactly the

Re: Production deployments and Version Control for DJango projects

ect > folder and running makemigrations and migrate. Since this manual process is > not sustainable in future, I would like to implement right process and > tools for source code management and both dev & production servers > deployments. > > Could someone provide me document

Re: Production deployments and Version Control for DJango projects

e manually to project folder > and running makemigrations and migrate. Since this manual process is not > sustainable in future, I would like to implement right process and tools for > source code management and both dev & production servers deployments. > > Could someone p

Production deployments and Version Control for DJango projects

and tools for source code management and both dev & production servers deployments. Could someone provide me documented procedure and tools to automate the deployment and manage the version control. I know GIT is one option but do you guys any other open source tools for souce code management.

Re: architecture for Blue/Green deployments

A related discussion on django-developers has turned up this module, written by one of the participants in the discussion there: https://github.com/aspiredu/django-safemigrate >> -- You received this message because you are subscribed to the Google Groups "Django users" group. To

Re: Deployments

You should follow each and every step of the tutorial. Once you can get an empty django project up and running, you can swap that project with yours. git clone the repo to the above projects folder location and make the changes (e.g. rename project name in config files, etc.) as required.

Re: Deployments

In this tutorial I think they are covering about a how we can create new project in digital ocean but I have already one project in my local machine. How I can upload that project into server?? Thank you for your support. On Fri, 7 Jun 2019, 01:24 Chetan Ganji, wrote: > >

Re: Deployments

https://www.digitalocean.com/community/tutorials/how-to-set-up-django-with-postgres-nginx-and-gunicorn-on-ubuntu-16-04 Regards, Chetan Ganji +91-900-483-4183 ganji.che...@gmail.com http://ryucoder.in On Thu, Jun 6, 2019 at 10:33 PM Soumen Khatua wrote: > Hi Folks, > > I develope one project

Deployments

Hi Folks, I develope one project using django in my localhost. Now how I can deploy that project into digital ocean and what are changes I need to do in my project for moving to production server. Please help I have no idea regarding this matter. Thank You. Regards, Soumen -- You received this

Re: architecture for Blue/Green deployments

I should clarify one thing... On Thu, 2 May 2019 at 20:28, Shaheed Haque wrote: > On Thu, 2 May 2019 at 19:37, wrote: > >> What gold! >> >> The essential piece of your logic is here: >> >>> Enforce a development process that ensures that (roughly speaking) all >>> database changes result in a

Re: architecture for Blue/Green deployments

On Thu, 2 May 2019 at 19:37, wrote: > What gold! > > The essential piece of your logic is here: > >> Enforce a development process that ensures that (roughly speaking) all >> database changes result in a new column, and where the old cannot be >> removed until a later update cycle. All

Re: architecture for Blue/Green deployments

What gold! The essential piece of your logic is here: > Enforce a development process that ensures that (roughly speaking) all > database changes result in a new column, and where the old cannot be > removed until a later update cycle. All migrations populate the new column. I assume that

Re: architecture for Blue/Green deployments

a web application framework that is not > Django, we've had no problem. > > I'm our "Systems/Applications Architect", and some years ago I helped > choose Django over some other solutions. I stand by that as correct for > us, but our Cloud guys want to know how to do Blue/Green dep

architecture for Blue/Green deployments

tions. I stand by that as correct for us, but our Cloud guys want to know how to do Blue/Green deployments, and the more I look at it the less happy I am. Here's the problem: - Django's ORM has long shielded developers from simple SQL problems like "SELECT * FROM fubar ..." an

Re: Automating deployments

config > > sudo python manage.py restartservices > > > Any thought on this? How do you automate your deployments? I heard > about fabric lots of times but never used it. Will fabric be helpful > in my case? Does it has any advantage for writing my own scripts? Or > maybe

Re: Automating deployments

I imagine the workflow: > >>> > >>> sudo pip install django-my_project > >>> my_project-admin.sh clone project_name path > >>> > >>> sudo python manage.py installrequirements > >>> sudo python manage.py setuppostgres > >&g

Re: Automating deployments

project >>> my_project-admin.sh clone project_name path >>> >>> sudo python manage.py installrequirements >>> sudo python manage.py setuppostgres >>> python manage.py syncdb >>> python manage.py migrate >>> python manage.py createsuperu

Re: Automating deployments

python manage.py syncdb >> python manage.py migrate >> python manage.py createsuperuser >> >> sudo python manage.py setupapache >> python manage.py collectstatic >> sudo python manage.py setupceleryd >> sudo python manage.py createtincserver >> python

Re: Automating deployments

> python manage.py updatetincd > sudo python manage.py setupfirmware > python manage.py loaddata firmwareconfig > > sudo python manage.py restartservices > > > Any thought on this? How do you automate your deployments? I heard > about fabric lots of times but never used it. W

Automating deployments

manage.py updatetincd sudo python manage.py setupfirmware python manage.py loaddata firmwareconfig sudo python manage.py restartservices Any thought on this? How do you automate your deployments? I heard about fabric lots of times but never used it. Will fabric be helpful in my case? Does it has any

Re: High availability deployments

On Wed, Mar 23, 2011 at 11:29:00PM -0700, Shamail Tayyab wrote: >We have a setup in which we can't afford downtime (even while > deployment). > > Our setup is based on lighttpd + django (on fcgi via flup). What my > problem is, when we restart django, the site goes down for about a > couple

Re: High availability deployments

We're all wrong... :) We're all wrong... Yes... Well first at all regradless of any programing language etc. there must be a service level agreement that states what that magical "high availabilty" really means. Usually, even in very critical systems there is reservation for short downtimes to

Re: High availability deployments

You need to handle this within your code logic. The problem is, when a 500 Error is given back, you don't know what actually happened on the server side. For all you know, it could have been half way through its task. You need to add logic within the client side and server side code, to handle

Re: High availability deployments

Hello, First of all, problem is not with lighttpd, but with flup On Mar 24, 8:29 am, Shamail Tayyab wrote: > Hi, > >    We have a setup in which we can't afford downtime (even while > deployment). > > Our setup is based on lighttpd + django (on fcgi via flup). What my >

Re: High availability deployments

See this blog post: http://rambleon.usebox.net/post/3279121000/how-to-gracefully-restart-django-running-fastcgi TL;DR : just send SIGHUP to flup process (pidfile option to fastcgi), like this: kill -SIGHUP `cat /path/to/flup.pid` I suggest using Gunicorn, as it handles graceful reloads better

Re: High availability deployments

Hi, First at all, if you're working with real high availability system you already have resolved most of the single point of failure problems, and other non- django related issues (like broken hardware, broken network connections etc.) And by looking what you're experiencing now indicates that

Re: High availability deployments

On Wed, 2011-03-23 at 23:29 -0700, Shamail Tayyab wrote: > Our setup is based on lighttpd + django (on fcgi via flup). What my > problem is, when we restart django, the site goes down for about a > couple of seconds (and all API calls to DB remains incomplete > resulting in 500.html being rendered

High availability deployments

Hi, We have a setup in which we can't afford downtime (even while deployment). Our setup is based on lighttpd + django (on fcgi via flup). What my problem is, when we restart django, the site goes down for about a couple of seconds (and all API calls to DB remains incomplete resulting in