DEV Community: Tima

How to Run a Django Server: Development, Testing, and Deployment

Tima — Thu, 06 Nov 2025 07:37:40 +0000

Running a Django server isn’t always the same—it depends on whether you’re developing locally, testing deployment readiness, or running on real hosting/VPS. This guide walks through the different approaches.

1. Normal Server Startup for Development

The simplest way to run Django locally is:

python manage.py runserver

By default, it runs on port 8000. You can specify another port:

python manage.py runserver 7000

👉 Changing ports can be useful when integrating with tools like VSCode Live Server or when running multiple apps side by side.

2. Testing Deployment Readiness

When you switch to production mode (DEBUG=False and ALLOWED_HOSTS set), Django stops serving static files. To simulate production but still serve static files locally, use:

python manage.py runserver --insecure

This lets you test custom error pages (404, 500, etc.) without setting up Apache or Nginx yet.

3. Running on Shared Hosting

Django apps don’t run with runserver in production. Instead, they use WSGI or ASGI interfaces to communicate with web servers.

WSGI: synchronous communication (classic Django setup).
ASGI: asynchronous communication (supports async features).

A typical wsgi.py might look like:

import os
from django.core.wsgi import get_wsgi_application

os.environ.setdefault("DJANGO_SETTINGS_MODULE", "Website.settings")
application = get_wsgi_application()

4. Running on a VPS

On a VPS, you’ll configure a web server (Apache or Nginx) to handle requests and proxy them to Django via a socket or port.

Example Nginx config (HTTP):

server {
    listen 80;
    server_name example.com;

    location /static {
        root /home/site/example.com;
    }

    location /media {
        root /home/site/example.com;
    }

    location / {
        proxy_set_header Host example.com;
        proxy_pass http://unix:/tmp/example.com.socket;
    }
}

👉 In 2025, you should use HTTPS (port 443) with SSL certificates from Let’s Encrypt:

server {
    listen 443 ssl;
    server_name example.com;

    ssl_certificate /etc/letsencrypt/live/example.com/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem;

    location /static {
        root /home/user/example.com;
    }

    location /media {
        root /home/user/example.com;
    }

    location / {
        proxy_set_header Host example.com;
        proxy_pass http://unix:/tmp/example.com.socket;
    }
}

Final Thoughts

Use runserver for local development.
Use --insecure for testing production‑like conditions.
Use WSGI/ASGI for shared hosting.
Configure Nginx/Apache for VPS deployment with HTTPS.

Treat server setup as part of your Django architecture—it’s not just about running code, but about ensuring reliability, scalability, and security.

Discussion

How do you usually run Django in production?

Do you prefer WSGI or ASGI for modern projects?

How to Publish Your Python Package to PyPI (Modern Guide with `pyproject.toml`)

Tima — Thu, 06 Nov 2025 07:33:24 +0000

Publishing your own Python package is a milestone for any developer. It turns your code into something the community can install with a simple pip install. This guide is a quick start for beginners who want to publish their first package using the modern pyproject.toml approach.

Why PyPI Matters

Central hub: PyPI is the official package index for Python, similar to npm for JavaScript.
Easy installs: With one command, you can pull in frameworks like Django or libraries like requests.
Standardization: Packaging ensures consistent distribution and deployment across projects.

pip install django

Setting Up the Basics

Install Python: Download from python.org. Pip comes bundled.
Create a project directory: Example: UsefulPackage/.
Set up a virtual environment:

python -m venv .venv

Register accounts:
- PyPI for production.
- TestPyPI for practice (recommended for beginners).

Minimal Project Structure

Your package should look like this:

UsefulPackage/
 ├── .venv/
 ├── src/
 │    └── useful_package_timthewebmaster/
 │         ├── __init__.py
 │         └── main.py
 ├── LICENSE
 ├── pyproject.toml
 ├── dist/

Configuring `pyproject.toml`

This file defines how your package is built and its metadata. Minimal example:

[build-system]
requires = ["hatchling >= 1.26"]
build-backend = "hatchling.build"

[project]
name = "useful-package-timthewebmaster"
version = "0.0.1"
authors = [
  { name="Tim The Webmaster", email="timachuduk@gmail.com" }
]
license = "MIT"

