Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/ghedamat/ember-cli-deploy-redis-cne
Our very own redis adapter for TheScene
https://github.com/ghedamat/ember-cli-deploy-redis-cne
Last synced: 15 days ago
JSON representation
Our very own redis adapter for TheScene
- Host: GitHub
- URL: https://github.com/ghedamat/ember-cli-deploy-redis-cne
- Owner: ghedamat
- License: mit
- Created: 2015-12-03T04:05:15.000Z (about 9 years ago)
- Default Branch: master
- Last Pushed: 2015-12-03T04:05:32.000Z (about 9 years ago)
- Last Synced: 2024-10-28T17:16:56.963Z (about 2 months ago)
- Language: JavaScript
- Size: 42 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE.md
Awesome Lists containing this project
README
# Ember-cli-deploy-redis-cne
This is a redis-adapter implementation to use [Redis](http://redis.io) with
[ember-cli-deploy](https://github.com/ember-cli/ember-cli-deploy).This was cloned and modified from [here](https://github.com/LevelbossMike/ember-deploy-redis).
Kind of a hack since the feature I'm emulating is partially coming in ember-cli-deploy v0.5.0. Basically, we parse the index file and only store the relevant file references instead of the WHOLE index. This is useful if your server adds a large amount of markup to each route, and you are only interested in the javascript/css sources.
WARNING. Implementation is SPECIFIC to thescene-frontend. No real reason to change it.
### Example:
Instead of an index file, json gets stored like this:
```json
{
"scripts": {
"vendor":"",
"app":".js>"
},
"stylesheets": {
"vendor":"",
"app":".js>"
},
"environment": {
"content":"",
"name":"/config/environment"
}
}
```And then on the server:
```erb
```