Gradle is a build system for Android that is based on Groovy. It allows for build variants through product flavors and build types. Project structure in Gradle uses a settings.gradle file to define modules and a gradle.properties file for configuration. Build files define dependencies and configuration. Gradle allows signing, building for different platforms, and managing library and app modules.
WP-CLI and aliases allow developers to automate tasks and deploy changes across WordPress environments. Aliases define shortcuts for remote WordPress sites accessed via SSH, letting developers run commands without changing directories. A script exports a database from production, imports it to development and replaces URLs, automating deployment. WP-CLI, aliases, variables and conditionals enable scripting multiple commands for remote WordPress site management and deployment.
Optimising Your Front End Workflow With Symfony, Twig, Bower and GulpMatthew Davis
We take great care in our back end coding workflow, optimising, automating and abstracting as much as is possible. So why don't we do that with our front end code?
We'll take a look at some tools to help us take our front end workflow to the next level, and hopefully optimise our load times in the process!
We'll be looking at using Twig templates and optimising them for the different areas of your application, integrating Bower and Gulp for managing assets and processing our front-end code to avoid repetitive tasks - looking at how that impacts the typical Symfony workflow.
This document contains configuration settings for a CMake build in the directory /home/lauro/Documents. It lists compiler flags, linker flags, and other configuration options for CMake, CUDA, and OpenCV. Key values include compiler and linker paths, build type, and CUDA and OpenCV library locations.
The document discusses using Composer and modules to better organize Magento projects. It recommends:
- Using Composer to install Magento core and modules separately from the project codebase.
- Treating modules as independent, reusable components with their own versioning and maintenance.
- Allowing multiple teams to collaborate on developing the same module for different projects.
- Managing module versions and dependencies flexibly between projects through Composer.
Video at http://www.youtube.com/watch?v=HaJnhYPLvx0
Large Drupal projects will generally have a themer or five working alongside the developers, site builders and designers. Themers are the magicians who transform what Drupal wants to do into what the designer wants it to do.
Smaller projects also usually need someone on the team who can make sense of Drupal's output, knows more CSS and JS than anyone else and can configure Views with their eyes closed.
The thing is — and whisper this, if possible redundancy concerns you — we can bypass the themer entirely.
With some simple configuration, a site builder can get Drupal to output exactly the semantic, lightweight markup that any modern front-end designer would be proud of. The designer can be left alone to write the most appropriate HTML, CSS and JS, while the site builder need only choose a couple of options when putting together content types, views and panels to make Drupal behave.
A friendly developer may have to lend a hand every now and then, but that’s it. You can get rid of the themer altogether.
http://2013.drupalcamplondon.co.uk/session/death-themer
Composer is a dependency manager and package manager for PHP that allows projects to declare their dependencies in a composer.json file. It installs dependencies and manages autoloading so that dependencies are available to a project. The presentation discusses why Composer is useful for avoiding dependency issues, how to initialize a project with Composer, add and update dependencies, and how Composer can be used to manage modules and themes in Drupal projects. It also covers using Composer scripts and plugins as well as integrating Composer and Drush.
Headless Drupal involves decoupling the Drupal backend from the frontend presentation layer. This allows for flexible frontend development while retaining Drupal's content management capabilities through a REST API. Key benefits include separation of concerns between content and presentation, using the best technologies for each, and improved performance through caching and scalability. Some topics to consider include available Drupal services, security, accessibility and SEO when implementing a headless architecture.
symfony: An Open-Source Framework for Professionals (Dutch Php Conference 2008)Fabien Potencier
This document provides an overview of the symfony framework presented by Fabien Potencier and Stefan Koopmanschap. It introduces symfony as an open-source PHP web framework built for professional websites and complex needs. It then demonstrates how to initialize a new symfony project, create modules and actions, implement templates and layouts, and integrate a database using Propel as the ORM.
WP-CLI and aliases allow developers to automate tasks and deploy changes across WordPress environments. Aliases define shortcuts for remote WordPress sites accessed via SSH, letting developers run commands without changing directories. A script exports a database from production, imports it to development and replaces URLs, automating deployment. WP-CLI, aliases, variables and conditionals enable scripting multiple commands for remote WordPress site management and deployment.
Optimising Your Front End Workflow With Symfony, Twig, Bower and GulpMatthew Davis
We take great care in our back end coding workflow, optimising, automating and abstracting as much as is possible. So why don't we do that with our front end code?
We'll take a look at some tools to help us take our front end workflow to the next level, and hopefully optimise our load times in the process!
We'll be looking at using Twig templates and optimising them for the different areas of your application, integrating Bower and Gulp for managing assets and processing our front-end code to avoid repetitive tasks - looking at how that impacts the typical Symfony workflow.
This document contains configuration settings for a CMake build in the directory /home/lauro/Documents. It lists compiler flags, linker flags, and other configuration options for CMake, CUDA, and OpenCV. Key values include compiler and linker paths, build type, and CUDA and OpenCV library locations.
The document discusses using Composer and modules to better organize Magento projects. It recommends:
- Using Composer to install Magento core and modules separately from the project codebase.
- Treating modules as independent, reusable components with their own versioning and maintenance.
- Allowing multiple teams to collaborate on developing the same module for different projects.
- Managing module versions and dependencies flexibly between projects through Composer.
Video at http://www.youtube.com/watch?v=HaJnhYPLvx0
Large Drupal projects will generally have a themer or five working alongside the developers, site builders and designers. Themers are the magicians who transform what Drupal wants to do into what the designer wants it to do.
Smaller projects also usually need someone on the team who can make sense of Drupal's output, knows more CSS and JS than anyone else and can configure Views with their eyes closed.
The thing is — and whisper this, if possible redundancy concerns you — we can bypass the themer entirely.
With some simple configuration, a site builder can get Drupal to output exactly the semantic, lightweight markup that any modern front-end designer would be proud of. The designer can be left alone to write the most appropriate HTML, CSS and JS, while the site builder need only choose a couple of options when putting together content types, views and panels to make Drupal behave.
A friendly developer may have to lend a hand every now and then, but that’s it. You can get rid of the themer altogether.
http://2013.drupalcamplondon.co.uk/session/death-themer
Composer is a dependency manager and package manager for PHP that allows projects to declare their dependencies in a composer.json file. It installs dependencies and manages autoloading so that dependencies are available to a project. The presentation discusses why Composer is useful for avoiding dependency issues, how to initialize a project with Composer, add and update dependencies, and how Composer can be used to manage modules and themes in Drupal projects. It also covers using Composer scripts and plugins as well as integrating Composer and Drush.
Headless Drupal involves decoupling the Drupal backend from the frontend presentation layer. This allows for flexible frontend development while retaining Drupal's content management capabilities through a REST API. Key benefits include separation of concerns between content and presentation, using the best technologies for each, and improved performance through caching and scalability. Some topics to consider include available Drupal services, security, accessibility and SEO when implementing a headless architecture.
symfony: An Open-Source Framework for Professionals (Dutch Php Conference 2008)Fabien Potencier
This document provides an overview of the symfony framework presented by Fabien Potencier and Stefan Koopmanschap. It introduces symfony as an open-source PHP web framework built for professional websites and complex needs. It then demonstrates how to initialize a new symfony project, create modules and actions, implement templates and layouts, and integrate a database using Propel as the ORM.
Dependency management in Magento with ComposerManuele Menozzi
This document discusses using Composer for dependency management in Magento projects. It explains what Composer is and how it works, including declaring dependencies in composer.json, installing packages, and generating autoloads. It also covers how to use the Magento Composer Installer plugin to install Magento modules and core via Composer. The benefits of managing Magento dependencies with Composer include time savings, code reuse, easy upgrades, and consistent code usage.
Best Practice Site Architecture in Drupal 8Pantheon
Drupal 8 offers developers many exciting new features to use in building websites. Have you tried configuration management? How about the new Symfony based routing system? Twig? Cache tags? Each of these systems is extremely powerful and will let you build websites like never before.
This document discusses the CSS preprocessor LESS and its features. LESS allows for nested rules, mixins, variables, imports and operators to make CSS more maintainable. It can be run from Node.js or a browser and compiles LESS files into normal CSS. Key features include mixins for common CSS patterns, variables for consistency, nesting for organization and imports to modularize code. LESS aims to make CSS leaner, meaner and more dynamic through its preprocessing abilities.
This document discusses how to set up a Vagrant development system. Vagrant allows you to run development environments in isolated virtual machines on your local machine. It ensures that your development environment matches production. The document explains how to install Vagrant and VirtualBox. It provides an overview of common Vagrant commands and configurations. It also demonstrates how to use Vagrant for WordPress development, including running unit tests and the makepot tool.
The document provides guidance on how to write a first WordPress plugin, including an overview of plugins and their capabilities, how to structure a plugin with PHP code and files, how to use hooks and filters to extend WordPress functionality, how to add administrative features like settings pages and widgets, and tips for best practices when developing WordPress plugins.
Development Workflow Tools for Open-Source PHP LibrariesPantheon
Having a fine-tuned continuous integration environment is extremely valuable, even for small projects. Today, there is a wide variety of standalone projects and online Software-As-A-Service offerings that can super-streamline your everyday development tasks that can help you get your projects up and running like a pro. In this session, we'll look at how you can get the most out of:
* GitHub source code repository
* Packagist package manager for Composer
* Travis CI continuous integration service
* Coveralls code coverage service
* Scrutinizer static analysis service
* Box2 phar builder
* Sami api documentation generator
* ReadTheDocs online documentation reader service
* Composer scripts and projects for running local tests and builds After mastering these tools, you will be able to quickly set up a new php library project and use it in your Drupal modules.
Session presented at Stanford Drupal Camp: https://drupalcamp.stanford.edu/development-workflow-tools-open-source-php-libraries
Modern Perl web development has evolved over the past 20 years. While Perl was once widely used for web development via CGI scripts, newer technologies emerged that were easier to maintain. The document discusses how Perl is still suitable for web development using modern tools like PSGI, Plack, Dancer2, and others. It demonstrates building a basic TODO application in Perl using these tools, including generating database classes from an existing database, retrieving and displaying data, and adding features with JavaScript and jQuery.
WordPress mit Composer und Git verwaltenWalter Ebert
This document provides instructions and examples for installing, configuring, and using Composer to manage WordPress and other PHP projects. It covers downloading and installing Composer, installing packages and dependencies, updating packages, using Composer scripts, setting up a WordPress project structure with Composer, and additional tips and strategies for version control and deployment.
How to create a joomla component from scratchTim Plummer
- The document discusses how to create a basic Joomla component from scratch in about an hour by forking and modifying the existing com_helloworld component.
- It describes the necessary files and code changes needed to modify the component name, add additional fields to the component form, and include features like publishing status filtering.
- The presentation provides step-by-step instructions for tasks like renaming files and text strings, adding columns to views, and including standard Joomla features like toolbar buttons and menu icons to create a functional component.
This document discusses several new features introduced in PHP 7 including:
1. Exception handling was improved with a new exception hierarchy and errors are now catchable.
2. Scalar type declarations were added allowing functions to declare and enforce parameter and return value types like int, float, bool, etc.
3. The null coalescing operator ?? was added to simplify checking for null values and providing defaults.
4. The spaceship operator <=> was added for combined comparison of values returning -1, 0, or 1.
Overall PHP 7 focused on major internal improvements and optimizations while maintaining backwards compatibility and adding several new features to further strengthen type safety.
Extending eZ Platform v2 with Symfony and ReacteZ Systems
This document discusses extending eZ Platform 2.x with Symfony and React. It provides background on the technology stack changes from 1.x to 2.x, including moving from YUI3 to Symfony and React to improve performance and extensibility. It describes various extension points for both frontend and backend developers, such as React modules, field types, and application menus. It demonstrates performance improvements of 2.x over 1.x through examples of login and location pages loading over 10x faster.
Versão com GIFs:
https://docs.google.com/presentation/d/17M-jHlkAP5KPfQ4_Alck_wIsN2gK3dZNGfJR9Bi1L50/present
Códigos para instalação das dependências:
https://github.com/fdaciuk/talks/tree/master/2015/wordcamp-sao-paulo
How to Issue and Activate Free SSL using Let's EncryptMayeenul Islam
How to issue and activate Free SSL Certificate on a shared hosting from cPanel using SSH access, PHP ACME client, and cPanel SSL/TLS widget.
Get the Video here:
https://www.youtube.com/watch?v=bk868eeiN8w
This document discusses caching in a multi-language Rails environment. It describes how Rails does not natively support caching across different languages or expiring caches for all languages at once. It then outlines extensions needed to Rails to add language routes, handle format and language negotiation through HTTP headers, set the request language, and support language-based page caching.
WordPress Structure and Best Practicesmarkparolisi
The document discusses the directory structure, core files, database structure, plugins, themes, and templates in WordPress. It provides information on actions, filters, widgets, modifying plugins, and best practices for developing WordPress sites and plugins. Key points include the directory locations for core files, plugins, themes, and uploads, as well as the main database tables like wp_posts and wp_options.
This document summarizes three new add-ons from the European Environment Agency (EEA): EEA Annotator for inline comments, EEA Progressbar for tracking editing progress, and EEA PDF for customizable PDF export. It provides information on the features and setup of each add-on, and includes links to demo videos. The presentation was given at the Plone Conference in Bristol, 2014 by Alin Voinea from Eau de Web in Romania.
VersionPress is an open-source version control plugin for WordPress that allows tracking of all changes made to a website. It assigns unique IDs to database entities to avoid conflicts when merging data between environments. It also handles foreign keys by defining relationships between database tables and values. The document discusses challenges with WordPress database design and how VersionPress addresses these through its own format for storing database data as files that can be version controlled.
This document outlines how to create a composer package for managing PHP dependencies. It discusses adding dependencies using composer, creating the package directory structure with src and tests folders, defining a Hello class in the src folder, writing tests for the Hello class in the tests folder, adding autoloading to the composer.json file, pushing the package to Git and releasing it on Packagist, and using the package by requiring it in another project's composer.json file. It also mentions setting up continuous integration for the package.
Gentle introduction to Pyramid. Where it comes from, how simple it, how fast, how flexible and why the future will be pyramid shaped.
Made for pyconau 2011
This document introduces Gradle basics for Android development. It covers setting up the Gradle environment, project structure, build configurations like flavors and build types. It also explains key Gradle concepts and tasks like settings.gradle, build.gradle, dependencies, variants. Basic Groovy syntax and how to customize tasks are also demonstrated.
OSGi Feature Model - Where Art Thou - David Bosschaert (Adobe)mfrancis
OSGi Community Event 2018 Presentation by David Bosschaert (Adobe)
Abstract: OSGi lends itself well to develop extensible applications assembled from reusable modules, where a set of bundles together with a set of configurations deployed to a provisioned OSGi framework is the application.
While this works very well for the originally intended use-cases, maintaining and building large applications developed by multiple teams often requires to assemble multiple larger components for which there is limited support in OSGi as of today. This is especially true in cases where multiple groups of bundles, configuration, metadata, and other artifacts need to be combined.
In this talk we will introduce you to OSGi RFP-188, named OSGi Features, which defines the requirements on providing a solution. We'll establish a shared understanding of the problem space and how it relates to already available mechanisms in OSGi (like e.g. subsystems, deploymentadmin, startlevels, etc.) and will subsequently, review it in the context of some of the current (open source) solutions like Apache Karaf Features and Apache Sling Features and Bnd.
Dependency management in Magento with ComposerManuele Menozzi
This document discusses using Composer for dependency management in Magento projects. It explains what Composer is and how it works, including declaring dependencies in composer.json, installing packages, and generating autoloads. It also covers how to use the Magento Composer Installer plugin to install Magento modules and core via Composer. The benefits of managing Magento dependencies with Composer include time savings, code reuse, easy upgrades, and consistent code usage.
Best Practice Site Architecture in Drupal 8Pantheon
Drupal 8 offers developers many exciting new features to use in building websites. Have you tried configuration management? How about the new Symfony based routing system? Twig? Cache tags? Each of these systems is extremely powerful and will let you build websites like never before.
This document discusses the CSS preprocessor LESS and its features. LESS allows for nested rules, mixins, variables, imports and operators to make CSS more maintainable. It can be run from Node.js or a browser and compiles LESS files into normal CSS. Key features include mixins for common CSS patterns, variables for consistency, nesting for organization and imports to modularize code. LESS aims to make CSS leaner, meaner and more dynamic through its preprocessing abilities.
This document discusses how to set up a Vagrant development system. Vagrant allows you to run development environments in isolated virtual machines on your local machine. It ensures that your development environment matches production. The document explains how to install Vagrant and VirtualBox. It provides an overview of common Vagrant commands and configurations. It also demonstrates how to use Vagrant for WordPress development, including running unit tests and the makepot tool.
The document provides guidance on how to write a first WordPress plugin, including an overview of plugins and their capabilities, how to structure a plugin with PHP code and files, how to use hooks and filters to extend WordPress functionality, how to add administrative features like settings pages and widgets, and tips for best practices when developing WordPress plugins.
Development Workflow Tools for Open-Source PHP LibrariesPantheon
Having a fine-tuned continuous integration environment is extremely valuable, even for small projects. Today, there is a wide variety of standalone projects and online Software-As-A-Service offerings that can super-streamline your everyday development tasks that can help you get your projects up and running like a pro. In this session, we'll look at how you can get the most out of:
* GitHub source code repository
* Packagist package manager for Composer
* Travis CI continuous integration service
* Coveralls code coverage service
* Scrutinizer static analysis service
* Box2 phar builder
* Sami api documentation generator
* ReadTheDocs online documentation reader service
* Composer scripts and projects for running local tests and builds After mastering these tools, you will be able to quickly set up a new php library project and use it in your Drupal modules.
Session presented at Stanford Drupal Camp: https://drupalcamp.stanford.edu/development-workflow-tools-open-source-php-libraries
Modern Perl web development has evolved over the past 20 years. While Perl was once widely used for web development via CGI scripts, newer technologies emerged that were easier to maintain. The document discusses how Perl is still suitable for web development using modern tools like PSGI, Plack, Dancer2, and others. It demonstrates building a basic TODO application in Perl using these tools, including generating database classes from an existing database, retrieving and displaying data, and adding features with JavaScript and jQuery.
WordPress mit Composer und Git verwaltenWalter Ebert
This document provides instructions and examples for installing, configuring, and using Composer to manage WordPress and other PHP projects. It covers downloading and installing Composer, installing packages and dependencies, updating packages, using Composer scripts, setting up a WordPress project structure with Composer, and additional tips and strategies for version control and deployment.
How to create a joomla component from scratchTim Plummer
- The document discusses how to create a basic Joomla component from scratch in about an hour by forking and modifying the existing com_helloworld component.
- It describes the necessary files and code changes needed to modify the component name, add additional fields to the component form, and include features like publishing status filtering.
- The presentation provides step-by-step instructions for tasks like renaming files and text strings, adding columns to views, and including standard Joomla features like toolbar buttons and menu icons to create a functional component.
This document discusses several new features introduced in PHP 7 including:
1. Exception handling was improved with a new exception hierarchy and errors are now catchable.
2. Scalar type declarations were added allowing functions to declare and enforce parameter and return value types like int, float, bool, etc.
3. The null coalescing operator ?? was added to simplify checking for null values and providing defaults.
4. The spaceship operator <=> was added for combined comparison of values returning -1, 0, or 1.
Overall PHP 7 focused on major internal improvements and optimizations while maintaining backwards compatibility and adding several new features to further strengthen type safety.
Extending eZ Platform v2 with Symfony and ReacteZ Systems
This document discusses extending eZ Platform 2.x with Symfony and React. It provides background on the technology stack changes from 1.x to 2.x, including moving from YUI3 to Symfony and React to improve performance and extensibility. It describes various extension points for both frontend and backend developers, such as React modules, field types, and application menus. It demonstrates performance improvements of 2.x over 1.x through examples of login and location pages loading over 10x faster.
Versão com GIFs:
https://docs.google.com/presentation/d/17M-jHlkAP5KPfQ4_Alck_wIsN2gK3dZNGfJR9Bi1L50/present
Códigos para instalação das dependências:
https://github.com/fdaciuk/talks/tree/master/2015/wordcamp-sao-paulo
How to Issue and Activate Free SSL using Let's EncryptMayeenul Islam
How to issue and activate Free SSL Certificate on a shared hosting from cPanel using SSH access, PHP ACME client, and cPanel SSL/TLS widget.
Get the Video here:
https://www.youtube.com/watch?v=bk868eeiN8w
This document discusses caching in a multi-language Rails environment. It describes how Rails does not natively support caching across different languages or expiring caches for all languages at once. It then outlines extensions needed to Rails to add language routes, handle format and language negotiation through HTTP headers, set the request language, and support language-based page caching.
WordPress Structure and Best Practicesmarkparolisi
The document discusses the directory structure, core files, database structure, plugins, themes, and templates in WordPress. It provides information on actions, filters, widgets, modifying plugins, and best practices for developing WordPress sites and plugins. Key points include the directory locations for core files, plugins, themes, and uploads, as well as the main database tables like wp_posts and wp_options.
This document summarizes three new add-ons from the European Environment Agency (EEA): EEA Annotator for inline comments, EEA Progressbar for tracking editing progress, and EEA PDF for customizable PDF export. It provides information on the features and setup of each add-on, and includes links to demo videos. The presentation was given at the Plone Conference in Bristol, 2014 by Alin Voinea from Eau de Web in Romania.
VersionPress is an open-source version control plugin for WordPress that allows tracking of all changes made to a website. It assigns unique IDs to database entities to avoid conflicts when merging data between environments. It also handles foreign keys by defining relationships between database tables and values. The document discusses challenges with WordPress database design and how VersionPress addresses these through its own format for storing database data as files that can be version controlled.
This document outlines how to create a composer package for managing PHP dependencies. It discusses adding dependencies using composer, creating the package directory structure with src and tests folders, defining a Hello class in the src folder, writing tests for the Hello class in the tests folder, adding autoloading to the composer.json file, pushing the package to Git and releasing it on Packagist, and using the package by requiring it in another project's composer.json file. It also mentions setting up continuous integration for the package.
Gentle introduction to Pyramid. Where it comes from, how simple it, how fast, how flexible and why the future will be pyramid shaped.
Made for pyconau 2011
This document introduces Gradle basics for Android development. It covers setting up the Gradle environment, project structure, build configurations like flavors and build types. It also explains key Gradle concepts and tasks like settings.gradle, build.gradle, dependencies, variants. Basic Groovy syntax and how to customize tasks are also demonstrated.
OSGi Feature Model - Where Art Thou - David Bosschaert (Adobe)mfrancis
OSGi Community Event 2018 Presentation by David Bosschaert (Adobe)
Abstract: OSGi lends itself well to develop extensible applications assembled from reusable modules, where a set of bundles together with a set of configurations deployed to a provisioned OSGi framework is the application.
While this works very well for the originally intended use-cases, maintaining and building large applications developed by multiple teams often requires to assemble multiple larger components for which there is limited support in OSGi as of today. This is especially true in cases where multiple groups of bundles, configuration, metadata, and other artifacts need to be combined.
In this talk we will introduce you to OSGi RFP-188, named OSGi Features, which defines the requirements on providing a solution. We'll establish a shared understanding of the problem space and how it relates to already available mechanisms in OSGi (like e.g. subsystems, deploymentadmin, startlevels, etc.) and will subsequently, review it in the context of some of the current (open source) solutions like Apache Karaf Features and Apache Sling Features and Bnd.
This document discusses different approaches to creating Gradle plugins, including build script plugins, buildSrc projects, and standalone plugins. It explains that build script plugins are only visible within the build script they are defined in, while buildSrc projects and standalone plugins can be shared and reused across multiple builds. Standalone plugins require publishing a JAR file and can include multiple plugins. The document also covers implementing plugins in different languages and creating tasks, extensions, and domain-specific languages within plugins.
This document discusses how automation tools like Grunt, Gulp, Phing and Make can help software developers by automating repetitive tasks. It outlines four key reasons for using build tools: 1) They allow for quick project setup by automatically configuring environments. 2) They ensure reproducible project output regardless of developer setup. 3) They enable easy work in development and production replicas. 4) They facilitate debugging by allowing work in source files through source maps. Build tools automate tasks like linting, preprocessing, concatenation, minification, testing and more so developers can focus on coding.
This document summarizes Go project layout and practices for a Go web application project. It discusses folder structure, configuration management using environment variables and files, embedding assets, command line interfaces, testing practices including fixtures, and packages for common functions like errors, middleware, models and more.
Gradle is the build system you have been waiting for or maybe the build system that has been waiting for you. The adoption rate is incredible from being the new Google Android development tools build system to most new Java opensource projects to JavaScript based front-end and back-end projects.
Lightweight Developer Provisioning with GradleQAware GmbH
This document discusses lightweight developer provisioning using Gradle. It describes how Gradle tasks and Groovy can be used to automate the creation and updating of a software development environment (SEU). Dependencies are expressed as Gradle configurations and stored in an artifact repository. The document provides examples of customizing an SEU by mounting network drives, initializing databases, and restoring Solr indexes using Gradle tasks. It also outlines how to easily build software packages and publish them to a repository.
Lightweight Developer Provisioning with Gradle and SEU-as-codeMario-Leander Reimer
This document discusses lightweight developer provisioning using Gradle. It describes how Gradle tasks and Groovy can be used to automate the creation and updating of a software development environment (SEU). Dependencies are expressed as Gradle configurations and stored in an artifact repository. The document provides examples of customizing an SEU by mounting network drives, initializing databases, and restoring Solr indexes using Gradle tasks. It also outlines how to easily build software package files and publish them to a repository.
Custom deployments with sbt-native-packagerGaryCoady
sbt-native-packager offers a comprehensive approach to packaging artifacts with SBT. The user describes a generic layout, which can then be extended for different types of software and deployments. For example, it is flexible enough to describe both a Zip-based archive format, and an RPM package with appropriate Systemd configuration for a service.
This talk will cover the essentials needed to understand the design of sbt-native-packager, and how to extend its structure to create custom layouts and deployments.
Single Page JavaScript WebApps... A Gradle StoryKon Soulianidis
From MelbJVM July 2014
This presentation covers building single page web applications with Gradle, including why we chose to use Gradle instead of a more commonly used JS based build tool, and the benefits by integrating a JS webapp into the JVM environment.
Getting started with building your own standalone Gradle plugintobiaspreuss
This document discusses building a standalone Gradle plugin and provides examples of plugin and Android build configuration files. It begins with an agenda that covers framing the problem, starting from a template, customization, local deployment, and further reading. Examples then show typical Android configuration elements as well as sample build files from existing open source projects that demonstrate different approaches to configuration. The status quo of duplicating configuration across projects is contrasted with the aim of encapsulating shared configuration in a plugin to avoid repetition and simplify maintenance. Finally, it notes that Gradle's init task can now generate a starting project template for a Gradle plugin written in Java, Groovy, or Kotlin.
Introducing RaveJS: Spring Boot concepts for JavaScript applicationsJohn Hann
Modern JavaScript frameworks have become quite sophisticated. Unfortunately, they have also become quite complicated. The demos and sample projects for these frameworks look deceptively simple. However, to build and deploy real applications, developers must scaffold, configure, and maintain a tremendous amount of intricate machinery. Until recently, the Java world wasn't very different. Spring Boot finally made it easy to create stand-alone, production-grade Spring Applications that can you can "just run". Can we do the same for JavaScript? Yes, we can! Introducing RaveJS. Rave eliminates configuration, machinery, and complexity. Stop configuring and tweaking machinery such as file watchers, minifiers, and transpilers just to get to a runnable app. Instead, go from zero to "hello world" in 30 seconds. In the next 30 seconds, easily add capabilities and frameworks to your application simply by installing *Rave Extensions* and *Rave Starter* packages from npm and Bower, the leading JavaScript package managers. Finally, install additional *Rave Extension* packages to apply your favorite build, deploy, and testing patterns.
DevFest 2022 - GitHub Actions를 활용한 Flutter 배포 자동화하기SuJang Yang
The document discusses automating builds and deployments of Flutter apps using GitHub Actions and Fastlane. It begins by explaining how to set up build variants in Flutter to target different environments. It then covers configuring Fastlane lanes to increment version numbers, build apps, and manage signing. Finally, it describes how the build and deploy flow can be automated with GitHub Actions by triggering Fastlane lanes on push events.
The document discusses developing plugins for Redmine. It outlines a three step process to create a plugin: 1) Generate the plugin files and structure, 2) Create any models, and 3) Create controllers. It also notes there were significant changes between the 1.x and 2.x branches of Redmine and provides resources for plugin development tutorials.
Pantheon's Greg Anderson presents on the topic of using Composer with Drupal and Drush. Composer is a dependency manager that has become the de-facto standard for managing the components used in any sort of PHP library or application. Drupal is no exception to this, and in this presentation, Greg showed that the future is already here: it is completely possible to use native Composer functions to manage the modules and themes used in a Drupal site. In this capacity, Composer can take over the functions usually performed with drush make, drush pm-download, and drush pm-update.
This document provides information about configuring Grails applications. It discusses the basic configuration files BuildConfig.groovy and Config.groovy, which contain settings for building and running the application respectively. It describes implicit variables available in both files like userHome and appName. Runtime settings in Config.groovy include the logging configuration, environments, data source configuration using DataSource.groovy, and advanced data source properties. The document also covers dependency resolution, and different dependency scopes for build, runtime, compile and test.
Το CMake είναι το πιο διαδεδομένο εργαλείο για να "χτίσεις" projects γραμμένα σε C++ για το 2021.
Το CMake δε μεταγλωτίζει το ίδιο τον κώδικα αλλά παράγει τις κατάλληλες παραμέτρους για άλλα εργαλεία (π.χ. make) τα οποία αναλαμβάνουν τη μεταγλώτισση.
Η χρήση εργαλείων όπως το CMake είναι μονόδρομος όταν ένα έργο σε C++ περιλαμβάνει πολλά αρχεία, διάφορες παραμέτρους, εξωτερικά dependencies κλπ. Σε αυτή την περίπτωση η ανάπτυξή του γίνεται εκθετικά δυσκολότερη όσο το μέγεθός του αυξάνεται, εάν δεν υιοθετηθεί χρήση εργαλείων όπως το CMake.
邏 Στο εργαστήριο θα δείξουμε πως μπορούμε να στήσουμε ένα τυπικό project γραμμένο σε C++ και θα καλύψουμε τα πιο βασικά σενάρια που χρειάζεται να γνωρίζει κάποιος όπως:
✅ Παραγωγή εκτελέσιμου αρχείου
✅ Καθορισμός του include path
✅ Δημιουργία βιβλιοθήκης για static ή dynamic linking
✅ Ελεγχος των διάφορων compilation flags
✅ Δημιουργία functions εντός του CMake
✅ Παραμετροποίηση μέσω options
This document provides an overview of configuration in Grails, including basic configuration, environments, data sources, dependency resolution, and more.
The basic configuration files are BuildConfig.groovy and Config.groovy. BuildConfig.groovy contains settings for Grails commands while Config.groovy contains runtime settings. Both files can access implicit configuration variables.
Environments like development, test, and production can be configured separately. Data sources are configured in DataSource.groovy and drivers are typically resolved using Ivy or Maven. Dependency resolution in Grails uses a DSL to control how plugins and JARs are resolved.
2. So, what’s gradle?
● It’s a build system
● Based on Groovy
● Extensible (plugins!)
● Introduced to Android with Android Studio
● No support for NDK (yet)
35. Material Design
● “paper” and “ink” based design language
● introduced with Android L-something
● cross-everything (mobile, desktop, wear, etc)
● adds depth through shadows
● beautifully crafted (unlike this ugly presentation)
Can run on IDE, as well as on Build Server;
New version of Android Studio (Beta, 0.8.1);
Groovy is like Java;
We can plug-in(to) any stage of a build process through tooling APIs
different sign
Move stuff Manifest -> gradle
Move stuff Manifest ->
consists of properties that are automatically parsed and provided in our build.gradle files
Move stuff Manifest ->
topmost build.gradle file;
it’s boring, provided by IDE/AS;
A lot of things happen in this file
since 0.8.0 there’s new plugin’s naming nomenclature
no need to repeat the same stuff across different manifests
where you’d put your signing
optional (even when we’re using flavors)
BuildConfig available as static variables in BuildConfig object
split it into multiple slides with animated examples:
Buttons,
progress bars,
paper layouts,
8dp grid,
improved animation curves,
webM -> gif: https://cloudconvert.org/webm-to-gif
google.com/design/spec
developer’s approch: https://www.youtube.com/watch?v=x5-ntYM_2UY
http://developer.android.com/preview/material/get-started.html
It takes time for users to find around in a new view
Let’s just ignore support library altogether for now
colorPrimary, colorAccent, tintMode (generic icons transformed to requested color)