Skip to content

Instantly share code, notes, and snippets.

@reggi
Created October 17, 2025 05:28
Show Gist options
  • Save reggi/46a5033265d03dbace98ae2020ecbdae to your computer and use it in GitHub Desktop.
Save reggi/46a5033265d03dbace98ae2020ecbdae to your computer and use it in GitHub Desktop.
Idea

I've had an idea for a bit that i've parked on and I just wanted to document it because I told someone today at a tech meetup about it, but I also spoke to some other people about it over the year.

The main idea is a static site generate / server side site generator.

It points to a directory of files and builds that list of files into a website.

Each directory is a webpage and there can be different views to how that webpage is viewed.

For instance you can have a directory show as "two column" / "wiki style" is where you have a list of files on the right and you click the page and the right is the content.

Or you can have a directory show all files rendered "pinterest style" with each item being a box with a masonry style.

Goal one - file-extenion driven

I want a file-extension driven webpage.

I want to serve a file like a .stl, downloadable as a binary and also renderable as a file extension.

I want download plugins that control how the server renders different file types.

Goal two - "micro apps"

I really want the ability to create "micro apps" from a collection of file extensions. For instance if you create a custom file type .form.json that represents an object from the package: https://github.com/rjsf-team/react-jsonschema-form then you could have a json file that represents a form and have a file-rendere that renders react, you can add an addtion to the spect to POST data to another sibling file guestlist.csv and that file could be append when the form is submitted. With two files a signup.form.json and a guestlist.csv file, you could have a whole guestlist app in two files.

Goal three - virtual filesystem

I've worked on an idea where a full postgres database mimics or parallels the unix file system. Each row is a file. Files have user permissions, a user is needed to check unix access to files. You can use postgres functions for common unix commands like cat, touch, adduser etc. You can virtualize all files in postgres, If files are binaries you can save then in a s3-like file store. This feature allows for a simple image uploader to work, save the file and referece it within "micro apps"

Goal four - sftp / ssh

If you virtualize the file system, you could have a wrapper for sftp / ssh that virtualizes ssh, you can run "touch meow.txt" and it would insert the item in postgres.

This would also allow you to upload the site using rsync from a folder on your machine.

Goal five - content views

If you have a json file in the address format https://schema.org/address and you have content-addressable components somehting like one for google maps, one for open map, etc https://reggi.com/google-map.view and https://reggi.com/open-street-map.view which both consume the address schema as a prop. I want a way to merge the content and the view addressable on the interent as two resource and have the server AND the client be able to render that unit.

https://reggi.com/flavortown.json + https://reggi.com/google-map.view

I'd love to be able to render both of these out.

https://reggi.com/render?content=https://reggi.com/flavortown.json&view=https://reggi.com/google-map.view


Obvously the "interactive" / "dynamic" things arent necessary, i like the idea for having this kind of stuff but it's fluffy and can be insecure. I like some of these ideas.

All I want is the ability to have a server where I really dont need to worry about the design, there's uniformity, and a standard set by the primatives involved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment