A short Show and Tell presentation by Herb Miller, Bobbing Wide outlining his work to analyse the effect of configuration changes on server response times.
First presented at Cheltenham WordPress Meetup ( #WPChelt ) on 31st March 2021
Git and GitHub are tools that software engineers use to collaborate on code and track changes over time. While primarily for software development, GitHub can also be used as a project management tool for any team. Key terms used in GitHub include repositories (folders for projects), branches (versions of code), commits (changes to code), and pull requests (requests to merge changes). As a non-technical professional, understanding these basic GitHub concepts and being able to engage teams there will help facilitate communication and progress on shared work. The document recommends following specific repositories at the company to stay informed on relevant projects.
Git basics, Team Workflows (Ciro Miranda)Ciro Miranda
The document discusses different version control workflows including local, centralized, and distributed systems. It focuses on Git and describes common Git commands like clone, status, add, commit, pull and push. Different Git workflows for teams are presented, including feature branches to isolate work and release branches to integrate completed features. The Git Flow model is described using main branches for production (master) and integration (develop), plus branches for features, releases and hotfixes.
This document outlines how to setup an agile development environment using test-driven development (TDD), behavior-driven development (BDD), and continuous integration (CI). It recommends using GitHub for source code management, Roboelectric for TDD, Calabash for BDD, and Jenkins for CI. Implementing these agile elements can provide benefits like fewer errors, faster feedback, and built-in regression testing.
This document appears to be notes from a product manager tracking multiple projects, issues, and tasks. It includes sections for a website project with various tasks and bugs assigned as "todo", "in progress", "in review", and "done". Another section discusses developing a master tag and task #216 being completed. Overall it provides a high-level overview of a product manager's work tracking projects, tasks, bugs and issues across versions.
A Tale of 3 CLIs - Angular 2, Ember, and ReactTracy Lee
Ember-CLI, Angular-CLI, and Create-React-App are necessities to web development, and many who have not had exposure to such wonderful technologies wonder what they are actually missing. This talk will show you how easy it is to scaffold up all 3 projects in less than 30 minutes, how to shave days, even weeks, off your development cycle, and why you should choose convention over configuration.
This document provides an overview and agenda for introducing GitLab tools. It discusses trends in modern development like increased use of open source tools and continuous integration/deployment. GitLab is presented as a one platform solution that provides version control, issue tracking, code review, CI/CD pipelines, and other DevOps tools. Key benefits of GitLab like open source contributions and frequent releases are outlined. Upcoming features in GitLab 11 like CI pipelines in the web IDE and license management are previewed. The presentation concludes with a Q&A and information on how to get a GitLab cheat sheet.
Wrapped in a single session, you'll find the concepts and techniques that convert the average Git practitioner into a master of the craft. We'll go from technical topics like "efficient conflict resolution" and "effective code cleanup," to the often-asked "how to handle project dependencies with Git" and "how to manage massive repositories." And much more.
Git and GitHub are tools that software engineers use to collaborate on code and track changes over time. While primarily for software development, GitHub can also be used as a project management tool for any team. Key terms used in GitHub include repositories (folders for projects), branches (versions of code), commits (changes to code), and pull requests (requests to merge changes). As a non-technical professional, understanding these basic GitHub concepts and being able to engage teams there will help facilitate communication and progress on shared work. The document recommends following specific repositories at the company to stay informed on relevant projects.
Git basics, Team Workflows (Ciro Miranda)Ciro Miranda
The document discusses different version control workflows including local, centralized, and distributed systems. It focuses on Git and describes common Git commands like clone, status, add, commit, pull and push. Different Git workflows for teams are presented, including feature branches to isolate work and release branches to integrate completed features. The Git Flow model is described using main branches for production (master) and integration (develop), plus branches for features, releases and hotfixes.
This document outlines how to setup an agile development environment using test-driven development (TDD), behavior-driven development (BDD), and continuous integration (CI). It recommends using GitHub for source code management, Roboelectric for TDD, Calabash for BDD, and Jenkins for CI. Implementing these agile elements can provide benefits like fewer errors, faster feedback, and built-in regression testing.
This document appears to be notes from a product manager tracking multiple projects, issues, and tasks. It includes sections for a website project with various tasks and bugs assigned as "todo", "in progress", "in review", and "done". Another section discusses developing a master tag and task #216 being completed. Overall it provides a high-level overview of a product manager's work tracking projects, tasks, bugs and issues across versions.
A Tale of 3 CLIs - Angular 2, Ember, and ReactTracy Lee
Ember-CLI, Angular-CLI, and Create-React-App are necessities to web development, and many who have not had exposure to such wonderful technologies wonder what they are actually missing. This talk will show you how easy it is to scaffold up all 3 projects in less than 30 minutes, how to shave days, even weeks, off your development cycle, and why you should choose convention over configuration.
This document provides an overview and agenda for introducing GitLab tools. It discusses trends in modern development like increased use of open source tools and continuous integration/deployment. GitLab is presented as a one platform solution that provides version control, issue tracking, code review, CI/CD pipelines, and other DevOps tools. Key benefits of GitLab like open source contributions and frequent releases are outlined. Upcoming features in GitLab 11 like CI pipelines in the web IDE and license management are previewed. The presentation concludes with a Q&A and information on how to get a GitLab cheat sheet.
Wrapped in a single session, you'll find the concepts and techniques that convert the average Git practitioner into a master of the craft. We'll go from technical topics like "efficient conflict resolution" and "effective code cleanup," to the often-asked "how to handle project dependencies with Git" and "how to manage massive repositories." And much more.
How do you choose a git workflow that increases productivity and reduces the friction of your team? What are the battle tested practices of successful teams that moved to git? How is git used inside Atlassian?
As you might have heard git has many compelling features and has gained incredible momentum in the industry at large. Yet understanding how an enterprise team can adopt it can be daunting. The presentation aims to help answer these questions and more:
- Available collaboration models when using a distributed version control system like git
- Branching models that foster and enhance parallel development
- Emerging code best practices and choices that can be safely adopted when migrating to git
- How Continuous Integration changes when your team embraces git
Over the past few years, Gradle has become a popular build tool in the JVM space. This is not surprising, considering the power and the features it brings, compared with its competitors. However, one thing Gradle lacks is history and the collective knowledge at the same level of other alternatives: how does one organize a Gradle project in an ‘idiomatic’ fashion?
We feel that we’ve put together a decent build pipeline for each of our microservices over the years, and each one starts with their build.gradle file(s). We’d like to share it, although we’re not sure if it’s the ‘correct’ way.
In this talk, we’ll walk through a sample project structure and build process. We’ll discuss the various checks and tools we use (e.g. Sonar, CodeNarc, Jenkins) at each step of the build. We’ll explain how each of the components in the process work for us, and share samples of our Groovy scripts. Most importantly, though, we’d like to hear what the audience are using in their builds!
Flex is an open source framework for building interactive web applications that run consistently across browsers and platforms. It uses MXML for declarative UI layouts and ActionScript for client logic. Flex includes a rich library of predefined UI controls like datagrids and charts. It can be used for both web and desktop development via AIR, adding features like file access.
Kathleen Vignos discusses migrating the 17 blogs on WIRED.com into a single WordPress install. Some issues with the separate blogs included separate logins, upgrades, and deployments for each one. The solution, called Project Pangea, involved purging unnecessary data, updating taxonomies, exporting and importing content using custom scripts, and adding post metadata and helpers. The results were easier administration, deployment, and development along with a single REST API and no need for RSS aggregation.
This document discusses service monitoring, server monitoring, and custom monitoring using various tools. It introduces Pingdom and Pagerduty for service monitoring to check if a service is working. New Relic is presented for server monitoring of CPU, disk, memory, etc, with Slack/email for alerts. Custom monitoring with Datadog is also covered to define custom metrics and thresholds according to requirements, with Pagerduty/email for alerts. The presenter encourages not being afraid of monitoring and building it incrementally like Lego blocks while adapting to application changes.
This document provides an overview of Git and how to use it. It explains why Git is useful for collaboration, provides an analogy comparing Git to smartphone updates, and defines key Git terms and functions including cloning a repository, pulling and pushing changes, commits, and repositories. It also introduces common Git tools like GitHub, Bitbucket, and SourceTree and includes basic instructions on installing Git and cloning a repository.
The document discusses various Git branching strategies, including:
- Common concepts like branches, merges, and pull requests
- Popular workflows like GitHub Flow and branching per platform/release
- A case study of Telenet's workflow of using long-running release branches merged from master for testing before production deployment
- Best practices like using pull requests for code reviews, keeping long-running branches stable, and ensuring features are fully tested before being merged.
These slides are about my personal experience from creating a continuous delivery process in the last 2 years.
The main focus lies in the tools I used and my experience with them.
The document discusses several common Git workflows:
- The Basic/Centralized Workflow is the most basic, similar to SVN, with a single master branch and all changes committed directly to it.
- The Feature Branch Workflow involves branching by feature, with each developer working on their own branch before merging into master via a pull request. This avoids broken code and allows code review.
- The Gitflow Workflow manages features, releases, and hotfixes across main branches like master and develop, plus feature, release, and hotfix branches. It is more complex but provides more structure than the Feature Branch.
- The Forking Workflow differs in that there is no central repository - each developer has their own public server
This document provides an overview of Git workflow in agile development. It introduces basic Git commands like git init, git add, git commit, git branch, git checkout, and git merge. It then demonstrates how these commands can be used in a typical workflow involving feature branches, hotfix branches, and merging changes back into the master branch for deployment. Key steps shown include creating feature branches off of develop, pushing changes to those branches, merging the feature branches back into develop once complete, creating hotfix branches off of master as needed, and merging those hotfixes back to both master and develop.
This document discusses using Vagrant, GitHub, and Heroku together for PHP development and deployment. It recommends using the Scotchbox Vagrant box for local development. Changes made in GitHub will trigger automatic deploys to Heroku using its pipeline feature to create review apps. The Heroku app is built from the code in the GitHub repository. Additional topics covered include using Laravel, continuous integration/deployment, and integrating a PHP app with Salesforce.
In this presentation, Dmitriy Zaporozhets and Job van der Voort talk about the GitLab Release process and give a guided tour of the new features in 8.4. You can find out why GitLab users always know when the next release is, and how they know what's coming next.
This document discusses how to contribute to the open source Impala project. It provides information on the types of contributions accepted, including code, bug reports, documentation and extensions. It outlines the contribution guidelines and code review process using Gerrit. The mailing lists for developers and users are also listed. The document encourages starting small with contributions and getting feedback before undertaking large changes.
GitLab 8.5 Highlights and Step-by-step tutorialHeather McNamee
In this webcast, learn how to collaborate with GitLab. You'll see new features from GitLab 8.5 in practice. Check out our blog for more information. https://about.gitlab.com/2016/02/26/webcast-wrapup/
The document compares features of GitHub and GitLab version control software. It notes that both support code repositories, issue tracking, pull requests, and project web pages. Additionally, it states that GitLab offers integrated continuous integration and container registry features. The document promotes GitLab as having CI integrated directly with the code repository, hassle-free pipeline creation, a seamless workflow, an open source business model, rapid growth, and complete transparency.
This document discusses using Git to develop code. It begins by motivating the use of Git over the traditional client view by noting that Git allows for code to be backed up, easily shared, and developed in branches without destroying work. It then outlines how Git can provide snapshots of work, create branches for ideas, undo changes, share branches, and commit freely without others seeing. The document briefly introduces the Git object model and suggests a simple Git workflow and using git-p4 to integrate with a Perforce server. It cautions that rebasing rewrites history and can cause issues for downstream branches.
The iOS team at The Washington Post needed to grow quickly and maintain sanity (and shipping quality). Here are some of the key workflow tools that we used.
With CollabNet TeamForge it is now possible to use feature branch workflow in addition to standard gerrit workflow to work on your changes. In this presentation you will learn how it works, why we have decided to implement it, how was it implemented and what were the choices we have made and challenges along the way.
Building A Distributed Build System at Google Scale (StrangeLoop 2016)Aysylu Greenberg
It's hard to imagine a modern developer workflow without a sufficiently advanced build system: Make, Gradle, Maven, Rake, and many others. In this talk, we'll discuss the evolution of build systems that leads to distributed build systems. Then, we'll dive into how we can build a scalable system that is fast and resilient, with examples from Google. We'll conclude with the discussion of general challenges of migrating systems from one architecture to another.
This document discusses version control and Git. It explains that version control allows developers to maintain stability and continuity in websites/applications by saving versions. Git tracks differences between commits, is distributed for less server overhead, and makes complex workflows easier to manage. The document provides examples of basic Git commands and realistic workflows for development, deployment, using branches, merging, and other "cool stuff" like hooks, stash, and reset. Resources are also included for learning more about Git vs Subversion and deploying with Git.
How do you choose a git workflow that increases productivity and reduces the friction of your team? What are the battle tested practices of successful teams that moved to git? How is git used inside Atlassian?
As you might have heard git has many compelling features and has gained incredible momentum in the industry at large. Yet understanding how an enterprise team can adopt it can be daunting. The presentation aims to help answer these questions and more:
- Available collaboration models when using a distributed version control system like git
- Branching models that foster and enhance parallel development
- Emerging code best practices and choices that can be safely adopted when migrating to git
- How Continuous Integration changes when your team embraces git
Over the past few years, Gradle has become a popular build tool in the JVM space. This is not surprising, considering the power and the features it brings, compared with its competitors. However, one thing Gradle lacks is history and the collective knowledge at the same level of other alternatives: how does one organize a Gradle project in an ‘idiomatic’ fashion?
We feel that we’ve put together a decent build pipeline for each of our microservices over the years, and each one starts with their build.gradle file(s). We’d like to share it, although we’re not sure if it’s the ‘correct’ way.
In this talk, we’ll walk through a sample project structure and build process. We’ll discuss the various checks and tools we use (e.g. Sonar, CodeNarc, Jenkins) at each step of the build. We’ll explain how each of the components in the process work for us, and share samples of our Groovy scripts. Most importantly, though, we’d like to hear what the audience are using in their builds!
Flex is an open source framework for building interactive web applications that run consistently across browsers and platforms. It uses MXML for declarative UI layouts and ActionScript for client logic. Flex includes a rich library of predefined UI controls like datagrids and charts. It can be used for both web and desktop development via AIR, adding features like file access.
Kathleen Vignos discusses migrating the 17 blogs on WIRED.com into a single WordPress install. Some issues with the separate blogs included separate logins, upgrades, and deployments for each one. The solution, called Project Pangea, involved purging unnecessary data, updating taxonomies, exporting and importing content using custom scripts, and adding post metadata and helpers. The results were easier administration, deployment, and development along with a single REST API and no need for RSS aggregation.
This document discusses service monitoring, server monitoring, and custom monitoring using various tools. It introduces Pingdom and Pagerduty for service monitoring to check if a service is working. New Relic is presented for server monitoring of CPU, disk, memory, etc, with Slack/email for alerts. Custom monitoring with Datadog is also covered to define custom metrics and thresholds according to requirements, with Pagerduty/email for alerts. The presenter encourages not being afraid of monitoring and building it incrementally like Lego blocks while adapting to application changes.
This document provides an overview of Git and how to use it. It explains why Git is useful for collaboration, provides an analogy comparing Git to smartphone updates, and defines key Git terms and functions including cloning a repository, pulling and pushing changes, commits, and repositories. It also introduces common Git tools like GitHub, Bitbucket, and SourceTree and includes basic instructions on installing Git and cloning a repository.
The document discusses various Git branching strategies, including:
- Common concepts like branches, merges, and pull requests
- Popular workflows like GitHub Flow and branching per platform/release
- A case study of Telenet's workflow of using long-running release branches merged from master for testing before production deployment
- Best practices like using pull requests for code reviews, keeping long-running branches stable, and ensuring features are fully tested before being merged.
These slides are about my personal experience from creating a continuous delivery process in the last 2 years.
The main focus lies in the tools I used and my experience with them.
The document discusses several common Git workflows:
- The Basic/Centralized Workflow is the most basic, similar to SVN, with a single master branch and all changes committed directly to it.
- The Feature Branch Workflow involves branching by feature, with each developer working on their own branch before merging into master via a pull request. This avoids broken code and allows code review.
- The Gitflow Workflow manages features, releases, and hotfixes across main branches like master and develop, plus feature, release, and hotfix branches. It is more complex but provides more structure than the Feature Branch.
- The Forking Workflow differs in that there is no central repository - each developer has their own public server
This document provides an overview of Git workflow in agile development. It introduces basic Git commands like git init, git add, git commit, git branch, git checkout, and git merge. It then demonstrates how these commands can be used in a typical workflow involving feature branches, hotfix branches, and merging changes back into the master branch for deployment. Key steps shown include creating feature branches off of develop, pushing changes to those branches, merging the feature branches back into develop once complete, creating hotfix branches off of master as needed, and merging those hotfixes back to both master and develop.
This document discusses using Vagrant, GitHub, and Heroku together for PHP development and deployment. It recommends using the Scotchbox Vagrant box for local development. Changes made in GitHub will trigger automatic deploys to Heroku using its pipeline feature to create review apps. The Heroku app is built from the code in the GitHub repository. Additional topics covered include using Laravel, continuous integration/deployment, and integrating a PHP app with Salesforce.
In this presentation, Dmitriy Zaporozhets and Job van der Voort talk about the GitLab Release process and give a guided tour of the new features in 8.4. You can find out why GitLab users always know when the next release is, and how they know what's coming next.
This document discusses how to contribute to the open source Impala project. It provides information on the types of contributions accepted, including code, bug reports, documentation and extensions. It outlines the contribution guidelines and code review process using Gerrit. The mailing lists for developers and users are also listed. The document encourages starting small with contributions and getting feedback before undertaking large changes.
GitLab 8.5 Highlights and Step-by-step tutorialHeather McNamee
In this webcast, learn how to collaborate with GitLab. You'll see new features from GitLab 8.5 in practice. Check out our blog for more information. https://about.gitlab.com/2016/02/26/webcast-wrapup/
The document compares features of GitHub and GitLab version control software. It notes that both support code repositories, issue tracking, pull requests, and project web pages. Additionally, it states that GitLab offers integrated continuous integration and container registry features. The document promotes GitLab as having CI integrated directly with the code repository, hassle-free pipeline creation, a seamless workflow, an open source business model, rapid growth, and complete transparency.
This document discusses using Git to develop code. It begins by motivating the use of Git over the traditional client view by noting that Git allows for code to be backed up, easily shared, and developed in branches without destroying work. It then outlines how Git can provide snapshots of work, create branches for ideas, undo changes, share branches, and commit freely without others seeing. The document briefly introduces the Git object model and suggests a simple Git workflow and using git-p4 to integrate with a Perforce server. It cautions that rebasing rewrites history and can cause issues for downstream branches.
The iOS team at The Washington Post needed to grow quickly and maintain sanity (and shipping quality). Here are some of the key workflow tools that we used.
With CollabNet TeamForge it is now possible to use feature branch workflow in addition to standard gerrit workflow to work on your changes. In this presentation you will learn how it works, why we have decided to implement it, how was it implemented and what were the choices we have made and challenges along the way.
Building A Distributed Build System at Google Scale (StrangeLoop 2016)Aysylu Greenberg
It's hard to imagine a modern developer workflow without a sufficiently advanced build system: Make, Gradle, Maven, Rake, and many others. In this talk, we'll discuss the evolution of build systems that leads to distributed build systems. Then, we'll dive into how we can build a scalable system that is fast and resilient, with examples from Google. We'll conclude with the discussion of general challenges of migrating systems from one architecture to another.
This document discusses version control and Git. It explains that version control allows developers to maintain stability and continuity in websites/applications by saving versions. Git tracks differences between commits, is distributed for less server overhead, and makes complex workflows easier to manage. The document provides examples of basic Git commands and realistic workflows for development, deployment, using branches, merging, and other "cool stuff" like hooks, stash, and reset. Resources are also included for learning more about Git vs Subversion and deploying with Git.
Be a Happier Developer with Git / Productive Team #gettinggitright Shunsuke (Sean) Osawa
This document provides information about a conference session on Git and productive teams, including:
1. An agenda for the session that covers happier developers, productive teams, and a product called Stash.
2. Information about WiFi access and instructions to fill out a survey for prizes.
3. Details on pricing plans for Stash, ranging from free basic versions to paid plans for more users.
This document provides an introduction to using Git version control. It discusses key Git concepts like distributed version control, objects in Git like blobs and trees, and commands like add, commit, branch, merge, rebase, fetch and push. The introduction includes an agenda, sources for further information, and demos several Git workflows and commands.
Thorben Lindhauer: Live Coding: Zeebe - Camunda Day San Franciscocamunda services GmbH
Zeebe is the next generation workflow engine developed by Camunda. It takes workflow automation to an entirely new level, with massive throughput and infinite horizontal scalibility. In this session, Zeebe core developer Thorben Lindhauer will demonstrate how to get started with Zeebe.
At UCR, automation is a part of everything we do. When designing a new architecture and the set of new processes for our new Java based development environment we came up with a set of continuous integration and deployment tools to enable our developers to write and deploy their own applications in a flexible and secure environment.
The New Renaissance of JavaScript - SMX London 2019Onely
This document contains advice from a presentation on JavaScript rendering and SEO. It recommends:
1) Being mindful that Google has not updated its tools yet to reflect improvements in JavaScript rendering.
2) Avoiding client-side JavaScript rendering and instead using server-side rendering or static sites, as client-side rendering can cause indexing issues.
3) Introducing and sticking to a web performance budget and limiting client-side JavaScript for reasons like performance, the crawler's technical limitations, and compatibility with other search engines and social media platforms.
The New Renaissance of JavaScript - SMX London 2019Onely
This document contains advice from a presentation on JavaScript rendering and SEO. It recommends: (1) Being mindful that Google has not fully updated its tools to the latest JavaScript rendering capabilities. (2) Avoiding client-side JavaScript rendering and instead implementing server-side rendering or static sites to ensure content is crawlable. (3) Introducing and adhering to web performance budgets and limiting client-side JavaScript to improve performance for users and search engines.
Fun with Github webhooks: verifying Signed-off-byJeff Squyres
An overview of an afternoon project I noodled around with one day to play with Ruby and Github Webhooks. I surprised myself by creating something somewhat actually useful.
Presentation given to the Kentucky Open Source Society (KyOSS) on July 8, 2015.
This document summarizes techniques for optimizing image delivery for fast page loads, including: reducing image quality, using optimized formats like WebP and SVG, sizing images appropriately, and lazy loading images below the fold. It provides examples of each technique and data on their impact, such as median savings of 2.83 seconds and 419KB from quality optimization. Recommended tools for optimizing and measuring performance are also listed. The overall message is that with the right optimizations, images can be both beautiful and fast loading.
Git is a version control system that allows developers to have multiple versions of codebases and easily revert changes. Github is a website that hosts git repositories on remote servers, facilitating code sharing among teams through a graphical user interface. The document provides instructions on configuring git and connecting it to Github repositories, as well as describing basic workflows for branching, merging, rebasing, and resolving conflicts when integrating changes.
Git is a version control system that allows developers to have multiple versions of codebases and easily revert changes. Github is a website that hosts git repositories on remote servers, facilitating code sharing among teams through a graphical user interface. The document provides instructions on configuring git and connecting it to Github repositories, as well as describing basic workflows for branching, merging, rebasing, and resolving conflicts when integrating changes.
Git is a source control management system that allows developers to work collaboratively by controlling versions from a central repository. Each team member has a local copy of the repository. Commands are used to upload and download changes from the central repository. Best practices for collaboration include using branches like develop and feature branches, and following a roadmap of branching, testing, merging into develop, and releasing to production.
The document discusses optimizing images for fast loading on mobile websites. It recommends 4 simple image optimizations: 1) reducing image quality to 85%, 2) using efficient formats like JPEG, PNG and WebP, 3) sizing images appropriately for the viewport, and 4) lazy loading images below the fold. Implementing these techniques, such as optimizing quality, format, sizing and lazy loading, can significantly improve page load speeds and reduce data usage.
VelocityConf EU 2013 - Turbocharge your mobile web apps by using offline Jan Jongboom
The document is a presentation about turbocharging mobile web apps. It discusses caching assets like CSS and images to make pages load faster. It introduces ServiceWorkers as a new way to control caching without breaking the web. It also discusses using IndexedDB and libraries like PouchDB to cache app content and sync data offline. The key lessons are to cache the shell assets, cache app content separately using tools like IndexedDB, and use an existing library for data syncing across devices.
The document discusses automated deployments using SaltStack and Docker containers. It describes how Docker can be used to build application environments in isolated containers with defined dependencies. This allows services to be easily started and stopped, and experiments with a low barrier for entry. The document outlines how to separate concerns between the host system and application services using Docker images. It also discusses Twelve-Factor App methodology for building applications and binding application ports, as well as using environment variables for configuration.
A Peek Behind the Curtain: Managing the Kubernetes Contributor CommunityBob Killen
The Kubernetes community is a vibrant beacon in open source. It takes a village to enable a city of contributors doing what they do best. There are a lot of fun stories and lessons to be shared from helping out the community. One lesson is taken straight from the Kubernetes project itself: declarative config management. Most aspects of the community are managed using declarative configs. Adding a new SIG, GitHub org member, and even Slack channel, involves updating and PRing a change into one of the many Kubernetes repos. Adopting this methodology provides the community the means to self-manage itself. Join us as we journey through the many bits of community automation and weigh the merits of automating every aspect of our community.
SCALE 18x 2020
SpringOne Platform 2017
Marcin Grzejszczak, Pivotal; Cora Iberkleid, Pivotal
"“I have stopped counting how many times I’ve done this from scratch” - was one of the responses to the tweet about starting the project called Spring Cloud Pipelines. Every company sets up a pipeline to take code from your source control, through unit testing and integration testing, to production from scratch. Every company creates some sort of automation to deploy its applications to servers. Enough is enough - time to automate that and focus on delivering business value.
In this presentation we’ll go through the contents of the Spring Cloud Pipelines project. We’ll start a new project for which we’ll have a deployment pipeline set up in no time. We’ll deploy to Cloud Foundry and check if our application is backwards compatible so that we can roll it back on production."
Similar to WordPress - Whats going on in the server? (20)
An annotated version of the poem entitled "My Favourite Block" presented / performed as a lightning talk at the Portsmouth WordPress Meetup on 15th May 2019.
Posts for the original poem and the annotated version are available from https://herbmiller.me
A brief introduction to the WordPress block editor’s features and where to find information about WordPress blocks you might want to use.
A lightning talk by Herb Miller at the WordPress Portsmouth Meetup 15th May 2019
This document discusses doing a site health check to check the PHP version a WordPress site is running. It recommends using the Site Health Check plugin to determine the PHP version and check for any issues. If the PHP version is out of date, the document provides steps to test for compatibility issues, update the version with the hosting provider, and migrate custom code and plugins to newer PHP versions. It also discusses resources for PHP updates and encourages contacting hosting providers for assistance.
Yoast SEO Workshop - WordPress Portsmouth Meetup 16 Jan 2019 Herb Miller
WordPress Portsmouth session on website search engine optimisation (SEO). Find out from the SEO experts at Yoast how to get your cat's 7,000 word post about lasagna and other pastas to rank higher in Google for both mobile and desktop searches.
WordPress Portsmouth meetup 20 dec 2018 v0.0.2Herb Miller
The document summarizes an agenda for a WordUp Pompey meetup on December 20th 2018. It includes details on meetup activities from 19:00-20:30 including introductions, Lean Coffee and Lightning Talks, and wrap up. It also lists sponsors RedIT and 34SP and outlines WordUp Pompey meetup plans for 2019 to take place monthly on the 4th Tuesday at Technopole in Portsmouth.
The document summarizes an agenda for a WordPress meetup event. It includes details on networking, presentations on switching from one theme to another, and questions and answers. It also lists sponsors and provides information on the venue, pizza sponsor, and social event after the meetup.
This document provides an agenda and details for a WordUp Pompey meetup on July 19th 2018. The agenda includes networking from 19:00-19:30, a problem solving clinic from 19:30-20:45, and a wrap up from 20:45-21:00. Following the meetup, there will be a social at Sovereigns pub from 21:00 onwards. The document also lists upcoming WordPress release dates and events, and provides a discount code for a web hosting company for WordUp Pompey members.
Introduction to Accessibility- with Abha followed by question and answer session. Difficult questions being deferred for Graham to answer.
Abha from @nonstopnewsuk will give an introduction to web accessibility. She will show how the web can present barriers to some users’ experience and participation, give an insight into some of the tools available to help those with accessibility needs, highlight the work of the WordPress Accessibility team, and explore with attendees how they can learn more about making their sites more accessible.
Graham Armfield’s presentation on accessibility tools will lead on from this and now be held on a new date later this year.
Agenda for the WordPress Portsmouth Meetup with Tim Nash from 34sp.com on the subject of "Website security and recovering your site from a hack".
A session to help take the fear out of being hacked, provide some practical tips for how to better protect your website and some of the steps you can take to recover.
The document announces a WordUp Pompey meetup on April 18th to discuss GDPR with a talk from @NonStopNewsUK followed by Q&A and networking. The agenda includes informal discussions from 19:00-19:30, the GDPR talk from 19:30-20:45, and wrapping up at 21:00 with socializing at Sovereigns. Upcoming WordPress events include WordCamp Belfast from May 25-27 and the 15th WordPress anniversary on May 27.
The document announces a WordUp Pompey networking event on March 15th 2018. The agenda includes networking from 19:00-19:30 to discuss problems, a clinic from 19:30-20:45, and a wrap up at 21:00 followed by socializing at a local venue. Attendees are asked to provide feedback on updating the title and posts on the WordUp Pompey website and reviewing the privacy policy. Future events are announced for April, May, and June on GDPR, security, and an unspecified topic. News items mention the lack of a WordPress 5.0 plan and a bug fix being merged. The document concludes by thanking the venue sponsor and providing information about the upcoming changes
WordUp Pompey - 22nd Feb 2018 - GutenbergHerb Miller
A new block editor is being built as a feature plugin for potential inclusion in WordPress 5.0. The product is still very much in development. It appears to favour new installations.The absence of a migration plan for existing content is a major concern to some people, especially developers, who are concerned that many sites will be broken. Is this a risk you're prepared to accept?
Slides from the the first Portsmouth WordPress Meetup held at the Technopole on 18th January 2018. See https://www.wp-pompey.org.uk/meetup/wordup-pompey-reboot/
Responsive web design: WordUp Pompey! Feb-2012Herb Miller
A quick look at building responsive websites with an Artisteer theme as the base theme, by Herb Miller, of Bobbing Wide and [oik]-plugins
Slides from WordUp Pompey, held on February 23rd 2012. See also
http://wp-pompey.org.uk/wordup-pompey-wordpress-meetup-for-portsmouth/
An overview of shortcodes for WordPress: what, why and how? by Herb Miller, of Bobbing Wide and [oik]-plugins
Slides from WordUp Pompey, held on February 23rd 2012. See also
http://wp-pompey.org.uk/wordup-pompey-wordpress-meetup-for-portsmouth/
A short set of slides suggesting that WordPress is not just a blog and it's not just for Christmas. First presented at 4N Petersfield - 20th December 2011, then as an afterthought at WordUp Pompey! - 21st December 2011
Ready to Unlock the Power of Blockchain!Toptal Tech
Imagine a world where data flows freely, yet remains secure. A world where trust is built into the fabric of every transaction. This is the promise of blockchain, a revolutionary technology poised to reshape our digital landscape.
Toptal Tech is at the forefront of this innovation, connecting you with the brightest minds in blockchain development. Together, we can unlock the potential of this transformative technology, building a future of transparency, security, and endless possibilities.
HijackLoader Evolution: Interactive Process HollowingDonato Onofri
CrowdStrike researchers have identified a HijackLoader (aka IDAT Loader) sample that employs sophisticated evasion techniques to enhance the complexity of the threat. HijackLoader, an increasingly popular tool among adversaries for deploying additional payloads and tooling, continues to evolve as its developers experiment and enhance its capabilities.
In their analysis of a recent HijackLoader sample, CrowdStrike researchers discovered new techniques designed to increase the defense evasion capabilities of the loader. The malware developer used a standard process hollowing technique coupled with an additional trigger that was activated by the parent process writing to a pipe. This new approach, called "Interactive Process Hollowing", has the potential to make defense evasion stealthier.
Discover the benefits of outsourcing SEO to Indiadavidjhones387
"Discover the benefits of outsourcing SEO to India! From cost-effective services and expert professionals to round-the-clock work advantages, learn how your business can achieve digital success with Indian SEO solutions.
Ever since I started developing plugins for WordPress I’ve wanted to know what’s going on under the covers and how I could improve it.
Here’s a chart that visualizes some results. I’ll try to explain them in later slides. There’s some clues in the questions.
What’s happening, what’s happening? Moley Mole asks Musky Muskrat in Deputy Dawg ( 1962 – 1963 )
To find out what’s going on I wrote a trace routine. It logs output to trace file. It’s not just a var_dump().
There’s an awful lot of contextual information. It’s similar to query-monitor; it traces front-end, admin, scheduled requests, AJAX requests, REST requests and command line stuff.
The main difference is that it produces plain text files you can browse at your leisure. The output is NOT intermingled with the real results. Oik-bwtrace also produces a “Daily Trace Summary” report, showing each request’s relevant(?) statistics at `shutdown`.
To understand any data echoed from a system it’s good to have context. Quite a lot of it. You never know when it’ll come in handy. In a debugger you can get this at run time. But debuggers slow the system down. So does tracing for that matter. Don’t remember to disable tracing when running performance tests.
5 years ago I wrote a post processing routine (Slog for Server Log) to summarise the requests in the Daily Trace Summary files grouping by elapsed time then merged the output from multiple logs and then manually produced a chart to display the results in Excel. It was a convoluted process. Recently I decided to invest some time to develop a Chart block which I could use to display the results immediately.
Using the server side rendering for the Chart block I was then able to start to visualize the WordPress web server’s processing.
The Reports tab is used to analyse a Daily Trace Summary file. Each Report shows the results of a grouping of data by selected values ( eg request type, URI, elapsed time IP address). It displays the results in a chart and table. The chart can show Count, Elapsed, Average, Percent count, Percent average, Cumulative percent count and Cumulative percent average. The table shows all columns. Requests can be automatically filtered by request type.
Again 5 years ago, when running tests to evaluate the effect of activating a plugin or configuration option I used a batch driver to perform a variety of requests closely matching real activity. For the Driver tab I just use one URL. The more requests run the better the results. That’s assuming response times are acceptable.
These are the results of running 100 requests to the home URL having activated each of the top 12 plugins.
See my website for an interactive version of the chart.
For the latest summary of top 12 plugins see https://top-10-wp-plugins.com/.
In this chart we can see that Jetpack, WooCommerce and Elementor are the most resource hungry.
https://cwiccer.com/wp-admin/admin.php?page=slog&tab=compare
You may ask where the migration line is!
Here’s the Blue Peter version of some tests that I ran today on cwiccer.com with Yoast SEO, JetPack, WooCommerce and combinations.
Jetpack in orange was with Jetpack activated but not connected.
Jetpack-site-accel is with the Acceleration toggled on.
I was visiting the home URL of cwiccer.com which displays latest posts.
Vanilla is Twenty Twenty with 3 plugins: oik-bwtrace, sb-chart-block and slog.
You can draw your own conclusions.
For more information about these plugins see my GitHub account: bobbingwide, or visit oik-plugins.com. Oik-bwtrace is on wordpress.org, sb-chart-block was submitted yesterday – as a single block plugin.
For my lightning talk on oik-bwtrace see the slides on WP-Pompey or watch the video on YouTube.
Contact me on Twitter or Slack.