HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
silviogutierrez
reactivated
Python2018–2022
silviogutierrez / reactivated

reactivated

Discover this repository through its Hacker News conversations.

2Distinct people
10Mentions
0Explicit recommenders
741GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A public description has not been verified.

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year10 dated mentions

Observed mentions: 2018-10-24 03:24:17 UTC to 2022-06-24 18:40:37 UTC.

012342018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2022

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC202
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC101
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC404
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC101
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC202

What Hacker News says

10 sources
Theoretically, the Dockerfile should "just work"™ with Render.com as well. Right now I focus on fly.io only because their free tier offers PostgreSQL without time limits. Render, I believe, only does so for a period of time. See here: https://github.com/silviogutierrez/reactivated/blob/main/dev... https://github.com/silviogutierrez/reactivated/blob/main/dev... https://github.com/silviogutierrez/reactivated/blob/main/dev...
In Things I do every time I start a Django project
That's exactly what https://github.com/silviogutierrez/reactivated does. It's a work in progress and docs are coming. But it's the best of both worlds: Django SSR using statically typed JSX. See for example my blog or business sites (on profile). Both SSRed by Django using React templates. Then when the client loads, it gracefully "attaches" for dynamic interactive behavior as needed. By far the biggest pain point is having to run node and python on the server. So I'm working on the best way to do that.
In Show HN: Django and React SaaS boilerplate tutorial
Sort of, but not always. My blog at https://www.silviogutierrez.com is React+Django strictly server side. I like JSX that much. Try loading it with JS disabled. Same at my business site: https://www.joyapp.com. It was a huge ordeal getting it setup (with React SSR, etc), but it's definitely doable. I've open sourced it but it sorely needs documentation (incoming): https://github.com/silviogutierrez/reactivated Basically, despite the tooling (not because of it), once you get going with JSX, TypeScript and the like, nothing else comes close. At least in my experience. But again, none of the above stops me from dumping that output into a single cache key per request. It's still dynamic, just cached robustly.
In Next.js 9.5
Tech Stack (We're on HN after all) - React, both for the app itself and the static pages. - Django for all server logic. - Heavy use of Redux for the application areas - Server-side rendered React templates with Django. Seamless with https://github.com/silviogutierrez/reactivated . - PostgreSQL - TypeScript for all React code - Mypy for some Python code, and type generation to interact with TypeScript Disclosures - I do use Google Analytics, but only on the marketing pages. Not in the app. - Mixpanel is used for my own analytics. - I'm working on a clearer privacy policy. Right now, I'm using the one Automattic gracefully open sourced.
In Show HN: Joy – a privacy-first, ad-free nutrition tracker for pragmatic types
I have a quite very crude implementation of form fields on my side, which annotates the type of formfield (as a string) along with several other useful things, like id_for_formfield, html_name etc. -- In your https://github.com/silviogutierrez/reactivated/blob/master/c... import {Form} from '../components/Form'; I can't find `../components/Form`. Where is the source for that? --- Here are the fields I was able to extract, meaningfully. https://github.com/pycampers/react-pages/blob/417ec24129b80b... It still doesn't seem enough for building anything serious though.
In React v16.6.0: lazy, memo and contextType
Agreed. But as soon as you hit any dynamic behavior, you kind of end up wishing you could "drop" into React. That's why I built the following project: https://github.com/silviogutierrez/reactivated It's very early on, but essentially, completely replaces the template rendering with React components. Still regular markup, but whenever you need dynamic behaviors, it's trivial. And it's all server side rendered. So basically, looking at https://github.com/silviogutierrez/reactivated/blob/master/c... You can see the traditional Django context becomes "Props" in the top level component. Then it's React all the way down. Notes: 1. The most complicated part is the initial setup. You do need to run NodeJS, webpack + Django server. Working on improving that. 2. I like TypeScript and use it here. But theoretically it'll be optional. The Django+Pyth
Read the rest
on part is also statically typed using MyPy. 3. No instructions whatsoever yet. But you can see a live site using this stack here: https://www.silviogutierrez.com/ . Notice it's server rendered but has dynamic behaviors that are trivial in React but harder with jQuery + Django. Example: https://www.silviogutierrez.com/blog/making-cck-fields-read-... Look at the nested commenting and moving the form around. Very easy in React. 4. Because of the architecture, adding a much-better-turbolinks style Ajax is trivial. Click around the site above (loading indicator not yet added). The page is re-rendered entirely on the client but gets a server AJAX response. Hope that's interesting info. If you'd like to try it out, definitely let me know. Once you overcome the setup hurdles, it's amazingly productive. As in, if all you wish to do is `{{ form }}` like old school Django, here's the equivalent sample template: https://github.com/silviogutierrez/reactivated/blob/master/c...
In React v16.6.0: lazy, memo and contextType

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.