1

Self-hosted API for creating/querying json files on different storage providers (local, S3, MinIO, ...). Typical use cases are (1) quick/flexible data storage in personal projects (2) mocking APIs (3) having a 'data scratchpad' for various scripts. Quite proud of it and looking for input :)

5
[-] LaVillaStrangiato@infosec.pub 0 points 3 weeks ago

Thanks! I never had much success there, but who knows. I will create the docker image, that is a good idea in general :)

[-] LaVillaStrangiato@infosec.pub 0 points 3 weeks ago* (last edited 3 weeks ago)

Thanks for checking my project out. In the readme I state it's for 'small personal projects' where you want to get something quickly. However, "widly insecure" seems a bit much? If you use it for storing data that has no privacy (like public blog posts, and their comments)?

2

Hi all. I'm looking for some advice. I've recently finished a side project I'm excited about (Self-hosted API for CRUD-ing JSON files on different storage providers (local, S3, minIO, etc). Available here.

However, I have a difficult time reaching engineers that would be interested in it. How do people typically market/share side projects for other developers? Thanks in advance!

2

Hi all. I made a self-hosted API for CRUD-ing JSON files. Built for data storage in small personal projects, or mocking an API for development. Advantages are simplicity, interoperability and performance (using the cache system).

API is based on your JSON structure. So the example below is for CRUD-ing [geralt][city] in file.json. The value (which can be anything) is then added to the body of the request. For me, it has been really flexible and useful, so I want to share it and collect feedback!

8

Built for data storage in small personal projects, or mocking an API for development. Advantages are simplicity, interoperability (JSON files, APIs, multiple filesystems) and performance (using the cache system).

The API is based on your JSON files/structure. So, the example below is for CRUD-ing [key1][key2] in file.json. The value (which can be anything) is then added to the body of the request. Moreover, there are helper functions for appending and incrementing values. As a result, the data creates the API.

DELETE/PUT/GET: /api/file/key1/key2/...

LaVillaStrangiato

joined 1 month ago