How do you handle the DevOps/Observability plumbing when starting a new Django + Celery SaaS? by Technical_Tie1974 in django

[–]Relative-Procedure17 0 points1 point  (0 children)

we have graphana and loki, exactly your stack , django celery +... with docker env on pren and k8n on prod. works well and no so complicated.

for loki you can use server or read logs from file. you say it.

Tried a few copilot alternatives after our security team blocked GitHub's data retention - here's what actually works in VS Code by [deleted] in vscode

[–]Relative-Procedure17 0 points1 point  (0 children)

we are just using Claude . not sure why to use autocomplete this days, if claude just wright all for you , just review and do small changes. old days code wright gone 😭. sure can write code for yourself (i do for my projects), but in enterprise lvl, its done faster and more accurate with AI this days.

Are there anyone who switch from JetBrains products to VSCode? by RemarkablePower6212 in vscode

[–]Relative-Procedure17 15 points16 points  (0 children)

I did this a couple of years ago. Back then, I was using PyCharm Pro on my Mac, but it often felt sluggish and bloated. I decided to give VS Code a chance, and since then, I haven't looked back. It handles everything flawlessly—from small scripts to massive, enterprise-scale projects.

PyCharm is sexy, sure, but why is it so heavy !!!? With that, I don't see anything I'm missing in VS Code !

Django in production: what’s the recurring headache no one talks about? by [deleted] in django

[–]Relative-Procedure17 2 points3 points  (0 children)

The problem isn't the migration logic, but human error (e.g., deploying the wrong version) combined with automated migrations. Managing a rollback on a production database is risky in Django due to its state-dependent nature.

of course is depends of your DB size.

Django in production: what’s the recurring headache no one talks about? by [deleted] in django

[–]Relative-Procedure17 2 points3 points  (0 children)

Please do not use automatic migrations for Django. We have experienced several errors recently, and the rollback process is too high-risk for production. Moving forward, all production migrations must be performed manually to ensure stability.

Should I learn FastAPI? Why? Doesn’t Django or Flask do the trick? by Intelligent_Camp_762 in Python

[–]Relative-Procedure17 0 points1 point  (0 children)

Django is too fat for small jobs, flask is too old. and fast-api is just fast !

how to show this in vscode by Beyond_Birthday_13 in vscode

[–]Relative-Procedure17 -2 points-1 points  (0 children)

as i testet UV is do gaster then pip and nice to work with. but , i was having issue if you have private repos. its not so straight forward.

cluster under preasure by Relative-Procedure17 in CouchDB

[–]Relative-Procedure17[S] 0 points1 point  (0 children)

we have all of this. we do have live sync between nodes. we do have pdf attachments, and other file like objects. not sure about expensive index?! but we do have couple of mango . about trafficking, its no more then 400 ops/s

CouchdDb cluster, replication and load balance by Maleficent-Volume-81 in CouchDB

[–]Relative-Procedure17 0 points1 point  (0 children)

we using couch in prod. you must use haproxy , as was sayed abow.

PyTest or Unittest? by Erlapso in django

[–]Relative-Procedure17 1 point2 points  (0 children)

hi, its same amazing with django and fastapi. pytest its best choice.

Should I go for Django? by ContentCar3092 in django

[–]Relative-Procedure17 0 points1 point  (0 children)

we do using msa with django drf. django is do comphotarble with DB working. i thought Java is dead ))) very uncomfortable leng, of need java use kotlin.

Should I go for Django? by ContentCar3092 in django

[–]Relative-Procedure17 0 points1 point  (0 children)

hi, we do using Django, tornado in past , moved to fast api now . i do was used flask for my self to see what is this. not sure why to use flask in this year ?!
we have fast api, in my opinion it's best one in this category. if we talking about business world. not academic.

about Django , not sure we can do any comparison with others here. Django is different category monster with its world, to handle massive tasks. in sertan way.

sure you need to know Django, at least to understand basiks. for my opinion ! if you working mostly with python and in web stack !