Getting localhost for next page url in production

Question

hlo, I have deployed a Django rest app in production. When I call a list API there is a pagination, and I am getting localhost for next page URL.

I am using GenericViewSet and LimitOffsetPagination for pagination. My app is running in docker container.And it is pointed to a specific domain. We can access it using domain name "https://abc.xyz.com". But I have used python manage.py runserver:0.0.0.0:8000(it's just for testing) CMD for running the server. Here is the image for more detail. I am calling an live hosted API to get a list from postman. In response data list contains pagination, which contains "http://localhost:8000/api/transaction/?limit=10&offset=10&ordering=-pk&purpose=1". for next page link instead of domain name.

I have hosted application using docker. Following is my docker file:

# Set the working directory
WORKDIR /app
# Copy requirements file
COPY requirements.txt .
# Install dependencies
RUN pip install --upgrade pip && pip install -r requirements.txt
# Copy project files
COPY . .
# Collect static files
RUN python manage.py collectstatic --noinput
# Run migrations
RUN python manage.py makemigrations
RUN python manage.py migrate
# Expose the port 8000
EXPOSE 8000
# Start the server
CMD ["python", "manage.py", "runserver", "0.0.0.0:8000"]

What should I do to get "https://abc.xyz.com/api/transaction/" instead of "http://localhost:8000/api/transaction/"

So what is the problem you are facing and what is your expectation ? Try to explain more detail in your question — Khanh Le Tran, Feb 02 '23 at 02:12
My problem is I am getting "http://localhost:8000/nextpage/?page=2" for next page url in pagination in production. It should be my domain "https://abc.xyz.com/nextpage/?page=2". — Krishna Bhandari, Feb 02 '23 at 06:54
Please clarify your specific problem or provide additional details to highlight exactly what you need. As it's currently written, it's hard to tell exactly what you're asking. — Community, Feb 02 '23 at 13:12
well, yes I solved the problem by customizing the next/previous page links by overriding the method in pagination class. But I don't think that is the good solution. — Krishna Bhandari, Feb 17 '23 at 07:37

score 0 · Answer 1 · answered Feb 02 '23 at 08:05

0

You can use relative url in your html, something like this:

http://localhost:8000/nextpage/?page=2

to

<a href="/nextpage/?page=2" />

When you change to this, your url will be change to yourdomain/nextpage/?page2. So you can run your app in localhost or VM or in container without changing host or absolute url for one by one environment you set up in project.

answered Feb 02 '23 at 08:05

Khanh Le Tran

860
4
15

I am using Django REST API. – Krishna Bhandari Feb 06 '23 at 16:06
I know but you must have html template right ? – Khanh Le Tran Feb 06 '23 at 17:03
no I do not have html template. I am testing this API using postman. After researching for 3-4 days I understood this is not the problem with my app but with the deployment process. Now I do not know how two solve this deployment problem – Krishna Bhandari Feb 07 '23 at 02:35
oh i see, i have to go out right now. I will update the answer as soon as i can. – Khanh Le Tran Feb 07 '23 at 02:39

Getting localhost for next page url in production

1 Answers1