This PR introduces an overhaul for the front page and login features while keeping the rest of the application intact. ## Major Changes - TailwindCSS + DaisyUI Integration: Add modern CSS framework for component-based utility styling - Build System: Added pnpm for CSS building; can be extended for updated frontend builds in the future - Navbar + Footer: Redesigned and includable; old version retained for unstyled elements - Optimized Assets: Added minified and CSS-stylable logos ## New Features - Static Pages: Added comprehensive mockups of static pages (legal, privacy policy, terms of use, contact, etc.). **Note:** These have to be fixed before a public release, as their content is largely unreviewed and incorrect. Probably best to do in a separate PR that only contains updates to these. - Discourse API: Implement minimal features based on RestAPI for controllable results. ## Current bugs - [x] The static pages include the default navbar and footer on the login page. This will likely not work, as users need to access it before logging in; no good workaround so far (problem with Django templating system). - [ ] The front page predict link is currently non-functional; the redesigned page is almost ready but better done in a separate PR as it also touches Django code. - [x] Visual bug with the news cards. Still intend to fix for this PR Co-authored-by: Tim Lorsbach <tim@lorsba.ch> Reviewed-on: enviPath/enviPy#179 Reviewed-by: jebus <lorsbach@envipath.com> Co-authored-by: Tobias O <tobias.olenyi@envipath.com> Co-committed-by: Tobias O <tobias.olenyi@envipath.com>
enviPy
Local Development Setup
These instructions will guide you through setting up the project for local development.
Prerequisites
- Python 3.11 or later
- uv - Python package manager
- Docker and Docker Compose - Required for running PostgreSQL database
- Git
- Make
Note: This application requires PostgreSQL (uses
ArrayField). Docker is the easiest way to run PostgreSQL locally.
1. Install Dependencies
This project uses uv to manage dependencies and poe-the-poet for task running. First, install uv if you don't have it yet.
Then, sync the project dependencies. This will create a virtual environment in .venv and install all necessary packages, including poe-the-poet.
uv sync --dev
Note on RDkit installation: if you have rdkit installed on your system globally with a different version of python, the installation will try to link against that and subsequent calls fail. Only option remove global rdkit and rerun sync.
The frontend requires pnpm to correctly display in development.
Install it here.
2. Set Up Environment File
Copy the example environment file for local setup:
cp .env.local.example .env
This file contains the necessary environment variables for local development.
3. Quick Setup with Poe
The easiest way to set up the development environment is by using the poe task runner, which is executed via uv run.
uv run poe setup
This single command will:
- Start the PostgreSQL database using Docker Compose.
- Run database migrations.
- Bootstrap initial data (anonymous user, default packages, models).
After setup, start the development server:
uv run poe dev
This will start the css-watcher as well as the django-development server,
The application will be available at http://localhost:8000.
Note: The development server automatically starts a CSS watcher (pnpm run dev) alongside the Django server to rebuild CSS files when changes are detected. This ensures your styles are always up-to-date during development.
Other useful Poe commands
You can list all available commands by running uv run poe --help.
uv run poe db-up # Start PostgreSQL only
uv run poe db-down # Stop PostgreSQL
uv run poe migrate # Run migrations only
uv run poe bootstrap # Bootstrap data only
uv run poe shell # Open the Django shell
uv run poe build # Build frontend assets and collect static files
uv run poe clean # Remove database volumes (WARNING: destroys all data)
Troubleshooting
-
Docker Connection Error: If you see an error like
open //./pipe/dockerDesktopLinuxEngine: The system cannot find the file specified(on Windows), it likely means your Docker Desktop application is not running. Please start Docker Desktop and try the command again. -
SSH Keys for Git Dependencies: Some dependencies are installed from private git repositories and require SSH authentication. Ensure your SSH keys are configured correctly for Git.
-
For a general guide, see GitHub's official documentation.
-
Windows Users: If
uv synchangs while fetching git dependencies, you may need to explicitly configure Git to use the Windows OpenSSH client and use thessh-agentto manage your key's passphrase.- Point Git to the correct SSH executable:
git config --global core.sshCommand "C:/Windows/System32/OpenSSH/ssh.exe" - Enable and use the SSH agent:
# Run these commands in an administrator PowerShell Get-Service ssh-agent | Set-Service -StartupType Automatic -PassThru | Start-Service # Add your key to the agent. It will prompt for the passphrase once. ssh-add
- Point Git to the correct SSH executable:
-