| server_data = compute.create_server( | |
| 1, | |
| 49 | |
| ).body['server'] | |
| until compute.get_server_details( | |
| server_data['id'] | |
| ).body['server']['status'] == 'ACTIVE' | |
| end |
| rds-modify-db-parameter-group {param-group-name} \ | |
| --parameters="name=character_set_server, value=utf8, method=pending-reboot" \ | |
| --parameters="name=collation_server, value=utf8_general_ci, method=pending-reboot" \ | |
| --parameters="name=tmp_table_size, value={DBInstanceClassMemory/16}, method=pending-reboot" \ | |
| --parameters="name=max_heap_table_size, value={DBInstanceClassMemory/16}, method=pending-reboot" \ | |
| --parameters="name=query_cache_type, value=1, method=pending-reboot" \ | |
| --parameters="name=query_cache_size, value=131072, method=pending-reboot" \ | |
| --parameters="name=table_open_cache, value=2500, method=pending-reboot" \ | |
| --parameters="name=join_buffer_size, value={DBInstanceClassMemory/64}, method=pending-reboot" \ | |
| --parameters="name=thread_cache_size, value={DBInstanceClassMemory/12582880}, method=pending-reboot" \ |
"required_if_attribute" => "The :attribute field is required." to application/language/[language]/validation.php.Define the rule using:
required_if_attribute:[field],[operator],[value]
I wanted to set up one of my Raspberry Pi's as a data dashboard, pushing sensor data to a web interface that's easy to digest. I decided to use Shopify's Dashing framework. Dashing is based on Sinatra, and is pretty lightweight.
Dashing does require Ruby 1.9.3 to run. In addition, it makes use of the execjs gem, which needs to have a working Javascript interpreter available. Originally, I tried to get therubyracer working, but decided to switch over to Node.js when I ran into roadblocks compiling V8.
One warning: The RPi is a very slow system compared with modern multi-core x86-style systems. It's pretty robust, but compiling all this complex software taxes the system quite a bit. Expect that it's going to take at least half a day to get everything going.
| form.awesome { | |
| // Defaults for custom inputs | |
| .custom { | |
| display: inline-block; | |
| width: 16px; | |
| height: 16px; | |
| position: relative; | |
| top: 2px; | |
| border: solid 1px $custom-form-border-color; |
| <?php if ( ! defined('BASEPATH')) exit('No direct script access allowed'); | |
| /* | |
| This is the file unique to each environment type, can be: | |
| config.local.php | |
| config.production.php | |
| config.staging.php | |
| */ | |
| /* |
| #!/bin/bash | |
| # This gist contains pre-commit hooks to prevent you from commiting bad code or to the wrong branch. | |
| # There are six variants that I have built: | |
| # - pre-commit: stops commits to master/main/develop branches. | |
| # - pre-commit-2: also includes a core.whitespace check. | |
| # - pre-commit-3: the core.whitespace check and an EOF-newline-check. | |
| # - pre-commit-4: only the core.whitespace check. | |
| # - pre-commit-5: elixir formatting check. | |
| # - pre-commit-6: prettier formatting check. | |
| # Set the desired version like this before proceeding: |
Putting ImageCache External in front of an image can significantly reduce the load time of images which are associated with CiviCRM. In this test, the time to serve the image ranged from 777ms - 7s when served via CiviCRM, and from 4 - 38ms when adding ImageCache External.
Inspired by questions in How to use Drupal image styles with a civicrm custom field (type file)
It's not uncommon to hear people mention "logging" or "logs" in relation to CiviCRM. There are some different usages of "log":
civicrm_system_log (has an API, only used for IPN data, see CRM_Utils_SystemLogger and forum post).civicrm/admin/setting/misc (mysql logging via triggers). AKA Change Log or Trigger Logging or Detailed Logging.