> On Mar 26, 2023, at 6:47 PM, Damanjeet Singh wrote:
>
> Depending on the requirements. Either two different databases or point to one
> database.
>
> Or
> Link one database to master (read and write)
>
> Another database instance to read only.
>
> And you can change Another database to
Depending on the requirements. Either two different databases or point to
one database.
Or
Link one database to master (read and write)
Another database instance to read only.
And you can change Another database to main.
Cheers
On Sun, 26 Mar 2023, 22:33 Sandip Bhattacharya,
wrote:
>
>
>
> On Mar 26, 2023, at 4:32 PM, Damanjeet Singh wrote:
>> 3. How do you do non-backward compatible schema upgrades? Do you do it out
>> of band from deployments? Do you shift traffic to a different cluster, and
>> then zero traffic upgrade the whole cluster at once?
>
>
> Daman: Blue Green
Hello,
Please read my reply below.
Best of luck.
Regards
On Sun, 26 Mar 2023, 21:17 Sandip Bhattacharya,
wrote:
> New to django, so wanted to ask some questions that I didn’t find good
> resources for:
>
> 1. If you deploy django apps using docker, do you run migrations before
> launching
So what would you want for existing entries in the table which were added
before you changed the model?
If you are ok with them being empty, you should use:
details = models.CharField(max_length=500, default=“”)
And run migrate again.
If you are ok instead of this column being null,
New to django, so wanted to ask some questions that I didn’t find good
resources for:
1. If you deploy django apps using docker, do you run migrations before
launching gunicorn/uwsgi etc within the docker image?
2. If you do, how does rolling migrations work? Won’t the non-upgraded replicas
bonsoir jaimerai utilisé l'api nexmo pour envoyer des msg, quelqu'un l'a
t-il deja fait ici??
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
7 matches
Mail list logo
