20190730 android taipei
•
0 likes•38 views
This document discusses the onBackPressedDispatcher which provides an alternative way to handle back button presses without strongly coupling fragment instances to activities. It can be implemented by adding dependencies, creating an OnBackPressedCallback class to handle callbacks, and using the OnBackPressedDispatcher in activities. The document provides references and links to a demo for how to use the onBackPressedDispatcher.
Report
Share
Report
Share
Download to read offline
Recommended
ConcourseCi Dockerimage
This document summarizes a presentation about managing Docker images with Concourse. It discusses building Docker images from a Dockerfile, triggering image builds when the Dockerfile or dependencies change. It also covers storing and pushing images, and using a Concourse pipeline to check for new images and code commits, rebuild images, tag images and the code repository with the new version.
Concourse updates
This document contains a summary of updates to the Concourse continuous integration and delivery (CI/CD) platform between versions 1.2.0 through 2.0.0. Key updates include adding the ability to pin builds to specific resource versions in 1.2.0, introducing build and test workflows in a single pipeline in 1.3.0, improving container retention and build log loading in 1.4.0 and 1.5.0, adding official Docker images and AWS ECR support in 1.6.0, and integrating multi-tenant team support with authentication in 2.0.0. The presentation also provides demonstrations of Concourse in action and links to documentation, tutorials, public pipelines, and Slack
Install Concourse CI with BOSH
This document discusses how to install Concourse CI using BOSH on AWS and Azure. It provides steps to set up the necessary infrastructure like VPC, security groups, install BOSH Director. It then covers uploading stemcells and releases, creating the BOSH manifest file, and deploying Concourse. The document emphasizes that BOSH allows provisioning Concourse in a production-ready, scalable way and provides samples for AWS and Azure deployments.
Git and GitFlow branching model
Version control systems like Git allow teams to collaborate on code by automatically backing up work, tracking changes over time, and easily sharing code between collaborators. Git uses repositories to store source code and a branching model like GitFlow to coordinate work between team members on features, releases, and hotfixes in a stable, collaborative way. Key concepts in Git include repositories, working copies, commits, updates, pulls, and pushes used to integrate changes between local and remote repositories.
A Git Workflow Model or Branching Strategy
Vivek Parihar is a serial entrepreneur and polyglot engineer who currently serves as VP of Engineering at XOXODay. He has co-founded two startups and previously served as Head of Engineering for Mobile at Yatra. When not working, he enjoys extreme thrill-seeking adventures like trekking and boxing. The document then outlines Gitflow, a branching model for managing code development, including feature branches for new features, release branches to prepare releases, and hotfix branches for urgent bug fixes in production.
Git branching strategies
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.
ActiveLAMP Process
This document summarizes the processes used by ActiveLAMP for code management, issue tracking, time tracking, deployment, and more. It recommends using Git for version control and GitHub for hosting code. It also recommends using Gitosis for version control, tracking time in Atrium, and deploying using Capistrano which installs as a Ruby gem and handles rollbacks. Drush is recommended for improving Drupal efficiency. Only custom code should be kept in a custom repository with the build process.
Git branching-model
This document outlines a Git branching model for managing code development. It describes using main branches like Master and Develop and support branches like Feature, Release, and Hotfix. The model advocates separating work into feature branches, merging them into develop, and merging develop into master upon release. It also lists tools for implementing git flow and sources for more information.
Recommended
ConcourseCi Dockerimage
This document summarizes a presentation about managing Docker images with Concourse. It discusses building Docker images from a Dockerfile, triggering image builds when the Dockerfile or dependencies change. It also covers storing and pushing images, and using a Concourse pipeline to check for new images and code commits, rebuild images, tag images and the code repository with the new version.
Concourse updates
This document contains a summary of updates to the Concourse continuous integration and delivery (CI/CD) platform between versions 1.2.0 through 2.0.0. Key updates include adding the ability to pin builds to specific resource versions in 1.2.0, introducing build and test workflows in a single pipeline in 1.3.0, improving container retention and build log loading in 1.4.0 and 1.5.0, adding official Docker images and AWS ECR support in 1.6.0, and integrating multi-tenant team support with authentication in 2.0.0. The presentation also provides demonstrations of Concourse in action and links to documentation, tutorials, public pipelines, and Slack
Install Concourse CI with BOSH
This document discusses how to install Concourse CI using BOSH on AWS and Azure. It provides steps to set up the necessary infrastructure like VPC, security groups, install BOSH Director. It then covers uploading stemcells and releases, creating the BOSH manifest file, and deploying Concourse. The document emphasizes that BOSH allows provisioning Concourse in a production-ready, scalable way and provides samples for AWS and Azure deployments.
Git and GitFlow branching model
Version control systems like Git allow teams to collaborate on code by automatically backing up work, tracking changes over time, and easily sharing code between collaborators. Git uses repositories to store source code and a branching model like GitFlow to coordinate work between team members on features, releases, and hotfixes in a stable, collaborative way. Key concepts in Git include repositories, working copies, commits, updates, pulls, and pushes used to integrate changes between local and remote repositories.
A Git Workflow Model or Branching Strategy
Vivek Parihar is a serial entrepreneur and polyglot engineer who currently serves as VP of Engineering at XOXODay. He has co-founded two startups and previously served as Head of Engineering for Mobile at Yatra. When not working, he enjoys extreme thrill-seeking adventures like trekking and boxing. The document then outlines Gitflow, a branching model for managing code development, including feature branches for new features, release branches to prepare releases, and hotfix branches for urgent bug fixes in production.
Git branching strategies
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.
ActiveLAMP Process
This document summarizes the processes used by ActiveLAMP for code management, issue tracking, time tracking, deployment, and more. It recommends using Git for version control and GitHub for hosting code. It also recommends using Gitosis for version control, tracking time in Atrium, and deploying using Capistrano which installs as a Ruby gem and handles rollbacks. Drush is recommended for improving Drupal efficiency. Only custom code should be kept in a custom repository with the build process.
Git branching-model
This document outlines a Git branching model for managing code development. It describes using main branches like Master and Develop and support branches like Feature, Release, and Hotfix. The model advocates separating work into feature branches, merging them into develop, and merging develop into master upon release. It also lists tools for implementing git flow and sources for more information.
Apereo OAE development and release process
The document outlines the development and release process for an open source project called OAE. It describes steps like designing features, developing code, testing performance, and releasing updates. Key aspects include developing features from start to finish, dealing with requirements from multiple stakeholders, and thoroughly testing releases through methods such as Tsung load testing before deploying updates to production environments.
ConcourseCi overview
- Concourse is a CI/CD tool that uses pipelines defined in YAML to automate workflows. It runs builds inside containers for isolation.
- It has three main concepts: resources that define inputs/outputs, tasks that define individual build steps, and jobs that define the actions in the pipeline.
- Concourse uses a pluggable resource model so many types of resources can be used as inputs or outputs like Git, Docker images, S3, etc. It can also integrate custom resource types.
- Tasks always behave the same way if inputs are the same. Jobs determine the order of tasks and resources in the pipeline.
- Concourse is installed either locally with Vagrant or on a cluster with Bosh
Fluo CICD OpenStack Summit
This document describes eBay's use of Fluo for continuous integration and deployment using OpenStack. Fluo provides a single interface for configuring, building, testing, and deploying code changes. It provisions instances on OpenStack to run tasks defined in a configuration file like running tests, building packages, and deploying code. Fluo replicates code, packages, and configuration management code across regions and datacenters. It supports common workflows from code review through integration testing, releases, and periodic jobs. Fluo aims to provide a fully automated and scalable continuous delivery system to deploy code changes to eBay's global infrastructure on OpenStack.
Route service-pcf-techmeetup
This document summarizes a presentation about Pivotal's route service in Cloud Foundry. The route service allows requests to be forwarded to an external endpoint before being routed to applications. This can be used for authentication, rate limiting, inspection, or integrating with other systems. The presentation demonstrates configuring a route service in Cloud Foundry to block a hack attempt and provides examples of rate limiting, logging, and web application firewall route services on GitHub. It also reviews documentation on the Cloud Foundry route service.
Spinnaker Chadev
Spinnaker is an open source continuous delivery platform that allows developers to release software changes quickly and safely across multiple cloud platforms. It was originally developed at Netflix to deploy over 100,000 instances to AWS daily using deployment strategies like blue-green deployments and canary releases. The document discusses Spinnaker's architecture, key concepts like pipelines and server groups, and demos how to deploy an application to Kubernetes using a Spinnaker pipeline.
Spinnaker at DevOpsDays Montreal
At DevOpsDays Montreal, CloudOps' Adrian Todorov discusses Spinnaker, a multi-cloud continuous delivery platform. Spinnaker automates your deployments and makes them reliable. It can be used to complement other CI tools, such as Jenkins.
Automated PHP delivery with Bamboo @Rakuten ICHIBA
This document discusses automating PHP application delivery with Bamboo by:
1. Having code changes trigger a build pipeline in Bamboo that produces a deployment artifact
2. Using scp to upload the artifact to target servers where it is unarchived and unnecessary files are discarded
3. Changing the target of a symbolic link to release the new version and restarting services, with the ability to rollback changes
It provides examples of the build and deployment results and links project automation to related issue tracking tickets.
Introduction to Drupal 7 - Installing and configuring WYSIWYG editors in Drupal
Short and practical tutorial on how to install and configure the popular WYSIWYG editors as: ckeditor, tinymce editor, etc
Dev ops cd tool chains
Overview of a DevOps tool chains, including build servers (Jenkins, GO, etc...), Vagrant, Docker, Configuration Management tools (Chef, Puppet, Ansible, etc..)
Auto-scaled Concourse CI on AWS w/o BOSH
This document discusses auto-scaling Concourse CI on AWS without using BOSH. It introduces concourse-aws, which allows bootstrapping a Concourse cluster on AWS with one command. Concourse-aws supports time-based and utilization-based auto-scaling to optimize costs. It implements auto-scaling using Terraform to provision AWS resources. The author hopes Concourse will support officially pausing pipelines when scaling workers and caching Docker images to improve build times after scaling out.
London devops - orc
Orc provides zero downtime deployments for heterogeneous applications running on multiple servers across environments through a standardized deployment interface. It defines contracts for applications to integrate with its deployment automation, checks conformance, and models desired states to do safe, predictable rolling deployments through state transitions. Participating applications get continuous deployment capabilities. It aims to participate load balancers and do deployment at the instance level through a state machine and prioritized actions.
Monolithic docker pattern
This document outlines a simple Docker development workflow for monolithic applications involving development, staging, and production hosts. It describes operations to update base images, develop changes in containers on the development host, build new images, save/load builds between hosts by copying redundant layers, test on staging, and deploy final builds to production by copying images and launching containers.
Continuous Deployment
This document discusses continuous integration practices including automatically building code, testing it, and creating deployment packages. It describes how continuous integration has evolved to incorporate more automated testing and deployment to test environments. The document advocates treating deployment to test environments as a "known release package" that is logged, versioned, and can be rolled back in a similar way to application releases. This helps ensure production deployments are replicable and auditable.
Drupal Europe 2018: Hackers automate but the drupal community still downloads...
“Automatic Updates for Drupal” was, is and will be a matter of debate. In this open discussion, we want to welcome everyone who wants to learn more about the current state of update processes within the Drupal Community, and especially about possible future scenarios in Drupal.
We welcome everyone who’s interested in joining the discussion about auto update possibilities and bringing in critical reflections.
Introduction to Go
The document discusses continuous integration and continuous delivery workflows. It provides definitions and best practices for continuous integration, continuous delivery, and continuous deployment. It also summarizes the key concepts and components of ThoughtWorks Go including pipelines, stages, jobs, tasks, agents, and the value stream map for visualization. Pros and cons are listed for ThoughtWorks Go compared to Jenkins, noting Go's strengths in end-to-end visualization, fan-in support, and security configuration while Jenkins has more plugins and flexibility.
A successful Git branching model
This document outlines a Git branching model to allow for smooth development with isolated features. The model uses main branches of master and develop, and support branches of feature, release, and hotfix. Feature branches isolate new work and merge back to develop. Release branches prepare releases and merge to both develop and master. Hotfix branches address urgent bugs in master and also merge to both develop and master. This model aims to allow multiple developers to work independently while reducing conflicts and enabling flexible releases and rollbacks.
AppStream repositories with CLM filters
Modularity allows users to choose a specific version of an application and receive updates for it. Modules act like views of a repository, hiding certain parts from the package manager. A typical workflow involves adding a modular channel, creating filters for needed modules, and building the project, with dependency resolution handled by a Python module that automatically adds dependencies to the repository.
Using JHipster for generating Angular/Spring Boot apps
The document discusses using JHipster 4 for generating Angular and Spring Boot applications. It begins with an overview of Spring Boot and Angular and demonstrates generating a basic monolithic application with them. It then introduces JHipster as a tool for generating Angular/Spring Boot projects along with best practices. The rest of the document demonstrates features of JHipster like generating entities, internationalization, and microservices architecture.
Branching Over The Top!
The document discusses branching and merging in revision control systems. It defines branching as duplicating an object under revision control to allow parallel modifications, and merging as reconciling changes made to different copies of the same file. Branching increases agility and maintainability. Reasons for branching include release isolation, feature isolation, and team isolation. The document outlines different branching plans and provides examples of branching structures for single and multi-team development as well as features, hotfixes and service packs.
All about Context API
The document discusses the Context API in React, including what it is, how to use it, when not to use it, nesting multiple providers, and how it relates to other state management tools like Redux.
The Context API allows components to subscribe to changes in context without having to pass props down manually at every level. It helps solve the problem of prop drilling. It can be used to pass common data like theme, authentication info, or locale throughout the component tree without passing props down manually at every level. When there are multiple providers, components can be wrapped with multiple contexts using tools like react-compose. While Context API is useful for smaller state management, Redux is still useful for centralized application logic and development
Getting started with Octopus Deploy
How do you automate the non-existing deployment routines of an organization with over 100 different customers, each having their own environments? How do you convince the leaders, developers and customers to give you the resources needed in order to automate everything? Is it really possible to introduce a deployment routine that works for everyone?
In less than six months, Karoline transformed the deployment routines at Epinova by introducing Octopus Deploy to the organization. She will take you through the steps needed to get started, the pitfalls along the way, and success that Octopus Deploy has become.
In this workshop we will start out by installing an Octopus Deploy server and tentacle on your laptop, before looking at the basic concepts of Environments, Machines, Roles and Projects. You will create a project of your own and deploy this using Octopus Deploy before we round off by looking at the advanced topics of Script modules, Step templates, Variable sets and Retention Policies.
At the end of this workshop, you'll have all the knowledge you need in order to create a more efficient and failproof deployment process for your project. Keep calm and deploy to production!
Cypress report
It is a presentation to help software developers get started with a testing platform Cypress. I have created it personally and given the most basics of explanation regarding the new concepts.
More Related Content
What's hot
Apereo OAE development and release process
The document outlines the development and release process for an open source project called OAE. It describes steps like designing features, developing code, testing performance, and releasing updates. Key aspects include developing features from start to finish, dealing with requirements from multiple stakeholders, and thoroughly testing releases through methods such as Tsung load testing before deploying updates to production environments.
ConcourseCi overview
- Concourse is a CI/CD tool that uses pipelines defined in YAML to automate workflows. It runs builds inside containers for isolation.
- It has three main concepts: resources that define inputs/outputs, tasks that define individual build steps, and jobs that define the actions in the pipeline.
- Concourse uses a pluggable resource model so many types of resources can be used as inputs or outputs like Git, Docker images, S3, etc. It can also integrate custom resource types.
- Tasks always behave the same way if inputs are the same. Jobs determine the order of tasks and resources in the pipeline.
- Concourse is installed either locally with Vagrant or on a cluster with Bosh
Fluo CICD OpenStack Summit
This document describes eBay's use of Fluo for continuous integration and deployment using OpenStack. Fluo provides a single interface for configuring, building, testing, and deploying code changes. It provisions instances on OpenStack to run tasks defined in a configuration file like running tests, building packages, and deploying code. Fluo replicates code, packages, and configuration management code across regions and datacenters. It supports common workflows from code review through integration testing, releases, and periodic jobs. Fluo aims to provide a fully automated and scalable continuous delivery system to deploy code changes to eBay's global infrastructure on OpenStack.
Route service-pcf-techmeetup
This document summarizes a presentation about Pivotal's route service in Cloud Foundry. The route service allows requests to be forwarded to an external endpoint before being routed to applications. This can be used for authentication, rate limiting, inspection, or integrating with other systems. The presentation demonstrates configuring a route service in Cloud Foundry to block a hack attempt and provides examples of rate limiting, logging, and web application firewall route services on GitHub. It also reviews documentation on the Cloud Foundry route service.
Spinnaker Chadev
Spinnaker is an open source continuous delivery platform that allows developers to release software changes quickly and safely across multiple cloud platforms. It was originally developed at Netflix to deploy over 100,000 instances to AWS daily using deployment strategies like blue-green deployments and canary releases. The document discusses Spinnaker's architecture, key concepts like pipelines and server groups, and demos how to deploy an application to Kubernetes using a Spinnaker pipeline.
Spinnaker at DevOpsDays Montreal
At DevOpsDays Montreal, CloudOps' Adrian Todorov discusses Spinnaker, a multi-cloud continuous delivery platform. Spinnaker automates your deployments and makes them reliable. It can be used to complement other CI tools, such as Jenkins.
Automated PHP delivery with Bamboo @Rakuten ICHIBA
This document discusses automating PHP application delivery with Bamboo by:
1. Having code changes trigger a build pipeline in Bamboo that produces a deployment artifact
2. Using scp to upload the artifact to target servers where it is unarchived and unnecessary files are discarded
3. Changing the target of a symbolic link to release the new version and restarting services, with the ability to rollback changes
It provides examples of the build and deployment results and links project automation to related issue tracking tickets.
Introduction to Drupal 7 - Installing and configuring WYSIWYG editors in Drupal
Short and practical tutorial on how to install and configure the popular WYSIWYG editors as: ckeditor, tinymce editor, etc
Dev ops cd tool chains
Overview of a DevOps tool chains, including build servers (Jenkins, GO, etc...), Vagrant, Docker, Configuration Management tools (Chef, Puppet, Ansible, etc..)
Auto-scaled Concourse CI on AWS w/o BOSH
This document discusses auto-scaling Concourse CI on AWS without using BOSH. It introduces concourse-aws, which allows bootstrapping a Concourse cluster on AWS with one command. Concourse-aws supports time-based and utilization-based auto-scaling to optimize costs. It implements auto-scaling using Terraform to provision AWS resources. The author hopes Concourse will support officially pausing pipelines when scaling workers and caching Docker images to improve build times after scaling out.
London devops - orc
Orc provides zero downtime deployments for heterogeneous applications running on multiple servers across environments through a standardized deployment interface. It defines contracts for applications to integrate with its deployment automation, checks conformance, and models desired states to do safe, predictable rolling deployments through state transitions. Participating applications get continuous deployment capabilities. It aims to participate load balancers and do deployment at the instance level through a state machine and prioritized actions.
Monolithic docker pattern
This document outlines a simple Docker development workflow for monolithic applications involving development, staging, and production hosts. It describes operations to update base images, develop changes in containers on the development host, build new images, save/load builds between hosts by copying redundant layers, test on staging, and deploy final builds to production by copying images and launching containers.
Continuous Deployment
This document discusses continuous integration practices including automatically building code, testing it, and creating deployment packages. It describes how continuous integration has evolved to incorporate more automated testing and deployment to test environments. The document advocates treating deployment to test environments as a "known release package" that is logged, versioned, and can be rolled back in a similar way to application releases. This helps ensure production deployments are replicable and auditable.
Drupal Europe 2018: Hackers automate but the drupal community still downloads...
“Automatic Updates for Drupal” was, is and will be a matter of debate. In this open discussion, we want to welcome everyone who wants to learn more about the current state of update processes within the Drupal Community, and especially about possible future scenarios in Drupal.
We welcome everyone who’s interested in joining the discussion about auto update possibilities and bringing in critical reflections.
Introduction to Go
The document discusses continuous integration and continuous delivery workflows. It provides definitions and best practices for continuous integration, continuous delivery, and continuous deployment. It also summarizes the key concepts and components of ThoughtWorks Go including pipelines, stages, jobs, tasks, agents, and the value stream map for visualization. Pros and cons are listed for ThoughtWorks Go compared to Jenkins, noting Go's strengths in end-to-end visualization, fan-in support, and security configuration while Jenkins has more plugins and flexibility.
A successful Git branching model
This document outlines a Git branching model to allow for smooth development with isolated features. The model uses main branches of master and develop, and support branches of feature, release, and hotfix. Feature branches isolate new work and merge back to develop. Release branches prepare releases and merge to both develop and master. Hotfix branches address urgent bugs in master and also merge to both develop and master. This model aims to allow multiple developers to work independently while reducing conflicts and enabling flexible releases and rollbacks.
AppStream repositories with CLM filters
Modularity allows users to choose a specific version of an application and receive updates for it. Modules act like views of a repository, hiding certain parts from the package manager. A typical workflow involves adding a modular channel, creating filters for needed modules, and building the project, with dependency resolution handled by a Python module that automatically adds dependencies to the repository.
Using JHipster for generating Angular/Spring Boot apps
The document discusses using JHipster 4 for generating Angular and Spring Boot applications. It begins with an overview of Spring Boot and Angular and demonstrates generating a basic monolithic application with them. It then introduces JHipster as a tool for generating Angular/Spring Boot projects along with best practices. The rest of the document demonstrates features of JHipster like generating entities, internationalization, and microservices architecture.
Branching Over The Top!
The document discusses branching and merging in revision control systems. It defines branching as duplicating an object under revision control to allow parallel modifications, and merging as reconciling changes made to different copies of the same file. Branching increases agility and maintainability. Reasons for branching include release isolation, feature isolation, and team isolation. The document outlines different branching plans and provides examples of branching structures for single and multi-team development as well as features, hotfixes and service packs.
All about Context API
The document discusses the Context API in React, including what it is, how to use it, when not to use it, nesting multiple providers, and how it relates to other state management tools like Redux.
The Context API allows components to subscribe to changes in context without having to pass props down manually at every level. It helps solve the problem of prop drilling. It can be used to pass common data like theme, authentication info, or locale throughout the component tree without passing props down manually at every level. When there are multiple providers, components can be wrapped with multiple contexts using tools like react-compose. While Context API is useful for smaller state management, Redux is still useful for centralized application logic and development
What's hot (20)
Automated PHP delivery with Bamboo @Rakuten ICHIBA
Automated PHP delivery with Bamboo @Rakuten ICHIBA
Introduction to Drupal 7 - Installing and configuring WYSIWYG editors in Drupal
Introduction to Drupal 7 - Installing and configuring WYSIWYG editors in Drupal
Drupal Europe 2018: Hackers automate but the drupal community still downloads...
Drupal Europe 2018: Hackers automate but the drupal community still downloads...
Using JHipster for generating Angular/Spring Boot apps
Using JHipster for generating Angular/Spring Boot apps
Similar to 20190730 android taipei
Getting started with Octopus Deploy
How do you automate the non-existing deployment routines of an organization with over 100 different customers, each having their own environments? How do you convince the leaders, developers and customers to give you the resources needed in order to automate everything? Is it really possible to introduce a deployment routine that works for everyone?
In less than six months, Karoline transformed the deployment routines at Epinova by introducing Octopus Deploy to the organization. She will take you through the steps needed to get started, the pitfalls along the way, and success that Octopus Deploy has become.
In this workshop we will start out by installing an Octopus Deploy server and tentacle on your laptop, before looking at the basic concepts of Environments, Machines, Roles and Projects. You will create a project of your own and deploy this using Octopus Deploy before we round off by looking at the advanced topics of Script modules, Step templates, Variable sets and Retention Policies.
At the end of this workshop, you'll have all the knowledge you need in order to create a more efficient and failproof deployment process for your project. Keep calm and deploy to production!
Cypress report
It is a presentation to help software developers get started with a testing platform Cypress. I have created it personally and given the most basics of explanation regarding the new concepts.
The Future of Adhearson
The document discusses plans for the next major version (2.0) of the Adhearsion telephony framework. It describes extracting Asterisk-specific code into a new library called Punchblock that will provide a common call control API across platforms. This will allow Adhearsion applications to run on Asterisk, FreeSWITCH or other backends. It also outlines changes to the API and goals for AdhearsionConf 2012, including porting apps to 3 platforms and gaining new contributors. Questions are posed about scaling, multi-platform use cases, needed features, and desired new capabilities.
[React-Native Tutorial 10] Camera Roll / Gallery / Camera / Native Modules by...
[React-Native Tutorial 10] Camera Roll / Gallery / Camera / Native Modules by...Kobkrit Viriyayudhakorn
This document discusses linking native libraries in React Native applications. It provides instructions for both automatic and manual linking. Automatic linking uses the react-native link command to link libraries added via npm. Manual linking requires opening the Xcode or Android Studio project and adding the native library files manually. The document then demonstrates manual linking of the RCTCameraRoll native library, which is needed to access the camera roll on iOS. It also discusses building a sample app with React Native and RCTCameraRoll to pick images from the camera roll or take new photos with the camera.Introduce Flux & react in practices (KKBOX)
Flux is an application architecture pattern for building user interfaces that uses unidirectional data flow. React is a view library that handles the visual DOM and component lifecycle. Flux uses a dispatcher to facilitate one-way data flow from the actions to stores to views. Stores hold the application state and trigger changes that cause React components to re-render. Together, Flux architecture and React components allow building large web applications in a predictable and performant way.
Eclipse IDE, 2019.09, Java Development
The document provides instructions for using decorations with controls in SWT/JFace applications. It discusses how the ControlDecoration class allows placing image decorations on controls to provide additional information. Creating a decoration involves adding a ControlDecoration to a Text field in the design view and then adding code in the source view to initialize the decoration. The decoration can display an image and tooltip text when the user hovers over it. Developers must leave space in the UI layout for decorations to be visible.
Introduce flux & react in practice
This document discusses introducing Flux and React in practice. It provides an overview of Flux as an architecture with one directional data flow. React is described as a library for creating views with components. The document then discusses how Flux and React work together, with data flowing from the store to components through a dispatcher. It provides examples of using Flux and React to build a music player app and mobile store app.
Oscon London 2016 - Docker from Development to Production
Docker revolutionized how developers and operations teams build, ship, and run applications, enabling them to leverage the latest advancements in software development: the microservice architecture style, the immutable infrastructure deployment style, and the DevOps cultural model.
Existing software layers are not a great fit to leverage these trends. Infrastructure as a service is too low level; platform as a service is too high level; but containers as a service (CaaS) is just right. Container images are just the right level of abstraction for DevOps, allowing developers to specify all their dependencies at build time, building and testing an artifact that, when ready to ship, is the exact thing that will run in production. CaaS gives ops teams the tools to control how to run these workloads securely and efficiently, providing portability between different cloud providers and on-premises deployments.
Patrick Chanezon offers a detailed overview of the latest evolutions to the Docker ecosystem enabling CaaS: standards (OCI, CNCF), infrastructure (runC, containerd, Notary), platform (Docker, Swarm), and services (Docker Cloud, Docker Datacenter). Patrick ends with a demo showing how to do in-container development of a Spring Boot application on a Mac running a preconfigured IDE in a container, provision a highly available Swarm cluster using Docker Datacenter on a cloud provider, and leverage the latest Docker tools to build, ship, and run a polyglot application architected as a set of microservices—including how to set up load balancing.
Build your next app with MvvmCross 6
MvvmCross is a cross-platform application framework for Xamarin and .NET that implements the MVVM pattern. MvvmCross 6 is the latest version which features polished Xamarin.Forms support, a redesigned framework initialization, new plugins architecture, improved view presenters, initial Tizen support, and many bug fixes. The presentation demonstrated building an app with MvvmCross 6 and discussed plans for ongoing improvements and community involvement.
AppCatalyst and Photon OS
VMware AppCatalyst is a lightweight desktop hypervisor for Mac that provides a drop-in replacement for VirtualBox in Docker Machine and Vagrant. It comes with Photon OS, a container-optimized Linux distribution built by VMware for cloud-native applications. AppCatalyst exposes a REST API and CLI for seamless integration with container workflows. It also includes Vagrant integration out of the box to support using Vagrant and Photon OS VMs. Photon OS is optimized for running containers and provides a secure container runtime with updates from VMware.
Octopus Deploy @Erie Day of Code
Octopus Deploy is a tool for .NET deployment automation. You can use it to deploy IIS websites, Windows services, and even certificates and scripts that you need to run on remote machines.
Octopus Deploy has the potential to make deploying from the build server to remote machines painless and repeatable- but there are some things you may want to know up front to make that happen. This session will explore why you might want to try Octopus Deploy, what sort of issues you may run into, and how Ocuvera uses Octopus to manage our on-premise product installations & updates.
4 maven junit
The document provides an overview of Maven and JUnit topics including how to set up a Maven project, the core concepts of Maven such as dependencies and repositories, how to write JUnit tests for a calculator example including annotations like @Before and @After, how to measure test coverage using tools like Cobertura, and guidelines for best practices in unit testing. It also assigns homework to convert an AddressBook project to Maven, add unit tests, and configure Cobertura to measure 85% line coverage as well as generate a Maven site.
Containers and Microservices for Realists
Talk for Oracle Code Conference- New York 2017. Container, Microservices, Serverless by Karthik Gaekwad
Containers and microservices for realists
Karthik Gaekwad presented on containers and microservices. He discussed the evolution of DevOps and how containers and microservices fit within the DevOps paradigm by allowing for collaboration between development and operations teams. He defined containers, microservices, and common containerization concepts. Gaekwad also provided examples of how organizations are using containers for standardization, continuous integration and delivery pipelines, and hosting legacy applications.
Productivity 101: Making a Easily Re-deployable Dev Environment with Subversion
This document discusses using Subversion to easily redeploy WordPress development environments. It recommends setting up a Subversion server and repository to store WordPress core files and common plugins/themes. The "svn:externals" property allows linking local folders to external Subversion paths, so updating checks out new files. This allows consistently deploying WordPress versions, plugins and themes across projects with minimal effort.
The Need For Speed - NxtGen Cambridge
This document provides an overview and introduction to Microsoft's AppFabric distributed caching platform. It discusses what AppFabric is, why a distributed cache is useful, how to configure an AppFabric client and server, how to manage a cache cluster, and considerations around concurrency and high availability. The document also outlines some common caching patterns like cache-aside and discusses how AppFabric compares to other caching solutions.
Infinum Android Talks #17 - Testing your Android applications by Ivan Kust
van will show you how to setup unit tests using Robolectric, how to test user interactions using Espresso and provide some tips and tricks for stress-free testing.
Play Framework + Docker + CircleCI + AWS + EC2 Container Service
The document discusses using Play Framework, Docker, CircleCI, and AWS together to create an automated microservices build pipeline. Key aspects include using GitHub for source control, CircleCI for continuous integration to build Docker images, pushing images to Docker Hub, and deploying to AWS using ECS for container orchestration. The author demonstrates setting up each part of the pipeline live.
React Native Firebase
- The document discusses React Native component lifecycles, including mounting and updating lifecycles.
- The mounting lifecycle includes constructor, componentWillMount, render, and componentDidMount. This lifecycle happens when a component is initialized and inserted into the DOM.
- The updating lifecycle includes componentWillReceiveProps, shouldComponentUpdate, componentWillUpdate, render, and componentDidUpdate. This lifecycle happens when a component re-renders as a result of changes to either props or state.
Drupal8 for Symfony Developers (PHP Day Verona 2017)
Drupal8 modernization (new object-oriented base) and adoption of many Symfony components is a huge step in connecting these two amazing communities and amazing projects. Drupal8 is not powered by full-stack Symfony and there is still many differences between these two relatives, but still, Symfony developers should master it easily.
This talk is for Symfony developers who don't have experience with Drupal8. It will guide you through routing, controllers, hooks, events, Drupal Console, DI and many other interesting elements that power Drupal8 under the hood. It will also show how to build custom modules Symfony way.
Similar to 20190730 android taipei (20)
[React-Native Tutorial 10] Camera Roll / Gallery / Camera / Native Modules by...
[React-Native Tutorial 10] Camera Roll / Gallery / Camera / Native Modules by...
Oscon London 2016 - Docker from Development to Production
Oscon London 2016 - Docker from Development to Production
Productivity 101: Making a Easily Re-deployable Dev Environment with Subversion
Productivity 101: Making a Easily Re-deployable Dev Environment with Subversion
Infinum Android Talks #17 - Testing your Android applications by Ivan Kust
Infinum Android Talks #17 - Testing your Android applications by Ivan Kust
Play Framework + Docker + CircleCI + AWS + EC2 Container Service
Play Framework + Docker + CircleCI + AWS + EC2 Container Service
Drupal8 for Symfony Developers (PHP Day Verona 2017)
Drupal8 for Symfony Developers (PHP Day Verona 2017)
Recently uploaded
Open Channel Flow: fluid flow with a free surface
Open Channel Flow: This topic focuses on fluid flow with a free surface, such as in rivers, canals, and drainage ditches. Key concepts include the classification of flow types (steady vs. unsteady, uniform vs. non-uniform), hydraulic radius, flow resistance, Manning's equation, critical flow conditions, and energy and momentum principles. It also covers flow measurement techniques, gradually varied flow analysis, and the design of open channels. Understanding these principles is vital for effective water resource management and engineering applications.
Blood finder application project report (1).pdf
Blood Finder is an emergency time app where a user can search for the blood banks as
well as the registered blood donors around Mumbai. This application also provide an
opportunity for the user of this application to become a registered donor for this user have
to enroll for the donor request from the application itself. If the admin wish to make user
a registered donor, with some of the formalities with the organization it can be done.
Specialization of this application is that the user will not have to register on sign-in for
searching the blood banks and blood donors it can be just done by installing the
application to the mobile.
The purpose of making this application is to save the user’s time for searching blood of
needed blood group during the time of the emergency.
This is an android application developed in Java and XML with the connectivity of
SQLite database. This application will provide most of basic functionality required for an
emergency time application. All the details of Blood banks and Blood donors are stored
in the database i.e. SQLite.
This application allowed the user to get all the information regarding blood banks and
blood donors such as Name, Number, Address, Blood Group, rather than searching it on
the different websites and wasting the precious time. This application is effective and
user friendly.
SCALING OF MOS CIRCUITS m .pptx
this ppt explains about scaling parameters of the mosfet it is basically vlsi subject
LLM Fine Tuning with QLoRA Cassandra Lunch 4, presented by Anant
Slides for the 4th Presentation on LLM Fine-Tuning with QLoRA Presented by Anant, featuring DataStax Astra
Mechanical Engineering on AAI Summer Training Report-003.pdf
Mechanical Engineering PROJECT REPORT ON SUMMER VOCATIONAL TRAINING
AT MBB AIRPORT
Null Bangalore | Pentesters Approach to AWS IAM
#Abstract:
- Learn more about the real-world methods for auditing AWS IAM (Identity and Access Management) as a pentester. So let us proceed with a brief discussion of IAM as well as some typical misconfigurations and their potential exploits in order to reinforce the understanding of IAM security best practices.
- Gain actionable insights into AWS IAM policies and roles, using hands on approach.
#Prerequisites:
- Basic understanding of AWS services and architecture
- Familiarity with cloud security concepts
- Experience using the AWS Management Console or AWS CLI.
- For hands on lab create account on [killercoda.com](https://killercoda.com/cloudsecurity-scenario/)
# Scenario Covered:
- Basics of IAM in AWS
- Implementing IAM Policies with Least Privilege to Manage S3 Bucket
- Objective: Create an S3 bucket with least privilege IAM policy and validate access.
- Steps:
- Create S3 bucket.
- Attach least privilege policy to IAM user.
- Validate access.
- Exploiting IAM PassRole Misconfiguration
-Allows a user to pass a specific IAM role to an AWS service (ec2), typically used for service access delegation. Then exploit PassRole Misconfiguration granting unauthorized access to sensitive resources.
- Objective: Demonstrate how a PassRole misconfiguration can grant unauthorized access.
- Steps:
- Allow user to pass IAM role to EC2.
- Exploit misconfiguration for unauthorized access.
- Access sensitive resources.
- Exploiting IAM AssumeRole Misconfiguration with Overly Permissive Role
- An overly permissive IAM role configuration can lead to privilege escalation by creating a role with administrative privileges and allow a user to assume this role.
- Objective: Show how overly permissive IAM roles can lead to privilege escalation.
- Steps:
- Create role with administrative privileges.
- Allow user to assume the role.
- Perform administrative actions.
- Differentiation between PassRole vs AssumeRole
Try at [killercoda.com](https://killercoda.com/cloudsecurity-scenario/)
Software Engineering and Project Management - Software Testing + Agile Method...
Software Testing: A Strategic Approach to Software Testing, Strategic Issues, Test Strategies for Conventional Software, Test Strategies for Object -Oriented Software, Validation Testing, System Testing, The Art of Debugging.
Agile Methodology: Before Agile – Waterfall, Agile Development.
一比一原版(爱大毕业证书)爱荷华大学毕业证如何办理
原版一模一样【微信：741003700 】【(爱大毕业证书)爱荷华大学毕业证成绩单】【微信：741003700 】学位证，留信认证（真实可查，永久存档）原件一模一样纸张工艺/offer、雅思、外壳等材料/诚信可靠,可直接看成品样本，帮您解决无法毕业带来的各种难题！外壳，原版制作，诚信可靠，可直接看成品样本。行业标杆！精益求精，诚心合作，真诚制作！多年品质 ,按需精细制作，24小时接单,全套进口原装设备。十五年致力于帮助留学生解决难题，包您满意。
本公司拥有海外各大学样板无数，能完美还原。
1:1完美还原海外各大学毕业材料上的工艺：水印，阴影底纹，钢印LOGO烫金烫银，LOGO烫金烫银复合重叠。文字图案浮雕、激光镭射、紫外荧光、温感、复印防伪等防伪工艺。材料咨询办理、认证咨询办理请加学历顾问Q/微741003700
【主营项目】
一.毕业证【q微741003700】成绩单、使馆认证、教育部认证、雅思托福成绩单、学生卡等！
二.真实使馆公证(即留学回国人员证明,不成功不收费)
三.真实教育部学历学位认证（教育部存档！教育部留服网站永久可查）
四.办理各国各大学文凭(一对一专业服务,可全程监控跟踪进度)
如果您处于以下几种情况：
◇在校期间，因各种原因未能顺利毕业……拿不到官方毕业证【q/微741003700】
◇面对父母的压力，希望尽快拿到；
◇不清楚认证流程以及材料该如何准备；
◇回国时间很长，忘记办理；
◇回国马上就要找工作，办给用人单位看；
◇企事业单位必须要求办理的
◇需要报考公务员、购买免税车、落转户口
◇申请留学生创业基金
留信网认证的作用:
1:该专业认证可证明留学生真实身份
2:同时对留学生所学专业登记给予评定
3:国家专业人才认证中心颁发入库证书
4:这个认证书并且可以归档倒地方
5:凡事获得留信网入网的信息将会逐步更新到个人身份内，将在公安局网内查询个人身份证信息后，同步读取人才网入库信息
6:个人职称评审加20分
7:个人信誉贷款加10分
8:在国家人才网主办的国家网络招聘大会中纳入资料，供国家高端企业选择人才
办理(爱大毕业证书)爱荷华大学毕业证【微信：741003700 】外观非常简单，由纸质材料制成，上面印有校徽、校名、毕业生姓名、专业等信息。
办理(爱大毕业证书)爱荷华大学毕业证【微信：741003700 】格式相对统一，各专业都有相应的模板。通常包括以下部分：
校徽：象征着学校的荣誉和传承。
校名:学校英文全称
授予学位：本部分将注明获得的具体学位名称。
毕业生姓名：这是最重要的信息之一，标志着该证书是由特定人员获得的。
颁发日期：这是毕业正式生效的时间，也代表着毕业生学业的结束。
其他信息：根据不同的专业和学位，可能会有一些特定的信息或章节。
办理(爱大毕业证书)爱荷华大学毕业证【微信：741003700 】价值很高，需要妥善保管。一般来说，应放置在安全、干燥、防潮的地方，避免长时间暴露在阳光下。如需使用，最好使用复印件而不是原件，以免丢失。
综上所述，办理(爱大毕业证书)爱荷华大学毕业证【微信：741003700 】是证明身份和学历的高价值文件。外观简单庄重，格式统一，包括重要的个人信息和发布日期。对持有人来说，妥善保管是非常重要的。
Height and depth gauge linear metrology.pdf
Height gauges may also be used to measure the height of an object by using the underside of the scriber as the datum. The datum may be permanently fixed or the height gauge may have provision to adjust the scale, this is done by sliding the scale vertically along the body of the height gauge by turning a fine feed screw at the top of the gauge; then with the scriber set to the same level as the base, the scale can be matched to it. This adjustment allows different scribers or probes to be used, as well as adjusting for any errors in a damaged or resharpened probe.
Accident detection system project report.pdf
The Rapid growth of technology and infrastructure has made our lives easier. The
advent of technology has also increased the traffic hazards and the road accidents take place
frequently which causes huge loss of life and property because of the poor emergency facilities.
Many lives could have been saved if emergency service could get accident information and
reach in time. Our project will provide an optimum solution to this draw back. A piezo electric
sensor can be used as a crash or rollover detector of the vehicle during and after a crash. With
signals from a piezo electric sensor, a severe accident can be recognized. According to this
project when a vehicle meets with an accident immediately piezo electric sensor will detect the
signal or if a car rolls over. Then with the help of GSM module and GPS module, the location
will be sent to the emergency contact. Then after conforming the location necessary action will
be taken. If the person meets with a small accident or if there is no serious threat to anyone’s
life, then the alert message can be terminated by the driver by a switch provided in order to
avoid wasting the valuable time of the medical rescue team.
DEEP LEARNING FOR SMART GRID INTRUSION DETECTION: A HYBRID CNN-LSTM-BASED MODEL
As digital technology becomes more deeply embedded in power systems, protecting the communication
networks of Smart Grids (SG) has emerged as a critical concern. Distributed Network Protocol 3 (DNP3)
represents a multi-tiered application layer protocol extensively utilized in Supervisory Control and Data
Acquisition (SCADA)-based smart grids to facilitate real-time data gathering and control functionalities.
Robust Intrusion Detection Systems (IDS) are necessary for early threat detection and mitigation because
of the interconnection of these networks, which makes them vulnerable to a variety of cyberattacks. To
solve this issue, this paper develops a hybrid Deep Learning (DL) model specifically designed for intrusion
detection in smart grids. The proposed approach is a combination of the Convolutional Neural Network
(CNN) and the Long-Short-Term Memory algorithms (LSTM). We employed a recent intrusion detection
dataset (DNP3), which focuses on unauthorized commands and Denial of Service (DoS) cyberattacks, to
train and test our model. The results of our experiments show that our CNN-LSTM method is much better
at finding smart grid intrusions than other deep learning algorithms used for classification. In addition,
our proposed approach improves accuracy, precision, recall, and F1 score, achieving a high detection
accuracy rate of 99.50%.
Digital Twins Computer Networking Paper Presentation.pptx
A Digital Twin in computer networking is a virtual representation of a physical network, used to simulate, analyze, and optimize network performance and reliability. It leverages real-time data to enhance network management, predict issues, and improve decision-making processes.
Pressure Relief valve used in flow line to release the over pressure at our d...
Pressure Relief valve used in flow line to release the over pressure at our desired pressure
AI-Based Home Security System : Home security
Home security is of paramount importance in today's world, where we rely more on technology, home
security is crucial. Using technology to make homes safer and easier to control from anywhere is
important. Home security is important for the occupant’s safety. In this paper, we came up with a low cost,
AI based model home security system. The system has a user-friendly interface, allowing users to start
model training and face detection with simple keyboard commands. Our goal is to introduce an innovative
home security system using facial recognition technology. Unlike traditional systems, this system trains
and saves images of friends and family members. The system scans this folder to recognize familiar faces
and provides real-time monitoring. If an unfamiliar face is detected, it promptly sends an email alert,
ensuring a proactive response to potential security threats.
Use PyCharm for remote debugging of WSL on a Windo cf5c162d672e4e58b4dde5d797...
This document serves as a comprehensive step-by-step guide on how to effectively use PyCharm for remote debugging of the Windows Subsystem for Linux (WSL) on a local Windows machine. It meticulously outlines several critical steps in the process, starting with the crucial task of enabling permissions, followed by the installation and configuration of WSL.
The guide then proceeds to explain how to set up the SSH service within the WSL environment, an integral part of the process. Alongside this, it also provides detailed instructions on how to modify the inbound rules of the Windows firewall to facilitate the process, ensuring that there are no connectivity issues that could potentially hinder the debugging process.
The document further emphasizes on the importance of checking the connection between the Windows and WSL environments, providing instructions on how to ensure that the connection is optimal and ready for remote debugging.
It also offers an in-depth guide on how to configure the WSL interpreter and files within the PyCharm environment. This is essential for ensuring that the debugging process is set up correctly and that the program can be run effectively within the WSL terminal.
Additionally, the document provides guidance on how to set up breakpoints for debugging, a fundamental aspect of the debugging process which allows the developer to stop the execution of their code at certain points and inspect their program at those stages.
Finally, the document concludes by providing a link to a reference blog. This blog offers additional information and guidance on configuring the remote Python interpreter in PyCharm, providing the reader with a well-rounded understanding of the process.
Recently uploaded (20)
LLM Fine Tuning with QLoRA Cassandra Lunch 4, presented by Anant
LLM Fine Tuning with QLoRA Cassandra Lunch 4, presented by Anant
Mechanical Engineering on AAI Summer Training Report-003.pdf
Mechanical Engineering on AAI Summer Training Report-003.pdf
2. protection of river banks and bed erosion protection works.ppt
2. protection of river banks and bed erosion protection works.ppt
Software Engineering and Project Management - Software Testing + Agile Method...
Software Engineering and Project Management - Software Testing + Agile Method...
DEEP LEARNING FOR SMART GRID INTRUSION DETECTION: A HYBRID CNN-LSTM-BASED MODEL
DEEP LEARNING FOR SMART GRID INTRUSION DETECTION: A HYBRID CNN-LSTM-BASED MODEL
Digital Twins Computer Networking Paper Presentation.pptx
Digital Twins Computer Networking Paper Presentation.pptx
4. Mosca vol I -Fisica-Tipler-5ta-Edicion-Vol-1.pdf
4. Mosca vol I -Fisica-Tipler-5ta-Edicion-Vol-1.pdf
Pressure Relief valve used in flow line to release the over pressure at our d...
Pressure Relief valve used in flow line to release the over pressure at our d...
Use PyCharm for remote debugging of WSL on a Windo cf5c162d672e4e58b4dde5d797...
Use PyCharm for remote debugging of WSL on a Windo cf5c162d672e4e58b4dde5d797...
20190730 android taipei
- 2. Agenda • Introduction • Implementation • Reference • Demo
- 3. Introduction • Traditional way • onBackPressedListener for fragments • Access fragment instance directly
- 5. Introduction cont. • strongly coupling!
- 6. So? Try another way! Here comes onBackpressedDispatcher
- 8. Add Dependency • Required: • Androidx 的 appcompat 1.1.0-alpha04 以上 • Androidx 的 activity 1.0.0-alpha06 以上
- 9. Implementation- onBackPressCallback • Class for handling OnBackPressedDispatcher#onBackPressed() callbacks without strongly coupling that implementation to a subclass of ComponentActivity. • This class(OnBackPressedCallback) maintains its own enabled state. • Only when this callback is enabled will it receive callbacks to handleOnBackPressed().
- 11. Reference • ComponentActivity: • https://developer.android.google.cn/reference/kotlin/androidx/activity/ ComponentActivity • Provide custom back navigation: • https://developer.android.com/guide/navigation/navigation-custom- back#activity_onbackpressed • 「AndroidXでのバックキー制御」について、 onBackPressedDispatcherの使い⽅方や注意点補⾜足: • https://qiita.com/tarumzu/items/d6b18447ad24b5b5bfa2