susam.net
flyctl
susam.net | flyctl | |
---|---|---|
6 | 545 | |
32 | 1,307 | |
- | 0.9% | |
9.0 | 9.9 | |
5 days ago | 7 days ago | |
Common Lisp | Go | |
GNU General Public License v3.0 or later | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
susam.net
-
How I run my servers
I have a similar setup for my personal and project websites. Some similarities and differences:
* I use Linode VMs ($5/month).
* I too use Debian GNU/Linux.
* The initial configuration of the VM is coded as a shell script: https://github.com/susam/dotfiles/blob/main/linode.sh
* Project-specific or service-specific configuration is coded as individual Makefiles. This takes care of creatng An example: https://github.com/susam/susam.net/blob/main/Makefile
* The software is written in Common Lisp. In case of a personal website or blog, a static website is generated by a Common Lisp program. In case of an online service or web application, the service is written as a Common Lisp program that uses Hunchentoot to process HTTP requests and return HTTP responses.
* I use Nginx too. Nginx serves the static files as well as functions as a reverse proxy when there are backend services involved. Indeed TLS termination is an important benefit it offers. Other benefits include rate limiting requests, configuring an allowlist for HTTP headers to protect the backend service, etc.
- Ask HN: What tools do you use on your blog in 2023?
-
Reasons you aren't updating your personal site (2020)
I began developing personal websites in 2001. It was a time when people like me would develop personal websites just because we could. It didn't matter whether we had something useful to say or if anyone visited the website. All that mattered was that it was fun! I still maintain my website in the same spirit.
I do share the technical posts from my websites on HN and Reddit hoping to get some feedback but that's not the primary motive. Also, there were no HN and Reddit in 2001. Back then I used to write for myself and I still do so now. My personal website is a way for me to keep an archive of some fun things I know so that my future self can look back at them when needed or desired. Only a few days ago, I added a jokes page[1] to my website just because I thought it would be nice to keep my favourite jokes somewhere easily accessible.
As years go by, I've found that the friction of editing and publishing new posts or pages to my website has only become less. First came, virtual private servers that swayed me away from shared web hosting solutions. Then came Git which made it incredibly efficient and convenient to keep a change history of my website and sync it to any system. I write my pages in plan HTML using Emacs. Then git add; git commit; make pub [2] and the updated website is published within seconds. A Common Lisp program reads all my HTML pages, adds a common theme and template to them and writes them out to a directory Nginx can read from. It is as low friction as it can get that suits my taste and preferences while maintaining complete flexibility on the website.
It has been 13 years since I wrote my first "Hello!" and while HTML and web development and publishing has evolved a lot since then, I am still having fun!
[1] https://susam.net/maze/jokes.html
[2] https://github.com/susam/susam.net/blob/main/Makefile#L144
-
Lisp for the web: deploying with Systemd, gotchas and solutions
form.service (the systemd unit file)
-
Simplicity of IRC
Source code [0] is available on GitHub; looks like they wrote their own simple site generator.
I've been thinking about something similar (maybe even simpler) for my blog too.
[0]: https://github.com/susam/susam.net
- Static site and comment form served dynamically using a tiny Common Lisp web server
flyctl
-
How to deploy a nestjs back-end from a mono repo on fly.io
To begin visit fly.io to create an account. Next install flyctl a command line tool for creating and deploying fly apps. macOS
-
Getting started with Open SaaS
For frontend deployment, I used Netlify (for the generous free package) and the recommended fly.io for server + database (also cheap package).
-
Breaking the Myth: Scalable, Multi-Region, Low-Latency App Exists And Will Not Cost You A Kidney.
Create an account on Fly.io.
-
How to use fly.io and Tigris to deploy a Next.js app
You can learn more about fly.io and tigris, we will need to create an account on both platforms for this project regardless. Anyway with the theory out of the way let's get started in the next section as we create our accounts and start building the app.
-
Set up your own personal browser in the Cloud
Fly.io is a platform that helps you run your apps and databases closer to your users all around the world. It takes your app code, packages it up neatly, and puts it on virtual machines that can be quickly started or stopped. This makes your app faster for users and more reliable. Fly.io is easy to use, works well for small projects or personal apps. It's a great way to make sure your app runs smoothly for people no matter where they are.
-
NoSQL Postgres: Add MongoDB compatibility to your Supabase projects with FerretDB
In this post, we'll start from scratch, running FerretDB locally via Docker, trying out the connection with mongosh and the MongoDB Node.js client, and finally deploy FerretDB to Fly.io for a production ready set up.
-
Free tools for developers to build their apps
2- fly.io
-
Top 5 Ways To Host Your Full-Stack App For Free πβ¨
Fly is a cloud platform that focuses on global edge computing. Fly specializes in high-performance hosting and provides a global network of edge locations. Fly is known for its scalability and performance optimizations.
-
Tech stack used for SaaS
But videototextai.com is built using NextJS + Firebase auth + Firestore and a backend deployed at fly.io . Fly makes it really easy to deploy docker containers and that is IMO the fastest way to develop, you can setup a local setup
-
Is it still worth choosing Heroku in 2023?
Alternatives explored: * northflank: While running the wrk test, requests were taking 3-7 seconds. Couldn't repeat Heroku's phenomenon of "400ms-800ms" during such a load test. * fly.io: Reliability: Itβs Not Great * render.com: I remember the time when indiehackers.com was down because of an outage on Render, not sure if it's worth trusting.
What are some alternatives?
maze - Susam's Maze β’ Main website: https://susam.in/maze/ β’ Mirror: https://susam.github.io/maze/
vercel - Develop. Preview. Ship.
spcss - A simple, minimal, classless stylesheet for simple HTML pages
supabase - The open source Firebase alternative.
docker-rollout - π Zero Downtime Deployment for Docker Compose
s6-overlay - s6 overlay for containers (includes execline, s6-linux-utils & a custom init)
ts-neural-network - A neural network to play with
podman-compose - a script to run docker-compose.yml using podman
The Lounge - π¬ β Modern, responsive, cross-platform, self-hosted web IRC client
litestream - Streaming replication for SQLite.
blog.johnnyreilly.com - This is the source code for https://johnnyreilly.com
Dokku - A docker-powered PaaS that helps you build and manage the lifecycle of applications