Download the PHP package few-far/stacheless without Composer
On this page you can find all versions of the php package few-far/stacheless. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Informations about the package stacheless
Stacheless
Stacheless is a Statamic addon to run CMS data through Eloquent.
Compatibility with Statamic
Stacheless Repositories do not subclass the Statamic as implementation details are different. Instead it implements the interfaces setout by Statamic. A consiquence of this is when Statamic adds new functionality (specifically methods) to their controllers there regularly is no automatic compatibility with the release.
Unfortunately, this is difficult to avoid but this package is frequently updated to support the latest Statamic releases – usually within a few days.
Stacheless | Statamic |
---|---|
1.5.0 | 5.35.0 |
... | |
1.2.0-1.2.8 | 4.42.1 |
1.0.0-1.1.0 | 4.39.0 |
0.1.19 | 4.23.2 |
0.1.13-0.1.18 | 4.0.0-4.15.0 |
0.1.11-0.1.12 | ???-3.4.11 |
0.1.10 | 3.3.48-3.3.49 |
0.1.9 | 3.3.38-3.3.47 |
Features
This addon provides multi-site supported Repository replacements for the file-based Statamic Repositories:
- [x] Entries
- [x] Revisions
- [x] Collections
- [x] Collection Trees
- [x] Navigations
- [x] Navigation Trees
- [X] Global Sets
- [X] Global Variables
- [X] Taxonomies
- [X] Terms
- [X] Assets
- [X] Asset Containers
For our currently usecases we don’t need support for DB driven:
- [ ] Forms
- [ ] Submissions
And for CMS configuration we actually check these into source control and have different images deployed which are config specific so there is no DB support for:
- [ ] Blueprints
- [ ] Fieldsets
For Users, Group and Permissions it’s recommended you use the built in Statamic solution: https://statamic.dev/tips/storing-users-in-a-database
Why?
A fast and scaleable method to store and access Statamic data via a database.
How to Install
How to Use
Optionally chose some types to keep using the Statamic Repositories:
Then publish and run the migrations:
You’re good to go.
For finer control you can publish the package’s config: