-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
improved docs, deployed app general improvements
- Loading branch information
Showing
9 changed files
with
133 additions
and
45 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,6 @@ | ||
**/__pycache__ | ||
**/venv | ||
**/.* | ||
**/Dockerfile* | ||
LICENSE | ||
README.md |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,4 +1,5 @@ | ||
venv | ||
/static/*.min.js | ||
.env | ||
.env.* | ||
sqlite |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,34 @@ | ||
# syntax=docker/dockerfile:1 | ||
|
||
FROM python:3.12.2-slim as base | ||
|
||
ENV PYTHONDONTWRITEBYTECODE=1 | ||
ENV PYTHONUNBUFFERED=1 | ||
|
||
WORKDIR /app | ||
|
||
RUN apt update && \ | ||
apt install -y make && \ | ||
apt clean && \ | ||
rm -rf /var/lib/apt/lists/* | ||
|
||
RUN adduser \ | ||
--disabled-password \ | ||
--gecos "" \ | ||
--home "/nonexistent" \ | ||
--shell "/sbin/nologin" \ | ||
--no-create-home \ | ||
--uid "10001" \ | ||
appuser | ||
|
||
RUN --mount=type=cache,target=/root/.cache/pip \ | ||
--mount=type=bind,source=requirements.txt,target=requirements.txt \ | ||
python -m pip install -r requirements.txt | ||
|
||
USER appuser | ||
|
||
COPY . . | ||
|
||
EXPOSE 8000 | ||
|
||
CMD make start |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,54 +1,57 @@ | ||
# Python FastAPI HTMX full-text-search demo | ||
|
||
This project is a **demo** full-text-search application that leverages the power of | ||
[SQLite FT5](https://www.sqlite.org/fts5.html) and | ||
[Algolia SaaS](https://www.algolia.com/) to retrieve search results. | ||
This project is a **demo** full-text-search application that compares the results from | ||
[SQLite FT5](https://www.sqlite.org/fts5.html) and | ||
[Algolia Search platform](https://www.algolia.com/). | ||
|
||
Conceived as an experimental venture, this project serves as a demonstration of an *unconventional* | ||
monolith tech stack. It features an interactive front-end, using a mix of traditional | ||
Server Side Rendering (SSR) and zero custom JavaScript: | ||
Server Side Rendering (SSR) declarative web framework with zero custom JS: | ||
|
||
- [FastAPI](https://fastapi.tiangolo.com/) the server framework; | ||
- [Jinja](https://jinja.palletsprojects.com/) for the SSR templating; | ||
- [HTMX](https://htmx.org/) to enable front-end interactivity in a declarative way. | ||
- [HTMX](https://htmx.org/) to enable front-end interactivity declaratively directly in the HTML. | ||
|
||
## Description and demo | ||
|
||
*So you don't have to spin up the project.* | ||
**[Live demo](https://full-text-search-demo.tofran.com/)** | ||
|
||
https://github.com/tofran/fastapi-htmx-full-text-search-demo/assets/5692603/43d642fd-52d5-4e5b-836a-6609d0c3d782 | ||
|
||
The outcome of this project is something very simple and minimal. The served content is **tiny** and | ||
**fast**. There's no initial loading, all is pre-rendered on the server and each API request renders | ||
HTML that is injected into the DOM - no need for Hydration, | ||
Resumability nor even data serialization. | ||
**fast**. There's no initial loading, everything is pre-rendered on the server, and each API request | ||
renders HTML that is injected into the DOM - no need for Hydration, Resumability nor even data | ||
serialization. It is compatible with most browsers, all the way back to IE11, where it struggles a | ||
little with style, but *works*. | ||
|
||
![OpenAPI spec (swagger)](https://github.com/tofran/fastapi-htmx-full-text-search-demo/assets/5692603/541f1f1a-fe1d-475c-8723-8f5a13e8f0df) | ||
|
||
The application works by serving a full rendered Jinja HTML template when the user navigates to a | ||
Front-End route. These templates are composed via smaller reusable templates (using `include`). | ||
And then I also serve these *components* de-coupled from the whole page in the *HTML API* | ||
(`/html-api/XXX`). HTMX handles the rest, replacing the content in the DOM when necessary. | ||
Front-End route. | ||
These templates are composed via smaller reusable templates (using `include`). | ||
And then the templates (*components*) are also served, de-coupled from the whole page in the | ||
*HTML API* (`/html-api/...`). | ||
HTMX handles the rest, listens to DOM events and updates it when when necessary. | ||
|
||
![Example HTML API request/response](https://github.com/tofran/fastapi-htmx-full-text-search-demo/assets/5692603/8e1aa2a0-53dd-443a-a1d2-caee11cad65c) | ||
|
||
## Development | ||
|
||
- Create a `.env` file based on the `.env.template`. | ||
Your will need an Algolia account, should be pretty simple to setup to | ||
grab the App ID and API Key | ||
(more info in their | ||
[Quick start guide](https://www.algolia.com/doc/guides/getting-started/quick-start/) | ||
). | ||
You will need an Algolia account, should be pretty simple to setup | ||
(more info in their [Quick start guide](https://www.algolia.com/doc/guides/getting-started/quick-start/)). | ||
|
||
- Setup a local environment with `make setup-venv`, | ||
activate it with `source ./venv/bin/activate`. | ||
activate it with `source ./venv/bin/activate` | ||
(or with your favourite tool). | ||
|
||
- Install dependencies `make install-dev`. | ||
- Install dependencies: `make install-dev`. | ||
|
||
- Start the development server `make dev`. | ||
- Start the development server: `make dev`. | ||
|
||
## Deployment | ||
|
||
For deployment the only difference is that you can skip the dev requirements with `make install` | ||
and run the application in a production ready server: `make start`. | ||
For deployment one would use the `./Dockerfile` and set the required environment variables. | ||
|
||
For running locally a production like build, install the dependencies with `make install` | ||
and run the application with `make start`. That's it. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters