Growth Website Live
The growth website is live now.
Now future monthly learnings should be more complete.
I fixed cloudflare proxy that caused login issues (now wired locally), went live with the new website with new ansible scripts.
The growth website is live now.
Now future monthly learnings should be more complete.
I fixed cloudflare proxy that caused login issues (now wired locally), went live with the new website with new ansible scripts.
Started growth.jonasruilong.com as the personal growth hub so I remember what I have done and learned so I dont make the same mistakes again :(
Achievements:
Continued working on my education website
Achievements:
Settled on Ubuntu as the production host for the Jonas sites — one server running the apps behind a reverse proxy.
Infra is described as Ansible playbooks so base setup, deploys, and rebuilds stay repeatable when migrating or standing up a new box.
Started a shared login service for the Jonas sites — one place to sign in, so edu, homepage, and later apps don’t each keep their own accounts.
Apps stay public where they should; private materials stay behind roles decided per app. No passwords stored on the client sites.
Started edu.jonasruilong.com as a personal lecture-notes library — Kanti Wettingen → ETH Zürich → Baruch
Achievements:
Started jonasruilong.com as the personal hub — story and navigation into other apps.
Explored layout ideas and chose a scroll-driven 2.5D “scroll opera”:
Welcome first, themed worlds as portals, Dock later.
Achievements:
Goal:
It is used for caching, Session Management, Real-time Analytics, Pub/Sub Messaging, Persistent Storage, Scalability
redis-cli to start
By default it is bind to localhost and also protectedmode (clients from other hosts can't connect), (read more about requirepass and ACL for user managment)
Redis should not be public. Better to use it as a storage service for a backend where users can connect
Redis uses binary TCP