Version: 1.9.8
Platform: x86_64
First, install or update to the latest system software.
sudo apt-get update
sudo apt-get install build-essential chrpath libssl-dev libxft-dev
| <?php | |
| /** | |
| * @file | |
| * Contains \Drupal\autoloader_example_d8\Controller\ExampleController. | |
| */ | |
| namespace Drupal\autoloader_example_d8\Controller; | |
| use Drupal\Component\Utility\String; |
| # Idempotent way to build a /etc/hosts file with Ansible using your Ansible hosts inventory for a source. | |
| # Will include all hosts the playbook is run on. | |
| # Inspired from http://xmeblog.blogspot.com/2013/06/ansible-dynamicaly-update-etchosts.html | |
| - name: "Build hosts file" | |
| lineinfile: dest=/etc/hosts regexp='.*{{ item }}$' line="{{ hostvars[item].ansible_default_ipv4.address }} {{item}}" state=present | |
| when: hostvars[item].ansible_default_ipv4.address is defined | |
| with_items: groups['all'] |
| #!/bin/bash | |
| # Reset | |
| sudo rm -rf cnf/settings.php | |
| sudo rm -rf cnf/files | |
| sudo rm -rf builds | |
| sudo rm -rf build | |
| sudo rm -rf src | |
| # Create new project. |
$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'ubuntu/trusty64' is up to date...
==> default: Clearing any previously set forwarded ports...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
| var docRef = app.activeDocument; | |
| cTID = function(s) { return app.charIDToTypeID(s); }; | |
| sTID = function(s) { return app.stringIDToTypeID(s); }; | |
| function newGroupFromLayers(doc) { | |
| var desc = new ActionDescriptor(); | |
| var ref = new ActionReference(); | |
| ref.putClass( sTID('layerSection') ); |
| Security Updates Best Practices | |
| ================================== | |
| The general workflow for running security updates is: | |
| 1. Make sure your local development environment for the site is up-to-date (sync the database from production, if needed) | |
| 1. If the site hasn't been managed for a long time, use `drush rsync @example.prod @example.local` (using the `--exclude` flag to exclude large directories like `sites/default/files`). Then type `git status`. If there are any unmanaged files, add them to version control. | |
| 2. In your local environment, run `drush up --security-only`. | |
| 1. Look at the list of packages that will be updated. Go to each project page on Drupal.org and read the release notes. | |
| 2. You may need to read several versions worth of release notes. You want to see if there are mentions of breaking changes or any changes to features/functionality your site uses. This is usually the most time consuming and difficult part of running the updates. |
| drush php-eval "module_load_install('MYMODULE'); MYMODULE_update_NUMBER();" |
Run natively Unreal Tournament Game Of The Year (GOTY) on Debian system.
UT is not dead! The install process is a bit cumbersome but the game has been published more than 20 years ago! Please let me know how it went for you and if you have any tips, please share :)
And most important, have fun!
(Tested on Debian Bullseye 64bits)
This documentation is destined for drupal.org. Created first as a gist to make initial comments easier. Rewrites and clarifications welcome. Code samples are simplified for clarity. Perhaps a bit too much?
When talking about extensibility, there are several distinct use cases:
The reaction can be anything; outputting a message, sending an email, modifying a related object, etc. Examples: