StorX
libsqlfs
StorX | libsqlfs | |
---|---|---|
5 | 10 | |
14 | 582 | |
- | 1.9% | |
10.0 | 0.0 | |
about 2 years ago | 7 months ago | |
PHP | C | |
GNU Affero General Public License v3.0 | GNU Lesser General Public License v3.0 only |
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.
StorX
-
PHP in 2024
Apparently it is still common practice to have such "if bla is set, when do blub" everywhere in ones code? No functions with decorators or a similar or alternative concept? I would think there should be some kind of easy to use mechanism in place, that tends to avoid forgetting these ifs.
There are ... 60 lines of global logic, that is not encapsulated in any function or so?
Some of the functions are quite long. But I think mostly because they render out HTML.
At line 107 with the procedure printHeader starting, what I call PHP nightmare starts:
Switching back and forth between PHP, HTML and HTML with integrated JS (!!!) and CSS. All of course without syntax highlighting, but that is a minor issue. The major issue is treating HTML and JS and CSS as mere strings, instead of structured data, and the very bad readability of having procedures suddenly "end" and spit out some wild HTML, then suddenly continuing again, because some server side logic/decision is required at some place in that stream of unstructured data, whether some part is to be included or not, then the stream continues and then at some point one needs to actually check, that one did not forget to truly end the procedure. This has some of the worst readability. Maybe C code with bit magic is worse.
One can find this kind of approach in many, if not most, Wordpress plugins. What's more is, that this is also terrible for writing tests. The procedures do not return a value to check against. All is a side effect. Perhaps there is some PHP library that manipulates the PHP system, so that one can at least do string comparisons on the side effects. Like mocking, basically. But still terrible for testing.
For a comparison of how it should be done instead, check any templating engine, that at least separates template files from PHP code. Better, checkout SXML libraries, that treat HTML as structured data, a tree that can be traversed and pattern matched against, without pulling out arcane string manipulations or regular expressions. And then consider how one could write tests based on such structured data.
If this "HTML is a string, even on the server side before sending it" kind of approach is how a language treats HTML, then the language is not suitable to be directly used for HTML templating, without any additional library. This alone has caused uncountable security issues in so many projects.
I realize, that this is probably kind of a "one off script" and may not reflect other kinds of PHP code.
I did all of those things myself, years ago. And when I already had moved away from such an approach, I had to maintain a project, that was written this way. It had no tests of course. No fun. It has not that much to do with you personally being a good dev or not. I think it has to do with the ecosystem encouraging you to do these things. Outputting HTML like that should be declared illegal and should be impossible.
https://github.com/aaviator42/StorX/blob/main/StorX.php in comparison looks much better. It seems it does not output things directly. Everything seems wrapped nicely into methods. One obvious footgun seems to be another global state thing, that I really hope is not a thing in PHP itself:
const THROW_EXCEPTIONS = TRUE;
-
Why you should probably be using SQLite
I'm a huge fan of SQLite! My org's apps use it heavily, often via this simple key-value interface built on sqlite: https://github.com/aaviator42/StorX
Handles tens of thousands of requests a day very smoothly! :)
-
Show HN: My Single-File Python Script I Used to Replace Splunk in My Startup
My org's apps heavily use this simple key-value interface built on sqlite: https://github.com/aaviator42/StorX
There's also a bunch of other purpose-built tiny utilities on that GitHub account.
-
SQLite-based databases on the Postgres protocol? Yes we can
I wrote a small PHP library that gives you a key-value storage interface to SQlite files: https://github.com/aaviator42/StorX
I've been dogfooding for a while by using it in my side projects.
And there's a basic API too, to use it over a network: https://github.com/aaviator42/StorX-API
-
Soul – A SQLite RESTful Server
This is probably ready to be used in production by others, but I wrote a library that gives you a key-value storage interface to SQlite files: https://github.com/aaviator42/StorX
And there's an API too, to use it over a network: https://github.com/aaviator42/StorX-API
libsqlfs
-
The File Filesystem
Closest I found: https://github.com/guardianproject/libsqlfs
> The libsqlfs library implements a POSIX style file system on top of an SQLite database. It allows applications to have access to a full read/write file system in a single file, complete with its own file hierarchy and name space. This is useful for applications which needs structured storage, such as embedding documents within documents, or management of configuration data or preferences. Libsqlfs can be used as an shared library, or it can be built as a FUSE (Linux File System in User Space) module to allow a libsqlfs database to be accessed via OS level file system interfaces by normal applications.
-
Why you should probably be using SQLite
- Use clone file to duplicate the cached data directory to give to individual tests.
One thing I'd like to pursue is to store the Postgres data dir in SQLite [1]. Then, I can reset the "file system" using SQL after each test instead of copying the entire datadir.
[1]: https://github.com/guardianproject/libsqlfs
-
SQLite: 35% Faster Than the Filesystem
Not sure about compression but somebody could probably hack it in an afternoon using this:
https://github.com/guardianproject/libsqlfs
or something similar to check the potential for speed up.
- Libsqlfs: A Posix-style file system on top of an SQLite database
- FUSE based Posix style file system on top of an SQLite database
-
Why the Windows Registry sucks technically (2010)
Maybe there isn't a database engine that explicitly supports file system daya structures, but you could implement a filesystem in the application layer using SQLite as a storage mechanism.
Here's an example of someone doing that very thing.
https://github.com/guardianproject/libsqlfs
- Is it time to remove reiserfs?
- SQLite Archive Files
-
A Future for SQL on the Web
now let's see what it takes to make absurd-fs, where we use https://github.com/guardianproject/libsqlfs to make a filesystem on top of sqlite on top of the File System Access API.
gotta keep ourselves fully looped. ⥀
What are some alternatives?
StorX-API - A REST API for StorX
sqlite-zstd - Transparent dictionary-based row-level compression for SQLite
sqld - LibSQL with extended capabilities like HTTP protocol, replication, and more.
sqlitefs - sqlite as a filesystem
libsql - libSQL is a fork of SQLite that is both Open Source, and Open Contributions.
dirs-rs - a low-level library that provides config/cache/data paths, following the respective conventions on Linux, macOS and Windows
configinator
sqlfs - Sqlite FUSE filesystem with sqlcipher support
zfs-autosnap - Minimal viable ZFS autosnapshot tool
nix-1p - A (more or less) one page introduction to Nix, the language.
roapi - Create full-fledged APIs for slowly moving datasets without writing a single line of code.
certificate-transparency - Auditing for TLS certificates.