Re: What makes the images deletion from the media folder?

2023-03-30 Thread ram.mu...@gmail.com
Hello David,

We are not using a docker container but our server is a dedicated cloud 
instance.

Best regards,
~Ram



On Thursday, March 23, 2023 at 10:34:44 PM UTC-6 David Nugent wrote:

> Are you using Django in a docker container?
>
> If so, any changes to the filesystem are ephemeral and disappear when the 
> container is recycled.
>
>
> Regards,
> David
>
>
> -- Original Message --
> From "Ram" 
> To django...@googlegroups.com
> Date 3/24/2023 2:04:56 PM
> Subject What makes the images deletion from the media folder?
>
> Hi,
>
> We are seeing weird issue that images are deleted between deployments in 
> our Dev. server and we are seeing this message in log files:
>
> example:
>
> WARNING 2023-03-10 07:03:16,927 - Not Found: /media/cl_1zf3am8.JPG
>
>
> Could someone let me know what could be the issue?
>
> Best regards,
> ~Ram 
>
> -- 
> 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 django-users...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/django-users/CA%2BOi5F2mTfx%2B32XKjM__gkgp0i7vPKgWsGuGVGQsr%3DSX_U0MRg%40mail.gmail.com
>  
> 
> .
>
>

-- 
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 django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/2ba08875-fb1a-4f11-a2db-435d9973c7c4n%40googlegroups.com.


Re: Error while running '$ python manage.py collectstatic --noinput'.

2023-12-16 Thread ram.mu...@gmail.com
Here is the static files setting that we have in our settings.py file:


*STATIC_URL = '/static/'STATIC_ROOT = os.path.join(BASE_DIR, 'static')*
On Saturday, December 16, 2023 at 7:02:46 PM UTC-7 Ram wrote:

> Hi,
>
> Did anyone hit this error before during production server or any type of 
> deployment. We tried deployment using Digital Oceanś App platform as a 
> pre-prod deployment to check whether this App platform is feasible for our 
> Django web site, but we are hitting this error no matter what ever 
> modification we change in settings.py to avoid this error. Tried a lot of 
> Google search results to address this issue, but no luck so far. We are 
> wondering whether anyone has any recommendations on this error. If you did 
> not try Digital Oceanś app platform, what would be your recommendation for 
> production server deployment? We are planning to use only app platforms to 
> avoid infrastructure overhead.
>
>
>> [2023-12-17 01:40:06] │ -> $ python manage.py collectstatic --noinput
>> [2023-12-17 01:40:06] │Traceback (most recent call last):
>> [2023-12-17 01:40:06] │  File "/workspace/manage.py", line 23, in 
>> 
>> [2023-12-17 01:40:06] │execute_from_command_line(sys.argv)
>> [2023-12-17 01:40:06] │  File 
>> "/app/.heroku/python/lib/python3.11/site-packages/django/core/management/__init__.py",
>>  
>> line 446, in execute_from_command_line
>> [2023-12-17 01:40:06] │utility.execute()
>> [2023-12-17 01:40:06] │  File 
>> "/app/.heroku/python/lib/python3.11/site-packages/django/core/management/__init__.py",
>>  
>> line 420, in execute
>> [2023-12-17 01:40:06] │django.setup()
>> [2023-12-17 01:40:06] │  File 
>> "/app/.heroku/python/lib/python3.11/site-packages/django/__init__.py", line 
>> 24, in setup
>> [2023-12-17 01:40:06] │apps.populate(settings.INSTALLED_APPS)
>> [2023-12-17 01:40:06] │  File 
>> "/app/.heroku/python/lib/python3.11/site-packages/django/apps/registry.py", 
>> line 91, in populate
>> [2023-12-17 01:40:06] │app_config = AppConfig.create(entry)
>> [2023-12-17 01:40:06] │ ^^^
>> [2023-12-17 01:40:06] │  File 
>> "/app/.heroku/python/lib/python3.11/site-packages/django/apps/config.py", 
>> line 228, in create
>> [2023-12-17 01:40:06] │import_module(entry)
>> [2023-12-17 01:40:06] │  File 
>> "/app/.heroku/python/lib/python3.11/importlib/__init__.py", line 126, in 
>> import_module
>> [2023-12-17 01:40:06] │return 
>> _bootstrap._gcd_import(name[level:], package, level)
>> [2023-12-17 01:40:06] │   
>> 
>> [2023-12-17 01:40:06] │  File "", 
>> line 1204, in _gcd_import
>> [2023-12-17 01:40:06] │  File "", 
>> line 1176, in _find_and_load
>> [2023-12-17 01:40:06] │  File "", 
>> line 1147, in _find_and_load_unlocked
>> [2023-12-17 01:40:06] │  File "", 
>> line 690, in _load_unlocked
>> [2023-12-17 01:40:06] │  File "> importlib._bootstrap_external>", line 940, in exec_module
>> [2023-12-17 01:40:06] │  File "", 
>> line 241, in _call_with_frames_removed
>> [2023-12-17 01:40:06] │  File 
>> "/app/.heroku/python/lib/python3.11/site-packages/django_tables2/__init__.py",
>>  
>> line 1, in 
>> [2023-12-17 01:40:06] │from .columns import (
>> [2023-12-17 01:40:06] │  File 
>> "/app/.heroku/python/lib/python3.11/site-packages/django_tables2/columns/__init__.py",
>>  
>> line 8, in 
>> [2023-12-17 01:40:06] │from .jsoncolumn import JSONColumn
>> [2023-12-17 01:40:06] │  File 
>> "/app/.heroku/python/lib/python3.11/site-packages/django_tables2/columns/jsoncolumn.py",
>>  
>> line 11, in 
>> [2023-12-17 01:40:06] │from django.contrib.postgres.fields 
>> import HStoreField
>> [2023-12-17 01:40:06] │  File 
>> "/app/.heroku/python/lib/python3.11/site-packages/django/contrib/postgres/fields/__init__.py",
>>  
>> line 1, in 
>> [2023-12-17 01:40:06] │from .array import *  # NOQA
>> [2023-12-17 01:40:06] │
>> [2023-12-17 01:40:06] │  File 
>> "/app/.heroku/python/lib/python3.11/site-packages/django/contrib/postgres/fields/array.py",
>>  
>> line 3, in 
>> [2023-12-17 01:40:06] │from django.contrib.postgres import 
>> lookups
>> [2023-12-17 01:40:06] │  File 
>> "/app/.heroku/python/lib/python3.11/site-packages/django/contrib/postgres/lookups.py",
>>  
>> line 4, in 
>> [2023-12-17 01:40:06] │from .search import SearchVector, 
>> SearchVectorExact, SearchVectorField
>> [2023-12-17 01:40:06] │  File 
>> "/app/.heroku/python/lib/python3.11/site-packages/django/contrib/postgres/search.py",
>>  
>> line 1, in 
>> [2023-12-17 01:40:06] │import psycopg2
>> [2023-12-17 01:40:06] │  File 
>> "/app/.heroku/python/lib/

Re: Error while running '$ python manage.py collectstatic --noinput'.

2023-12-19 Thread ram.mu...@gmail.com
Hi Ihor,

Thank you for your email. We do not have any reference to heroku but 
Digital Oceanś App platform is using heroku. We resolved  the above error 
by adding this environment variable:

DISABLE_COLLECTSTATIC = 1
But we are planning to enable this once the main deployment is done.

Best Regards,
~Ram


On Monday, December 18, 2023 at 3:02:47 PM UTC-7 Ihor Dmytrenko wrote:

> Why you have heroku in your log? Remove all old dependency configs in your 
> settings first and then you need specify 
>
> ```python
> STATICFILES_DIRS = [
> os.path.join(BASE_DIR, 'static'),
> ]
>
> STATIC_ROOT = os.path.join(BASE_DIR, 'staticfiles')
> STATIC_URL = '/static/'
>
> HOME_DIRECTORY_SELF_STORAGE = os.path.expanduser('~')
> MEDIA_ROOT = os.path.join(HOME_DIRECTORY_SELF_STORAGE, 'public_html/')
> MEDIA_URL = '/media/'
> DEFAULT_FILE_STORAGE = 'django.core.files.storage.FileSystemStorage'
> ```
>

-- 
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 django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/dd8bd37a-b000-4872-b56b-06487410665an%40googlegroups.com.


Re: Why would a deployed site shows up with distorted layout

2024-03-04 Thread ram.mu...@gmail.com
Thank you all for providing valuable answers. 

1. My case was actually related to the permission issue on 
~/www-data/example.com/static folder as mentioned by @Asamoah Emmanuel. 
2. Though I changed the ownership of the folder with 
siteUser:www-data ~/www-data/example.com/static
the problem was not resolved, but resolved with the next step.
3. So I had to add siteUser in nginx.conf file and then restarted gunicorn 
and nginx

Here is the solution lead me fixing my 
issue: 
https://stackoverflow.com/questions/44918725/django-301-and-403-forbidden-errors-on-my-static-files-in-production

Best Regards,
~Ram


On Thursday, February 29, 2024 at 2:32:19 PM UTC-7 Mordecai Etukudo wrote:

> First install white noise and collect static you are good to go 
>
> On Thu, Feb 29, 2024, 7:38 PM ASAMOAH EMMANUEL  
> wrote:
>
>> I faced this issue before and I know how frustrating it can be. after 
>> sifting through several results, this worked. sudo usermod -aG username 
>> www-data
>> sudo chown -R :www-data /home/username/projects/personal
>>
>> On Thu, Feb 29, 2024 at 6:37 PM ASAMOAH EMMANUEL  
>> wrote:
>>
>>> Replace your username with this and run this code: sudo usermod -aG 
>>> username www-data
>>> sudo chown -R :www-data /home/username/projects/personal
>>>
>>> On Thu, Feb 29, 2024 at 2:15 PM Amitesh Tripathi  
>>> wrote:
>>>
 Your website is in debug mode??

 On Thu, 29 Feb 2024, 11:54 Ram,  wrote:

> Hi,
>
> We are able to deploy our pre-production site successfully using 
> jenkins deployment and as part of the deployment we do the following:
>
> 1. Django application with runserver
> 2. Gunicorn restart
> 3. Nginx restart
>  
> But our web application loads with distorted layout and we have this 
> setting for staticfiles
>
> STATIC_URL = '/static/'
> STATIC_ROOT = os.path.join(BASE_DIR, 'static')
>
> We are wondering what is missing?
>
> Best Regards,
> ~Ram
>
> -- 
> 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 django-users...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/django-users/CA%2BOi5F2xrz-hiJphYeuGX56hU26wWJGduUZHNibTUXVs-KtjeA%40mail.gmail.com
>  
> 
> .
>
 -- 
 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 django-users...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/django-users/CAFJ1wEUvJK_Ur_6JpLeMVMXK4TMH_ryUy7gLWqjXG8a0%2B_o2VA%40mail.gmail.com
  
 
 .

>>>
>>>
>>> -- 
>>> I don't stop when I'm tired, I only stop when the job is done.
>>>
>>
>>
>> -- 
>> I don't stop when I'm tired, I only stop when the job is done.
>>
>> -- 
>> 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 django-users...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/django-users/CABFHQYx%3DsSpZZo3gbXctqFC9Nrdyb49WvbxL6CYo%3DiZ%2B_dqOVQ%40mail.gmail.com
>>  
>> 
>> .
>>
>

-- 
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 django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/5d38a298-723a-4065-90c0-e33d5e7f979fn%40googlegroups.com.


Django web site is not opened though runserver us running

2024-03-05 Thread ram.mu...@gmail.com
Hi,

Could someone look at this post and help me understand what is missing? We 
think there is no issue in our Django application but Digital Ocean 
concluded that the issue is from our application.

https://serverfault.com/questions/1155482/django-site-is-not-opening-up-on-digital-ocean-ubuntu-droplet

Best Regards,
~Ram

-- 
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 django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/8e4927bb-8e7d-45c0-900b-4f7f18dd578en%40googlegroups.com.


Re: Django web site is not opened though runserver us running

2024-03-06 Thread ram.mu...@gmail.com
Hi,

Hoping someone can provide some clue on this?

Best regards,
~Ram

On Tuesday, March 5, 2024 at 1:32:51 AM UTC-7 ram.mu...@gmail.com wrote:

> Hi,
>
> Could someone look at this post and help me understand what is missing? We 
> think there is no issue in our Django application but Digital Ocean 
> concluded that the issue is from our application.
>
>
> https://serverfault.com/questions/1155482/django-site-is-not-opening-up-on-digital-ocean-ubuntu-droplet
>
> Best Regards,
> ~Ram
>

-- 
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 django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/573034cd-fd0a-4a31-97a5-e551416331den%40googlegroups.com.


Re: Django web site is not opened though runserver us running

2024-03-06 Thread ram.mu...@gmail.com
Thank you both. I deployed the same site twice on DO droplets without any 
issues and the site was running fine for a year, but it stopped working 
lately. I did not find any clue so far. 

1. Before deployment

$ ps -ef | grep runserver rmbl 1424 1414 0 05:02 pts/0 00:00:00 grep 
--color=auto runserver --- 

$ $ sudo nmap -p 4000, 22 > 136.189.5.1 -Pn Starting Nmap 7.94SVN ( 
https://nmap.org ) at 2024-02-29 05:03 UTC Nmap scan report for 22 
(0.0.0.22) Host is up. PORT STATE SERVICE 4000/tcp filtered remoteanything 
Nmap scan report for rmbl-s-1vcpu-2gb-ams3-01 (136.189.5.1) Host is up 
(0.82s latency). PORT STATE SERVICE 4000/tcp closed remoteanything Nmap 
done: 2 IP addresses (2 hosts up) scanned in 2.15 seconds  $ $ 
sudo ufw status Status: active To Action From -- --  OpenSSH ALLOW 
Anywhere 8080 ALLOW Anywhere 8000 ALLOW Anywhere 5432 ALLOW Anywhere 4000 
ALLOW Anywhere OpenSSH (v6) ALLOW Anywhere (v6) 8080 (v6) ALLOW Anywhere 
(v6) 8000 (v6) ALLOW Anywhere (v6) 5432 (v6) ALLOW Anywhere (v6) 4000 (v6) 
ALLOW Anywhere (v6) --


2. After successful deployment:
 

$ $ sudo netstat -lanp | grep 4000 $ $ sudo nmap -p 4000, 22 136.189.5.1 
-Pn Starting Nmap 7.94SVN ( https://nmap.org ) at 2024-02-29 05:07 UTC Nmap 
scan report for 22 (0.0.0.22) Host is up. PORT STATE SERVICE 4000/tcp 
filtered remoteanything Nmap scan report for rmbl-s-1vcpu-2gb-ams3-01 
(136.189.5.1) Host is up(0.82s latency). PORT STATE SERVICE 4000/tcp 
closed remoteanything Nmap done: 2 IP addresses (2 hosts up) scanned in 
2.14 seconds $ $ ps -ef | grep runserver jenkins 1679 1 1 05:05 ? 00:00:00 
/var/lib/jenkins/workspace/dev-rmbl-project/env/bin/python manage.py 
runserver 0.0.0.0:4000 jenkins 1691 1679 1 05:05 ? 00:00:01 
/var/lib/jenkins/workspace/dev-rmbl-project/env/bin/python manage.py 
runserver 0.0.0.0:4000 rmbl 1727 1414 0 05:07 pts/0 00:00:00 grep 
--color=auto runserver $ $ sudo nmap -p 4000, 22 136.189.5.1 -Pn Starting 
Nmap 7.94SVN ( https://nmap.org ) at 2024-02-29 05:08 UTC Nmap scan report 
for 22 (0.0.0.22) Host is up. PORT STATE SERVICE 4000/tcp filtered 
remoteanything Nmap scan report for rmbl-s-1vcpu-2gb-ams3-01 (136.189.5.1) 
Host is up (0.78s latency).

PORT STATE SERVICE 4000/tcp closed remoteanything Nmap done: 2 IP addresses 
(2 hosts up) scanned in 2.13 seconds $ $ $wget http://136.189.5.1:4000 
--2024-02-29 13:44:39-- http://136.189.5.1:4000/ Connecting to 
136.189.5.1:4000... failed: Connection refused.


3. DO support answer:

Upon checking the issue you are facing with the Django application, I can 
see port 4000 is showing as closed on your Droplet. Please refer to the 
snippet for the details:

nmap -p 4000,22 136.189.5.1 -Pn
Starting Nmap 7.94 ( https://nmap.org ) at 2024-02-28 13:45 IST
Nmap scan report for 136.189.5.1
Host is up (0.23s latency).
PORT STATE  SERVICE
22/tcp   open   ssh
4000/tcp closed http-alt

A closed result means, no active service is listening to that port.  In 
this situation, you would need to check the application status that's 
configured to run on this port and proceed further with its result. If it's 
not active, try restarting the service. If it is still failing to start, 
you might have to troubleshoot further to check what is preventing the 
services from starting.  If it shows any error please check the logs and 
proceed accordingly. 

Best Regards,
~Ram

On Wednesday, March 6, 2024 at 9:40:40 PM UTC-7 Muhammad Juwaini Abdul 
Rahman wrote:

> I always follow the following steps to deploy my site on DO. 
>
> https://www.digitalocean.com/community/tutorials/how-to-set-up-django-with-postgres-nginx-and-gunicorn-on-ubuntu
>
> Countless attempts and 0 fail. 
>
> Maybe you can try this. If you want to keep trying with your way, also no 
> problem.
>
> On Thu, 7 Mar 2024 at 12:02, ram.mu...@gmail.com  
> wrote:
>
>> Hi,
>>
>> Hoping someone can provide some clue on this?
>>
>> Best regards,
>> ~Ram
>>
>> On Tuesday, March 5, 2024 at 1:32:51 AM UTC-7 ram.mu...@gmail.com wrote:
>>
>>> Hi,
>>>
>>> Could someone look at this post and help me understand what is missing? 
>>> We think there is no issue in our Django application but Digital Ocean 
>>> concluded that the issue is from our application.
>>>
>>>
>>> https://serverfault.com/questions/1155482/django-site-is-not-opening-up-on-digital-ocean-ubuntu-droplet
>>>
>>> Best Regards,
>>> ~Ram
>>>
>> -- 
>>
> 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 django-users...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d

Re: Django web site is not opened though runserver us running

2024-03-06 Thread ram.mu...@gmail.com
We have been using 8000 only but just to avoid this problem we tried 4000 
to see whether we can get out of this problem. Basically tested with both 
8000 and 4000 so far, but the result is the same.

Best Regards,
~Ram

On Wednesday, March 6, 2024 at 10:45:39 PM UTC-7 Muhammad Juwaini Abdul 
Rahman wrote:

> Why do you need to use a non-standard port such as 4000 when deployed on a 
> server?
>
> On Thu, 7 Mar 2024 at 13:18, ram.mu...@gmail.com  
> wrote:
>
>> Thank you both. I deployed the same site twice on DO droplets without any 
>> issues and the site was running fine for a year, but it stopped working 
>> lately. I did not find any clue so far. 
>>
>> 1. Before deployment
>>
>> $ ps -ef | grep runserver rmbl 1424 1414 0 05:02 pts/0 00:00:00 grep 
>> --color=auto runserver --- 
>>
>> $ $ sudo nmap -p 4000, 22 > 136.189.5.1 -Pn Starting Nmap 7.94SVN ( 
>> https://nmap.org ) at 2024-02-29 05:03 UTC Nmap scan report for 22 
>> (0.0.0.22) Host is up. PORT STATE SERVICE 4000/tcp filtered remoteanything 
>> Nmap scan report for rmbl-s-1vcpu-2gb-ams3-01 (136.189.5.1) Host is up 
>> (0.82s latency). PORT STATE SERVICE 4000/tcp closed remoteanything Nmap 
>> done: 2 IP addresses (2 hosts up) scanned in 2.15 seconds  $ $ 
>> sudo ufw status Status: active To Action From -- --  OpenSSH ALLOW 
>> Anywhere 8080 ALLOW Anywhere 8000 ALLOW Anywhere 5432 ALLOW Anywhere 4000 
>> ALLOW Anywhere OpenSSH (v6) ALLOW Anywhere (v6) 8080 (v6) ALLOW Anywhere 
>> (v6) 8000 (v6) ALLOW Anywhere (v6) 5432 (v6) ALLOW Anywhere (v6) 4000 (v6) 
>> ALLOW Anywhere (v6) --
>>
>>
>> 2. After successful deployment:
>>  
>>
>> $ $ sudo netstat -lanp | grep 4000 $ $ sudo nmap -p 4000, 22 136.189.5.1 
>> -Pn Starting Nmap 7.94SVN ( https://nmap.org ) at 2024-02-29 05:07 UTC 
>> Nmap scan report for 22 (0.0.0.22) Host is up. PORT STATE SERVICE 4000/tcp 
>> filtered remoteanything Nmap scan report for rmbl-s-1vcpu-2gb-ams3-01 
>> (136.189.5.1) Host is up(0.82s latency). PORT STATE SERVICE 4000/tcp 
>> closed remoteanything Nmap done: 2 IP addresses (2 hosts up) scanned in 
>> 2.14 seconds $ $ ps -ef | grep runserver jenkins 1679 1 1 05:05 ? 00:00:00 
>> /var/lib/jenkins/workspace/dev-rmbl-project/env/bin/python manage.py 
>> runserver 0.0.0.0:4000 jenkins 1691 1679 1 05:05 ? 00:00:01 
>> /var/lib/jenkins/workspace/dev-rmbl-project/env/bin/python manage.py 
>> runserver 0.0.0.0:4000 rmbl 1727 1414 0 05:07 pts/0 00:00:00 grep 
>> --color=auto runserver $ $ sudo nmap -p 4000, 22 136.189.5.1 -Pn Starting 
>> Nmap 7.94SVN ( https://nmap.org ) at 2024-02-29 05:08 UTC Nmap scan 
>> report for 22 (0.0.0.22) Host is up. PORT STATE SERVICE 4000/tcp filtered 
>> remoteanything Nmap scan report for rmbl-s-1vcpu-2gb-ams3-01 (136.189.5.1) 
>> Host is up (0.78s latency).
>>
>> PORT STATE SERVICE 4000/tcp closed remoteanything Nmap done: 2 IP 
>> addresses (2 hosts up) scanned in 2.13 seconds $ $ $wget 
>> http://136.189.5.1:4000 --2024-02-29 13:44:39-- http://136.189.5.1:4000/ 
>> Connecting to 136.189.5.1:4000... failed: Connection refused.
>>
>>
>> 3. DO support answer:
>>
>> Upon checking the issue you are facing with the Django application, I can 
>> see port 4000 is showing as closed on your Droplet. Please refer to the 
>> snippet for the details:
>>
>> nmap -p 4000,22 136.189.5.1 -Pn
>> Starting Nmap 7.94 ( https://nmap.org ) at 2024-02-28 13:45 IST
>> Nmap scan report for 136.189.5.1
>> Host is up (0.23s latency).
>> PORT STATE  SERVICE
>> 22/tcp   open   ssh
>> 4000/tcp closed http-alt
>>
>> A closed result means, no active service is listening to that port.  In 
>> this situation, you would need to check the application status that's 
>> configured to run on this port and proceed further with its result. If it's 
>> not active, try restarting the service. If it is still failing to start, 
>> you might have to troubleshoot further to check what is preventing the 
>> services from starting.  If it shows any error please check the logs and 
>> proceed accordingly. 
>>
>> Best Regards,
>> ~Ram
>>
>> On Wednesday, March 6, 2024 at 9:40:40 PM UTC-7 Muhammad Juwaini Abdul 
>> Rahman wrote:
>>
>>> I always follow the following steps to deploy my site on DO. 
>>>
>>> https://www.digitalocean.com/community/tutorials/how-to-set-up-django-with-postgres-nginx-and-gunicorn-on-ubuntu
>>>
>>> Countless attempts and 0 fail. 
>>>
>>> Maybe you can try th

Re: Any open source SMS?

2024-03-10 Thread ram.mu...@gmail.com
Hello Vitaly,

Thank you for your email but my requirement is to send OTP to registered 
phone numbers.

Best Regards,
~Ram


On Friday, March 8, 2024 at 7:41:13 AM UTC-7 Vitaly Bogomolov wrote:

> Hi
>
>
> Our use case: 
> We need to generate OTP code to users upon signup in our application. 
>
>
> You can take a look at my solution to this task for Django:
>
> https://github.com/vb64/django.admin.auth.emailpin
>
>

-- 
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 django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/74f1f5e0-b549-4808-a16b-1847a6f8ffb0n%40googlegroups.com.


Passionate Django Full Stack developers from Colorado, USA

2024-03-19 Thread ram.mu...@gmail.com
Dear Passionate developers, 

I would like to connect with expert developers who live in Colorado, USA. 
Please message me if you are interested?

Best Regards,
~Ram

-- 
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 django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/ac51ce0e-5bd4-43ae-bd8b-e7de71c1f59dn%40googlegroups.com.