We have moved: https://github.com/magnetikonline/linuxmicrosoftievirtualmachines
Due to the popularity of this Gist, and the work in keeping it updated via a Gist, all future updates will take place at the above location. Thanks!
| Why is there no such DataImportHandler thing in ElasticSearch? Uhm, well ... but because: | |
| 1. You should really consider your own scripts | |
| (be it jvm based, perl, ruby, php, nodejs/javascript) | |
| to feed ElasticSearch via bulk indexing: | |
| http://www.elasticsearch.org/guide/reference/java-api/bulk.html | |
| 2. There are two projects doing it already: | |
| * http://code.google.com/p/sql-to-nosql-importer/ | |
| * https://github.com/Aconex/scrutineer (keeps DB in synch with ES or solr!) |
| # | |
| # Slightly tighter CORS config for nginx | |
| # | |
| # A modification of https://gist.github.com/1064640/ to include a white-list of URLs | |
| # | |
| # Despite the W3C guidance suggesting that a list of origins can be passed as part of | |
| # Access-Control-Allow-Origin headers, several browsers (well, at least Firefox) | |
| # don't seem to play nicely with this. | |
| # |
| { | |
| "Description" : "ProjectX scalable stack of frontal nodes", | |
| "Parameters" : { | |
| "InstanceType" : { | |
| "Description" : "Type of EC2 instance to launch", | |
| "Type" : "String", | |
| "Default" : "m1.xlarge" | |
| }, | |
| "SSHKeyName" : { | |
| "Description" : "The EC2 Key Pair to allow SSH access to the instances", |
| # a fairly complete set of deny rules for Magento when running under Nginx webserver | |
| # replicating functionality from the .htaccess files present in a base install. | |
| location ~ "\.htaccess$" { | |
| deny all; | |
| } | |
| location ^~ /app/ { | |
| deny all; | |
| } |
| allprojects { | |
| // Marker Task to enable findbugs. | |
| task findbugs( | |
| group: "Verification", | |
| description: """Marker task to enabled findbugs. Findbugs is by default | |
| disabled. E.g. ( ./gradlew findbugs build )""" | |
| ) | |
| } | |
| subprojects { |
We have moved: https://github.com/magnetikonline/linuxmicrosoftievirtualmachines
Due to the popularity of this Gist, and the work in keeping it updated via a Gist, all future updates will take place at the above location. Thanks!
Follow each step manually and any bugs during (resource) model instantiation will become obvious.
Since many people find model and resource model instantiation to be one of the more challenging things in Magento 1, these are all the steps Magento does to resolve the factory name to the real PHP class name.
To debug, simply follow each step manually until you find a non-match. This works really well in my experience.
Less guessing, more and faster results.
In the examples I use a factory name of "example/thing".
Open $ vim /etc/default/grub then add elevator=noop next to GRUB_CMDLINE_LINUX_DEFAULT. Run $ update-grub and $ cat /sys/block/sda/queue/scheduler to be sure that noop is being used:
$ vim /etc/default/grub
$ update-grub
$ cat /sys/block/sda/queue/scheduler
[noop] deadline cfq
| <script> | |
| // inject inlined constants | |
| angular.module('app.constants', []) | |
| .constant('contextPath', '${pageContext.request.contextPath}'); | |
| </script> |