opdavies/oliverdavies.uk
1
0
Fork 0
Code Issues Pull requests Actions Packages Projects Releases Wiki Activity

Add other times

Browse source
This commit is contained in:
Oliver Davies 2017-03-19 10:03:16 +00:00
parent 08e4515f12
commit 517972fa1f
3 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
source/_talks/deploying-php-with-fabric.md
View file

@ -6,7 +6,7 @@ slides: ~
slides_embed: ~
tags: [meetup, php, fabric]
events:
- { id: nomad_php, date: '2017-04-20', time: '19:00 CEST' }
- { id: nomad_php, date: '2017-04-20', time: '19:00 (CET)' }
---
You’ve built your application, and now you just need to deploy it. There are various ways that this could be done – from (S)FTP, to SCP and rsync, to running commands like “git pull” and “composer install” directly on the server (not recommended).

2
source/_talks/getting-your-data-into-drupal-8.md
View file

@ -7,7 +7,7 @@ slides:
tags: [drupalcamp, migration, drupal-8]
events:
- { id: drupal-bristol, date: '2017-01-18' }
- { id: drupalcamp-london-17, date: '2017-03-04' }
- { id: drupalcamp-london-17, date: '2017-03-04', time: '12:05 - 12:50' }
---
If you’ve moved a site from Drupal 6 to 7, the chances are that you’ve either used the upgrade path to update your old site in-place, or you built a new site from scratch and used the Migrate module from contrib to migrate your data from the old database.

2
source/_talks/test-driven-drupal-simpletest-phpunit.md
View file

@ -6,7 +6,7 @@ slides:
embed: <script async class="speakerdeck-embed" data-id="4f12722ed400468b93ebb32a23b3c757" data-ratio="1.37081659973226" src="//speakerdeck.com/assets/embed.js"></script>
tags: [drupalcamp, simpletest, phpunit, testing]
events:
- { id: drupalcamp-london-17, date: '2017-03-04' }
- { id: drupalcamp-london-17, date: '2017-03-04', time: '16:15 - 17:00' }
---
Testing is important. Why? It allows developers to add new features and edit and refactor existing code without the worry of adding regressions, reduces the reliance on manual testing to discover bugs, and by taking a test driven approach, your implementation code is leaner as you only write what is needed for your tests to pass.