PHPackages                             html\_first/atla-as - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. html\_first/atla-as

ActiveLibrary

html\_first/atla-as
===================

php file system routing, file serving, connection and SQL DB querying library

2.0.0(1y ago)019MITPHPPHP >=8.0.0

Since Nov 15Pushed 1y ago1 watchersCompare

[ Source](https://github.com/hakimjazuli/atlaAS)[ Packagist](https://packagist.org/packages/html_first/atla-as)[ RSS](/packages/html-first-atla-as/feed)WikiDiscussions main Synced 1mo ago

READMEChangelogDependenciesVersions (8)Used By (0)

atlaAS
======

[](#atlaas)

- php:

> - [file system routing](https://github.com/hakimjazuli/atlaAS/blob/main/README.md#routing);

> - [setting up middleware](https://github.com/hakimjazuli/atlaAS/blob/main/README.md#middlewares);

> - [file serving](https://github.com/hakimjazuli/atlaAS/blob/main/README.md#serving-files);

> - [connection and SQL DB querying library](https://github.com/hakimjazuli/atlaAS/blob/main/README.md#sql-query);

- this library is designed to be used in the conjuction with our client side HATEOAS sister

library *[https://github.com/hakimjazuli/atlaAS\_client](https://github.com/hakimjazuli/atlaAS_client)* in mind;

- however you can still uses it as Backend normally for, like:

> - building REST json api backend: using our "*HtmlFirstatlaASMiddlewares\_Middleware*",

> to set up header default header on `/api/**` routes;

> - serving files: using our "*HtmlFirstatlaASRouter\_MapResources;*";

> - building HATEOAS backend for htmx/other HATEOAS library/framework;

> > - in fact you might be surprissed how good File System Routing might fare for

> > htmx/other HATEOAS library due to the nature of atlaAS code splitting in general;

> >

> > > - automatic routes setup;

> > > - no need to register it using framework class instances first;

> >

> > - in htmx use case, you can even opt out from using `hx-select` and/or `hx-target` as

> > the returned html needed are easily split per routes file;

> > - not to mention how php is a natural templating language for html \_(well... if

> > there's any more natural language, php is still the most easiest to set up, "there's no setup", just use `?>` to enter front end and `