aoloe / b Goto Github PK

imo, the biggest interest for such a small tool is to use a shared hosting.

installing without docker should be well documented and at least as easy to perform.

currently, there should be a folder for each user at BASE_DIR (in my case the db/ foler).

since the database is the only file needed for each user, we could simply create a database named after the user in db/

list all dead links

we need a pure php way to read the configuration.

we should include a configuration array ((include('../conf/config.php'))()) or an env reader (https://github.com/devcoder-xyz/php-dotenv)

currently it's not easy to understand what index.php does.

extending the router and introducing a tiny template engine might help.

currently the bookmarklet can be reached through its php file and through the router.

only the router way should be kept.

add a path to the router for the json request and use it.

i mean: how can i find it among my repos?

offer a cloud tag or an autocomplete during search.

study (and update?) the merge request that has not been accepted yet.

relying on htaccess feels so 1990... (no logout, hardcoded path to the users list).

i've written a 70 LOC library that can read the file created by htpasswd and renders the widgets for login / logout.

i'll probably publish it as a standalone library and add it to the composer requirements.