👉 You can add classifiers, dependencies, keywords, and URLs to make your package more discoverable. See PyPI classifiers for options.

Building the Package

Install the build tool:

pip install build

Generate distributions:

python -m build

This creates .tar.gz and .whl files inside dist/.

Uploading to PyPI

Install Twine:

pip install twine

Upload to TestPyPI:

python -m twine upload --repository testpypi dist/*

Upload to PyPI:

python -m twine upload dist/*

You’ll need an API token from your PyPI account.

Testing Your Package

Install from TestPyPI:

pip install --index-url https://test.pypi.org/simple/ useful-package-timthewebmaster

Or from PyPI directly:

pip install useful-package-timthewebmaster

Run your project and confirm imports work correctly.

Final Thoughts

Publishing to PyPI is more than distribution—it’s about joining the ecosystem. By sharing your package, you contribute to the collective toolbox of developers worldwide. Start small, iterate, and soon you’ll have a portfolio of packages that reflect your coding style and creativity.

💡 Pro tip: Use TestPyPI for practice. It keeps the main index clean and gives you confidence before going public.

Discussion

Have you published a package to PyPI before?

What challenges did you face during the process?

Monetizing Your Website with Yandex Advertising Network (RSYA): A Developer’s Guide

Tima — Thu, 06 Nov 2025 07:26:30 +0000

When we talk about website monetization, most developers immediately think of Google AdSense. But if your audience includes Russian‑speaking users, Yandex Advertising Network (RSYA) can be a powerful alternative. It’s not just another ad platform—it’s a way to align monetization with regional traffic patterns and user expectations.

Why RSYA Matters

Localized reach: RSYA is deeply integrated into the Russian‑speaking internet ecosystem.
Flexible ad formats: From contextual banners to native blocks, RSYA offers customization that developers can embed seamlessly.
Better relevance: Ads are matched to user intent and site content, often outperforming generic networks in CTR for RU traffic.

Getting Started

Eligibility: Your site needs consistent traffic and must comply with Yandex’s content policies.
Application: Submit your site for review. Approval usually takes a few days.
Integration: Once approved, you’ll receive ad code snippets. These can be embedded directly into your HTML or managed via template tags in frameworks like Django.

Technical Integration Tips

Modular templates: Wrap RSYA ad blocks in reusable components.
Responsive design: RSYA supports adaptive blocks—test across devices.
Performance considerations: Lazy‑load ads or place them strategically to avoid slowing down page rendering.

<!-- Example RSYA ad block -->
<div class="rsya-block">
  <!-- Yandex ad code snippet -->
</div>

Developer-Friendly Strategies

Experiment with placement: Sidebar vs. inline content can yield very different results.
Track metrics: Use Yandex.Metrica or Google Analytics to measure CTR, bounce rate, and revenue impact.
Combine with other models: RSYA doesn’t have to be your only monetization stream. Pair it with affiliate links, donations, or premium content.

Ethical Monetization

Independent developers often face the challenge of balancing monetization with user trust. RSYA allows you to filter ad categories, so you can avoid intrusive or irrelevant ads. This helps maintain credibility with your audience.

Final Thoughts

If you’re building for a bilingual or international audience, don’t overlook regional ad networks. RSYA can be a strong complement to global solutions, especially if your traffic leans toward Russian‑speaking users. For developers, the key is to treat monetization as part of your architecture—modular, scalable, and respectful of user experience.

💡 Pro tip: Think of RSYA not just as an ad network, but as a developer tool. By integrating it cleanly into your stack, you maintain control over design, performance, and ethics—while unlocking a new revenue stream.

Discussion

Have you tried RSYA or other regional ad networks?

What strategies worked best for you when balancing monetization with user trust?

SEO in Practice: +55% Impressions, +17% Clicks

Tima — Thu, 25 Sep 2025 10:37:23 +0000

I recently ran a focused SEO optimization experiment on my site. Instead of chasing big overhauls, I made small, measurable changes:

Meta tags rewritten across ~20 articles
Low‑value pages cleaned up or removed
A few quality backlinks added

6‑week results (Google Search Console):

Metric        Before     After     Change
------------------------------------------
Impressions   88,000     137,000    +55%
Clicks        850        1,000     +17.5%
CTR           0.96%      0.71%     -26%

6‑week results (Yandex Webmaster):

Metric        Before     After     Change
------------------------------------------
Impressions   29,000     27,500    -10%
Clicks        800        950       +18.7%
CTR           2.75%      3.45%     +21%

The takeaway: you don’t always need a massive content push. Sometimes, tightening the screws on what you already have delivers the biggest lift.

👉 Full case study with screenshots and details: SEO Optimization Results

When “Visitors” Aren’t Visitors: My Battle With Bots

Tima — Wed, 24 Sep 2025 21:00:00 +0000

One day my site traffic spiked — bounce rates shot up, charts went wild, and most of the “visitors” were hitting only pagination pages. At first, I thought: DDoS? Clickers? Real users from China?

After digging deeper, I realized it was most likely a parser bot scraping my content. The solution? A crash course in .htaccess, IP ranges, and blocking entire countries just to keep my site breathing.

It’s a story about sudden traffic bursts, false alarms, and the messy reality of defending a small independent site.

Read the full breakdown here: Someone is parsing my website from China, and then I’ve blocked them via htaccess file

Tool of the week: Free WYSIWYG Editor with QuillJS

Tima — Wed, 24 Sep 2025 04:00:48 +0000

I’ve put together a simple but powerful online WYSIWYG editor powered by QuillJS. It’s designed for developers, bloggers, and content managers who want to quickly create and format HTML without writing raw code.

Features:

Rich text editing (bold, italic, underline, headings, quotes, lists)
Insert links, media, and code blocks
Export clean HTML instantly
Save, reload, or download your pages for later use
Works right in the browser — no setup required

This tool started as an educational experiment with QuillJS, but it’s grown into a handy utility for anyone who needs quick HTML snippets or formatted content.

Try it here: WYSIWYG Online Editor

Would love to hear your feedback — what features would make this even more useful for your workflow?

DEV Community: Tima

How to Run a Django Server: Development, Testing, and Deployment

1. Normal Server Startup for Development

2. Testing Deployment Readiness

3. Running on Shared Hosting

4. Running on a VPS

Final Thoughts

Tags

Discussion

Further Reading

How to Publish Your Python Package to PyPI (Modern Guide with `pyproject.toml`)

Why PyPI Matters

Setting Up the Basics

Minimal Project Structure

Configuring `pyproject.toml`

Building the Package

Uploading to PyPI

Testing Your Package

Final Thoughts

Tags

Discussion

Further Reading

Monetizing Your Website with Yandex Advertising Network (RSYA): A Developer’s Guide

Why RSYA Matters

Getting Started

Technical Integration Tips

Developer-Friendly Strategies

Ethical Monetization

Final Thoughts

Tags

Discussion

Further Reading

SEO in Practice: +55% Impressions, +17% Clicks

When “Visitors” Aren’t Visitors: My Battle With Bots

Tool of the week: Free WYSIWYG Editor with QuillJS

DEV Community: Tima

How to Run a Django Server: Development, Testing, and Deployment

1. Normal Server Startup for Development

2. Testing Deployment Readiness

3. Running on Shared Hosting

4. Running on a VPS

Final Thoughts

Tags

Discussion

Further Reading

How to Publish Your Python Package to PyPI (Modern Guide with `pyproject.toml`)

Why PyPI Matters

Setting Up the Basics

Minimal Project Structure

Configuring pyproject.toml

Building the Package

Uploading to PyPI

Testing Your Package

Final Thoughts

Tags

Discussion

Further Reading

Monetizing Your Website with Yandex Advertising Network (RSYA): A Developer’s Guide

Why RSYA Matters

Getting Started

Technical Integration Tips

Developer-Friendly Strategies

Ethical Monetization

Final Thoughts

Tags

Discussion

Further Reading

SEO in Practice: +55% Impressions, +17% Clicks

When “Visitors” Aren’t Visitors: My Battle With Bots

Tool of the week: Free WYSIWYG Editor with QuillJS

Configuring `pyproject.toml`