Continuous Delivery/Deployment w/ Gitflow, Docker, Jenkins and Rancher

Nov 7, 20181 like1,054 views

The document discusses continuous delivery and deployment using tools like Docker, Gitflow, and Jenkins. Continuous delivery provides benefits like getting features and bug fixes to production quickly, improving quality, and lowering costs. It presents how to use Gitflow for version control, Docker for containerization, and Jenkins for continuous integration and deployment through pipelines. The talk concludes that continuous delivery using these tools can result in better products, lower costs, and happier teams.

Alin Voinea
Eau de Web, Romania
Continuous
Delivery / Deployment
Gitflow, Docker & Jenkins

● Docker
● Gitflow
● Jenkins
2
Continuous delivery / deployment

Continuous delivery / deployment - Why?
● Features / Bug fixes in production ASAP
● Higher quality
● Better products
● Lower costs
● Happier teams
4

Continuous delivery / deployment - Tools
5

Continuous delivery / deployment - Tools
6

Jenkinsfile
10
pipeline {
stages {
stage('Build') {
...
}
stage('Test') {
...
}
stage('Release') {
...
}
}
}

Jenkins release pipelines - Plone Add-on
11

Demo
https://youtu.be/TtpJ_bfAkiY 14

Conclusions
● Continuous delivery / deployment
○ Docker
○ Gitflow
○ Jenkins
~
Lower costs, Better products, Happier teams!
15

ありがとうございました - Thank you!
● References
○ github.com
■ avoinea
● demo.docker.ploneconf
● avoinea.rancher.catalog
■ eea
● eea.rancher.catalog
● eea.docker.gitflow
● eea.docker.jenkins.master
● eea.docker.jenkins.slave-dind
16

The document describes the journey of an insurance comparison website moving from a yearly release cycle with 12 releases in 2012 to a continuous delivery model with daily releases by 2014. It discusses how the company transitioned to using Kanban and feature teams to allow independent delivery of features as soon as they are ready for production. This enables production deployments every day with a focus on fast, reliable builds; automated testing and deployment; and production monitoring.

vodQA Pune (2019) - Jenkins pipeline As codevodQA

This document discusses Jenkins pipeline as code. It provides an overview of continuous integration and continuous delivery practices. It introduces Jenkins and describes its project types including freestyle and pipeline. Key benefits of using Jenkins pipeline are that the pipeline is implemented as code in source control, is durable across Jenkins restarts, and is extensible. The document contrasts scripted and declarative pipeline syntax. It also discusses using Jenkins Job Builder to configure Jenkins jobs from YAML/JSON templates. The presenters provide their contact information for any questions.

Magento 2 Deploy StrategiesRafael Corrêa Gomes

- Magento 2 deploy strategies aim to deploy more frequently with less downtime and reduced costs through consistent, developer-friendly processes. - Challenges include continuous improvement, resilience, ease of use, training, and integration with tools like Slack and Magemojo. - Example code provided automates the deployment process through commands like composer install and cache flushing. - Tools like Deployer and Magedeploy.sh help standardize local development and deployment through recipes that support features like zero downtime deployment and rollback. - Continuous delivery tools like GitHub Actions integrate deployment into existing workflows while deployment tools separate these concerns for more flexibility.

Continuous integration with git labMahyuddin Mahyuddin

This document discusses continuous integration using Gitlab-CI. It defines continuous integration as integrating work frequently, usually daily, by members of a software development team. It introduces Gitlab-CI as the continuous integration and continuous delivery tool integrated within Gitlab for testing, building, and deploying source code. Key features of Gitlab-CI highlighted include being multi-platform, multi-language, stable, supporting parallel builds, real-time logging, versioned tests, pipelines, autoscaling, and build artifacts. Best practices for configuration via .gitlab-ci.yml files are also outlined.

WebVR is now accessibleKevin Simper

PUG ROMAGNA - Alternative a Magento2Giuseppe Morelli

Continuous Delivery in Practice (extended)Tzach Zohar

Extended version of a previously uploaded presentation: 10 practical field-proven tips for building a continuously delivered service, based on Kenshoo's experience with its RTB service - a critical, high throughput, highly available component, serving millions of requests per minute in under 50 milliseconds. From coding practices to test automation, from monitoring tools to feature A/B testing - the entire development chain should be focused around removing blockers and manual steps between your code and your clients, without ever settling for quality. Join to see what makes our clients and developers happy and effective.

Foundations for the perfect technology streamBernd Alter

OpenText MBPM Q&A Webinarconvedo Group

This webinar discusses migrating processes from Metastorm BPM 7.x to Opentext MBPM v9. It outlines the key steps to migrate including using the file migrator to convert 7.x processes to v9 format and the repository migrator to move data. The webinar demonstrates these tools migrating a sample flight booking process and provides tips for the migration such as converting libraries first and handling changes in terminology between the versions. Resources for planning and executing a full migration project are also provided.

Continuous Delivery com Docker, OpenShift e JenkinsBruno Padilha

The document discusses continuous delivery using Docker, OpenShift and Jenkins. It provides an overview of Leroy Merlin, a French home improvement retailer operating in Brazil. It describes the architecture of a microservices-based mobile project at Leroy Merlin including use of a monorepo. It also covers how the project is set up locally using Docker Compose as well as the CI/CD pipeline and use of Jenkins.

Learn Continuous Integration with Jenkins All in One GuideSam Dias

Jenkins is an open source automation server written in Java that provides continuous integration (CI) services for software development. It can be started via command line or as a web application, running on a servlet container like Apache Tomcat. Jenkins has over 1000 plugins, making it easy to create and automate builds. Continuous integration with Jenkins involves frequent code commits triggering automated builds, compilation, unit testing, and source control integration to provide feedback. The document advertises an online course teaching how to use Jenkins for continuous integration, available for $15 using the coupon code "OFFER15".

The new way to extend VSTS Build and ReleaseJesse Houwing

Extending the new Build and Release features of Visual Studio Team Services (and TFS) helps you turn your scripts into easily re-usable build steps. There are a number of options, from simple scripts to complete custom tasks built using C#, PowerShell or Typescript. We’ll walk through the options and will pros and cons each and quickly walk through the process of building and releasing a custom task to the Visual Studio Marketplace.

Go Pro, Inc. Case Study: Dive into the details of our node.js applicationsAndrew Maxwell

GoPro, Inc. Case study: Dive into the details of our web applicationsAndrew Maxwell

The document discusses GoPro's web applications. It outlines GoPro's goals for their applications, including following the Unix philosophy, isolating apps that connect only through login, basing apps on a common framework, running all apps in Docker, and enabling independent deploys. It also describes their development setup, coding process, problems encountered and solutions, and plans for the future, including continued framework improvements and more testing.

Multi Streaming PlayerGuillaume Chabin

The document introduces a multi-streaming video player project. It discusses the project goals of allowing playback of multiple videos simultaneously. It describes the existing backend and iOS application. It then demonstrates the Android application, discussing its architecture, implementation using FFmpeg, and user interface features. Finally, it outlines opportunities for further improving performance and user experience.

Igor Bondarenko - Process organization of the development modules specific to...Meet Magento Italy

Over the years of my working experience, I have faced the fact that the way development process is organized differs greatly from company to company. At the same time, if we take the development of extensions as a separate subject it may seem to be a short-term activity, which has no particular nuances. In practice, it turns out that the development of an extension is not at all that simple. I want to talk about how we have organized the process of extensions development at our company, and give some recommendations on how to optimize the development process so that to reduce costs and improve your product quality. My report covers the following aspects of the development process: - getting prepared for development: what idea to choose and what to do next - role separation within a team - tools - development of an extension - testing - differences in approaches for Magento and Magento 2 All practices are divided into groups, so listeners can choose those of them that will harmoniously fit into their workflows.

My Git workflowRui Carvalho

The document discusses Git workflows and best practices for managing source code versions. It recommends using small, focused branches for new features or bug fixes, then pushing branches to the remote repository for review and merging. It also recommends forking repositories for outside contributions, where others can submit pull requests to merge changes into the main repository. Following these practices helps keep code organized, allows for easy integration of new changes, and facilitates collaboration.

Develop 4 DevelopersChristian Güdemann

The document discusses the development of the POI4XPages plugin, which allows exporting and importing data between XPages applications and Excel/Word documents. It began from a developer's request to more easily handle recurring tasks of exporting data to office formats. The creator designed the plugin to make these tasks simpler through an extensible plugin model. The document provides advice on open sourcing projects, leveraging existing code, understanding audiences, and making money through reducing complexity and production costs for customers.

$DevOps Fest 2020. Павел Жданов та Никора Никита. Построение процесса CI\CD дл...$ $DevOps Fest 2020. Павел Жданов та Никора Никита. Построение процесса CI\CD дл...$

DevOps Fest 2020. Павел Жданов та Никора Никита. Построение процесса CI\CD дл...DevOps_Fest

Хотя на первый взгляд кажется, что нет никакой разницы, в действительности проприетарные и opensource проекты имеют большое отличие в реализации CI\CD process. Разные команды к которым добавляются неучтенные котрибьютеры работают в разных временных зонах, разработка ведется в условиях недостаточной коммуникации. За добавление новых изменений отвечает не один или несколько человек, а консорциум. В результате, процесс внесения изменений слишком затягивается, увеличивая потенциальные конфликты не только в файлах но и бизнес логике. Все эти особенности вносят свое влияние на устройство CI\CD для open source project. Как он устроен мы и расскажем в нашем докладе.

Git workflowsThuc Le Dong

The document discusses Git workflows, comparing centralized and feature branch workflows. It then describes Vincent Driessen's branching model which uses two main branches (master and develop) and three supporting branch types (feature, release, hotfix). The master branch is stable and used for production, while develop is integrated features. Feature branches branch off develop for new work, and release branches prepare releases by merging to develop and master. Hotfix branches fix production issues. The model aims to support collaboration while keeping branches stable. Special cases in applying the model are also addressed.

EFL QA: Where Are We and Where Should We Go?Samsung Open Source Group

The document discusses the current and missing parts of Samsung's open source QA process. It covers their use of compile-time testing, unit testing, and static analysis currently. Areas missing include runtime testing, graphical unit tests, code coverage, and pre-push continuous integration. The presentation proposes steps like making tests mandatory for new APIs, increasing test coverage 5-10% per release, improving graphical testing, and adding pre-push continuous integration through Jenkins and Phabricator hooks. It ends with questions about these proposals and announcements of job opportunities.

Patterns: The new Javascript framweorkFranco Pellegrini

This document introduces Patterns, a new Javascript framework for Plone. It summarizes the current state of Javascript development in Plone, which involves many individual JS files and no standard testing. The document then proposes adopting existing Javascript tools and best practices, including Yeoman for scaffolding, Grunt for building and testing, Bower for packages, and Mocha for testing. It demonstrates a new approach called Plone Mockup that uses these tools to provide pre-compiled and tested JS code through patterns and bundles. Generators are also introduced to easily set up new Mockup projects which produce a build folder with all necessary JS files.

Introducing Deployit 3.9XebiaLabs

Deployit 3.9 is the latest version of the Application Release Automation platform from XebiaLabs. Key features of Deployit 3.9 include the Deployit Cloud Pack for provisioning test environments in cloud infrastructures, enhanced support for Continuous Delivery of .NET applications, and new Plan Analyzer and Dry Run views for visualizing deployment plans. The updated version also includes additional middleware version support, UI improvements, and new capabilities added in response to customer feedback.

Continuous delivery with open source toolsSebastian Helzle

Continuous Delivery with JenkinsJadson Santos

The document provides an overview of continuous integration and continuous delivery practices. It discusses continuous integration, which involves integrating code changes frequently and verifying them through automated builds and tests. Continuous delivery is described as building software in a way that allows release to production at any time, while continuous deployment means any change is automatically deployed to production. Jenkins, an open source automation server, is introduced as a tool that enables continuous integration and deployment through jobs, credentials, scheduling, build steps, and post-build actions. Pipelines in Jenkins are discussed as dividing deployment into stages to provide quick feedback. The Blue Ocean plugin is highlighted as providing a simplified user interface for Jenkins pipelines.

Pipeline: Continuous Delivery as Code in Jenkins 2.0Jules Pierre-Louis

This document discusses continuous delivery and the new features of Jenkins 2, including pipeline as code. Jenkins 2 introduces the concept of pipeline as a new type that allows defining build pipelines explicitly as code in Jenkinsfiles checked into source control. This enables pipelines to be versioned, more modular through shared libraries, and resumed if interrupted. The document provides examples of creating pipelines with Jenkinsfiles that define stages and steps for builds, tests and deployments.

7 Habits of Highly Effective Jenkins UsersJules Pierre-Louis

Software Delivery in 2016 - A Continuous Delivery ApproachGiovanni Toraldo

Jenkins in the real world - DevOpsCon 2017Gianluca Arbezzano

There are a lot of Continuous Integration services but Jenkins is still one of the most used in most programming languages. In this talk I will share the CurrencyFair experience, how our IT Team made of 40 engineers manage CurrencyFair delivery with GitHub, Jenkins, Hubot and Slack on different environments. Artifact to guarantee the stability of your codebase, pipeline and some Jenkins’s plugins in order to create the most comfortable delivery flow for your projects.

More Related Content

What's hot (16)

Foundations for the perfect technology streamBernd Alter

OpenText MBPM Q&A Webinarconvedo Group

Continuous Delivery com Docker, OpenShift e JenkinsBruno Padilha

Learn Continuous Integration with Jenkins All in One GuideSam Dias

The new way to extend VSTS Build and ReleaseJesse Houwing

Go Pro, Inc. Case Study: Dive into the details of our node.js applicationsAndrew Maxwell

GoPro, Inc. Case study: Dive into the details of our web applicationsAndrew Maxwell

Multi Streaming PlayerGuillaume Chabin

Igor Bondarenko - Process organization of the development modules specific to...Meet Magento Italy

My Git workflowRui Carvalho

Develop 4 DevelopersChristian Güdemann

DevOps Fest 2020. Павел Жданов та Никора Никита. Построение процесса CI\CD дл...DevOps_Fest

Git workflowsThuc Le Dong

EFL QA: Where Are We and Where Should We Go?Samsung Open Source Group

Patterns: The new Javascript framweorkFranco Pellegrini

Introducing Deployit 3.9XebiaLabs

Foundations for the perfect technology streamBernd Alter

OpenText MBPM Q&A Webinarconvedo Group

Continuous Delivery com Docker, OpenShift e JenkinsBruno Padilha

Learn Continuous Integration with Jenkins All in One GuideSam Dias

The new way to extend VSTS Build and ReleaseJesse Houwing

Go Pro, Inc. Case Study: Dive into the details of our node.js applicationsAndrew Maxwell

GoPro, Inc. Case study: Dive into the details of our web applicationsAndrew Maxwell

Multi Streaming PlayerGuillaume Chabin

Igor Bondarenko - Process organization of the development modules specific to...Meet Magento Italy

My Git workflowRui Carvalho

Develop 4 DevelopersChristian Güdemann

DevOps Fest 2020. Павел Жданов та Никора Никита. Построение процесса CI\CD дл...DevOps_Fest

Git workflowsThuc Le Dong

EFL QA: Where Are We and Where Should We Go?Samsung Open Source Group

Patterns: The new Javascript framweorkFranco Pellegrini

Introducing Deployit 3.9XebiaLabs

Similar to Continuous Delivery/Deployment w/ Gitflow, Docker, Jenkins and Rancher (20)

Continuous delivery with open source toolsSebastian Helzle

Continuous Delivery with JenkinsJadson Santos

Pipeline: Continuous Delivery as Code in Jenkins 2.0Jules Pierre-Louis

7 Habits of Highly Effective Jenkins UsersJules Pierre-Louis

Software Delivery in 2016 - A Continuous Delivery ApproachGiovanni Toraldo

Jenkins in the real world - DevOpsCon 2017Gianluca Arbezzano

Pipeline as Code Continuous Delivery with Jenkins Kubernetes and Terraform 1s...naveencwana55

PuppetConf 2016: Continuous Delivery and DevOps with Jenkins and Puppet Enter...Puppet

This document discusses continuous delivery and DevOps practices using Jenkins and Puppet. It defines DevOps as addressing security at every stage and having high-performing teams that spend less time fixing issues. It also discusses the DevOps trinity of people, processes, and tools. Jenkins Pipelines and infrastructure as code with Puppet are presented as key practices for continuous delivery. The integration of Jenkins and Puppet Enterprise is demonstrated for automating application deployments.

Continuous delivery with jenkins pipelines @ devdaysRoman Pickl

Continuous delivery with jenkins pipelines @devops pro moscow Roman Pickl

Jenkins Continuous DeliveryJadson Santos

This document discusses how to build a continuous delivery pipeline using Jenkins. It describes setting up continuous integration, continuous delivery, and continuous deployment processes. Continuous integration involves testing code commits, continuous delivery means software can be released at any time, and continuous deployment automatically deploys releases. The document outlines configuring Jenkins jobs to compile code, run tests, and deploy packages across three stages of a pipeline. It also explains plugins for defining and visualizing the pipeline in Jenkins.

Integração contínua com JenkinsAécio Pires

Nesta apresentação conheceremos as definições de Integração, Entrega e Implantação Contínua e como o uso do Jenkins possibilita a criação de pipelines que ajudam as equipes de desenvolvimento, testes, qualidade e operação na entrega de produtos com maior qualidade aos clientes. Também será apresentado o uso do Jenkins em conjunto com o Gitlab, SonarQube, Maven, Nexus, Docker e Terraform, que é o tema central do livro Integração contínua com Jenkins, publicado em Fevereiro/2019 pela editora Novatec.

Devops CI-CD pipeline with ContainersNuSpace

** Devops CI-CD pipeline using Containers ** by Priyanka Dive, DevOps Engineer/Senior Solutions Architect. Priyanka will briefly introduce DevOps practices and technologies. She will also give a demo of an end-to-end DevOps pipeline using Git (source code management), Jenkins ( continuous integration), Sonarqube (code analysis) with Docker & Kubernetes. Presented at Nulab Drinking Code meetup (30 August 2019): https://www.meetup.com/DrinkingCodeSG/events/263412142/

Continuous Delivery @ Codemotion Miguel Serrano Milano

This document discusses scaling continuous integration (CI) to a continuous delivery (CD) pipeline at a social casino startup with 250k daily active users and ~20 technical staff. It covers decisions around tools, test strategy, deployment frequency, and on-call strategy. It also discusses using trunk-based development versus branching, versioning challenges, and how to optimize the build pipeline graph. Finally, it outlines moving from CI to CD to continuous deployment, with considerations for non-technical processes, feature toggles, and limitations of some domains.

Continuous DeliveryNetcetera

Deployments of larger server applications are often risky and error-prone. They cost development teams, system administrators and customers a lot of nerves and gray hair. The path from the development environment into production is often much more difficult than planned. Continuous Delivery - against all intuition - propagates as the solution for this problem to make more deployments. In this talk, we want to have a look at this paradox and show how ideas from Continuous Delivery can help to optimize the software delivery process. We talk about our experiences in customer projects and what tools we use to automate and optimize our software delivery process, to minimize effort and risk and increase the quality of deployments.

Perforce on Tour 2015 - Optimising the Developer Pipeline: Deliver Faster & ...Perforce

This document discusses continuous delivery and how Perforce enables it. It provides an overview of continuous delivery, best practices for success including team collaboration, flexible workflows, complete visibility and versioning everything. It then discusses common tools and technologies used for continuous integration, infrastructure as code, deployment automation and test automation. Finally, it demonstrates Perforce's capabilities for enabling continuous delivery through a demo of deploying a Jpetstore application from development to production using Perforce and other tools.

Turnkey Continuous DeliveryGianni Bombelli

When it comes to Continuous Integration and Delivery, the common idea is that the tools necessary to practice it are complex and require a lot of study and time to create the basic infrastructure. With this workshop we want to show a "turnkey" solution to experiment the Continuous Delivery technique in just a few minutes! And show that the challenge is not to dominate the tools, but to change ourselves and the way we work and approach this topic.

(Declarative) Jenkins PipelinesSteffen Gebert

This document summarizes a Jenkins pipeline for testing and deploying Chef cookbooks. The pipeline is configured to automatically scan a GitHub organization for any repositories containing a Jenkinsfile. It will then create and manage multibranch pipeline jobs for each repository and branch. The pipelines leverage a shared Jenkins global library which contains pipeline logic to test and deploy the Chef cookbooks. This allows for standardized and reusable pipeline logic across all Chef cookbook repositories.

Continuous delivery with jenkins pipelines @devopsdays cairoRoman Pickl

Continuous Integration & DeliveryJen Wei Lee

This document discusses continuous integration and continuous delivery processes. It describes using tools like Jenkins, Redmine, and SVN/Git for continuous integration to automate code deployment, tracking of issues and changes, and enabling multiple developers to work on the same codebase simultaneously. The goals are to streamline development and deployment, facilitate collaboration between teams, and improve time-to-market for features and fixes while maintaining quality. An overview of the continuous delivery process and screenshots of the tools are provided.

Continuous delivery with open source toolsSebastian Helzle

Continuous Delivery with JenkinsJadson Santos

Pipeline: Continuous Delivery as Code in Jenkins 2.0Jules Pierre-Louis

7 Habits of Highly Effective Jenkins UsersJules Pierre-Louis

Software Delivery in 2016 - A Continuous Delivery ApproachGiovanni Toraldo

Jenkins in the real world - DevOpsCon 2017Gianluca Arbezzano

Pipeline as Code Continuous Delivery with Jenkins Kubernetes and Terraform 1s...naveencwana55

PuppetConf 2016: Continuous Delivery and DevOps with Jenkins and Puppet Enter...Puppet

Continuous delivery with jenkins pipelines @ devdaysRoman Pickl

Continuous delivery with jenkins pipelines @devops pro moscow Roman Pickl

Jenkins Continuous DeliveryJadson Santos

Integração contínua com JenkinsAécio Pires

Devops CI-CD pipeline with ContainersNuSpace

Continuous Delivery @ Codemotion Miguel Serrano Milano

Continuous DeliveryNetcetera

Perforce on Tour 2015 - Optimising the Developer Pipeline: Deliver Faster & ...Perforce

Turnkey Continuous DeliveryGianni Bombelli

(Declarative) Jenkins PipelinesSteffen Gebert

Continuous delivery with jenkins pipelines @devopsdays cairoRoman Pickl

Continuous Integration & DeliveryJen Wei Lee

More from Alin Voinea (17)

EEA and Plone Lightning at Plone Conference 2024 BrasiliaAlin Voinea

EEA & Eau de Web Front-end add-ons - Plone conference 2023 Alin Voinea

This document summarizes various Volto add-ons created by EEA and Eau de Web for customizing the front-end of Plone sites. It describes add-ons for theming, widgets, layout/styling, data visualization, text editing, and other functionalities. Over 100 Volto add-ons are maintained in GitHub repositories and published to NPM. The add-ons are used to build websites like eea.europa.eu and provide features like maps, charts, footnotes, and metadata handling.

EEA Faceted Navigation and Plone 6.pdfAlin Voinea

EEA Volto Add-ons - Plone Conference 2020Alin Voinea

Plone 6 / Volto Dexterity Content Types - Schema & LayoutAlin Voinea

This document discusses Dexterity content types in Plone 6/Volto. It covers defining content type schemas through the TTW schema editor, GenericSetup profiles, and behaviors. It also discusses defining page layouts through blocks, including custom block properties schemas and layout editor. The presenter is Alin Voinea from Eau de Web in Romania, and specializes in Plone, Volto, Python, and related tools.

Docker & rancherAlin Voinea

- Docker allows for OS-level virtualization of applications into lightweight isolated containers. Docker Hub is used to store and distribute Docker images. - Rancher provides tools for orchestrating Docker containers across multiple hosts. The Rancher Catalog allows deploying Dockerized applications in a standardized way using templates that prompt for configurable options. - The document discusses using Docker and Rancher together to build, deploy, manage and scale containerized applications both on a single host and across multiple hosts for production use.

Faceted navigation in Plone 5Alin Voinea

Plone 5 Faceted Navigation is a library that provides faceted navigation and filtering capabilities for Plone. It is compatible with both Plone 4 and 5. It has dropped its dependency on Archetypes and uses zope.schema and z3c.form instead. The JavaScript and CSS resources used for faceted views and editing have been reorganized into bundles. It can be easily added to a Plone 5 Docker container. The library provides faceted widgets and views that can be configured through ZCML.

Docker and ploneAlin Voinea

This document discusses using Docker to deploy and manage Plone CMS installations. It begins by explaining what Docker is and how it provides isolated, consistent environments. It then compares installing and running Plone without Docker versus with Docker. With Docker, the process is simplified and the same environment can be easily replicated. The document also covers developing Plone add-ons within Docker containers, debugging, managing data volumes, running ZEO clusters, extending Docker images, and using Docker Compose and Rancher for orchestration and continuous deployment.

Plone and dockerAlin Voinea

This document discusses how to run Plone, an open source content management system, using Docker. It provides information on Plone versions available as Docker images, how to run Plone 4 and 5 with Docker commands or Docker Compose files, and where to find the Docker images, source code, and support. Additional Plone add-ons can be included by specifying environment variables when running the Docker images.

Kotti CMS 101Alin Voinea

Kotti is a Python web application framework that provides a content management system. It is built on Pyramid and SQLAlchemy and aims to be lightweight, flexible, and developer-friendly compared to alternatives like Plone. Key features include built-in content types, user and workflow management, and integration with common Python packages like Bootstrap, Colander, and Deform. While smaller in scope than Plone, Kotti provides a simpler and more performant alternative for developing CMS applications.

Developing Single Page Applications on Plone using AngularJSAlin Voinea

Responsive design in ploneAlin Voinea

This document discusses how to create high-performing and maintainable Plone themes. It recommends measuring key site sections and performance metrics, optimizing elements like JavaScript loading and resource bundles, and documenting standards through an automated or manual style guide. Maintaining performance requires periodic testing, keeping the style guide updated when features are added, and focusing on the most important user experiences. Automated tools can help monitor for regressions, while setting performance budgets helps guide optimization work.

Plone and dockerAlin Voinea

Display eea’s semantic content with elasticsearch and node.js applications sh...Alin Voinea

New EEA Plone Add-onsAlin Voinea

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.

Python eggs (RO)Alin Voinea

Data visualization in ploneAlin Voinea

EEA DaViz is a plone product which uses Exhibit and Google Charts API to easily create data visualizations based on data from CSV/TSV, JSON, SPARQL endpoints and more. EEA DaViz is the first Semantic web data visualisation tool for Plone CMS, entirely web-based! Main features: - No desktop tools needed to make visualizations. all web based. - Data input: easy copy and paste of data table from any webpage or excel sheet - Data input: drag-and-drop your data from CSV/TSV files, and we do the rest - Data input advanced: retrieve data from any SPARQL endpoint on the fly - Intuitive visualization editor to create interactive charts. - Large amount of visualizations available: Area, Bar, Bubble, Candlestick, Column, Combo Chart, Gauge, Geo Intensity Maps, Line, Pie, Radar, Scatter, Stepped Area, Table, Tree Map, Motion Charts, Faceted search table, Faceted tiles, Faceted timeline, Faceted map and more... - Dashboard. Group charts into one dashboard. - Share any chart. Embeddable visualization in any webpage. - Customizable chart options and colors - Data table manipulation via drag and drop, preparing table for chart - Pivot table (Transpose), transform row values into columns - Modular framework for extending it with more visualizations - And much more...

EEA and Plone Lightning at Plone Conference 2024 BrasiliaAlin Voinea

EEA & Eau de Web Front-end add-ons - Plone conference 2023 Alin Voinea

EEA Faceted Navigation and Plone 6.pdfAlin Voinea

EEA Volto Add-ons - Plone Conference 2020Alin Voinea

Plone 6 / Volto Dexterity Content Types - Schema & LayoutAlin Voinea

Docker & rancherAlin Voinea

Faceted navigation in Plone 5Alin Voinea

Docker and ploneAlin Voinea

Plone and dockerAlin Voinea

Kotti CMS 101Alin Voinea

Developing Single Page Applications on Plone using AngularJSAlin Voinea

Responsive design in ploneAlin Voinea

Plone and dockerAlin Voinea

Display eea’s semantic content with elasticsearch and node.js applications sh...Alin Voinea

New EEA Plone Add-onsAlin Voinea

Python eggs (RO)Alin Voinea

Data visualization in ploneAlin Voinea

Recently uploaded (20)

How John started to like TDD (instead of hating it) (ViennaJUG, June'25)Nacho Cougil

Let me share a story about how John (a developer like any other) started to understand (and enjoy) writing Tests before the Production code. We've all felt an inevitable "tedium" when writing tests, haven't we? If it's boring, if it's complicated or unnecessary? Isn't it? John thought so too, and, as much as he had heard about writing tests before production code, he had never managed to put it into practice, and even when he had tried, John had become even more frustrated at not understanding how to put it into practice outside of a few examples katas 🤷‍♂️ Listen to this story in which I will explain how John went from not understanding Test Driven Development (TDD) to being passionate about it... so much that now he doesn't want to work any other way 😅 ! He must have found some benefits in practising it, right? He says he has more advantages than working in any other way (e.g., you'll find defects earlier, you'll have a faster feedback loop or your code will be easier to refactor), but I'd better explain it to you in the session, right? PS: Think of John as a random person, as if he was even the speaker of this talk 😉 ! --- Presentation shared at ViennaJUG, June'25 Feedback form: https://bit.ly/john-like-tdd-feedback

How Insurance Policy Administration Streamlines Policy Lifecycle for Agile Op...Insurance Tech Services

Build Smarter, Deliver Faster with Choreo - An AI Native Internal Developer P...WSO2

Enterprises must deliver intelligent, cloud native applications quickly—without compromising governance or scalability. This session explores how an internal developer platform increases productivity via AI for code and accelerates AI-native app delivery via code for AI. Learn practical techniques for embedding AI in the software lifecycle, automating governance with AI agents, and applying a cell-based architecture for modularity and scalability. Real-world examples and proven patterns will illustrate how to simplify delivery, enhance developer productivity, and drive measurable outcomes. Learn more: https://wso2.com/choreo

Online Queue Management System for Public Service Offices [Focused on Municip...Rishab Acharya

This report documents the design and development of an Online Queue Management System tailored specifically for municipal offices in Nepal. Municipal offices, as critical providers of essential public services, face challenges including overcrowded queues, long waiting times, and inefficient service delivery, causing inconvenience to citizens and pressure on municipal staff. The proposed digital platform allows citizens to book queue tokens online for various physical services, facilitating efficient queue management and real-time wait time updates. Beyond queue management, the system includes modules to oversee non-physical developmental programs, such as educational and social welfare initiatives, enabling better participation and progress monitoring. Furthermore, it incorporates a module for monitoring infrastructure development projects, promoting transparency and allowing citizens to report issues and track progress. The system development follows established software engineering methodologies, including requirement analysis, UML-based system design, and iterative testing. Emphasis has been placed on user-friendliness, security, and scalability to meet the diverse needs of municipal offices across Nepal. Implementation of this integrated digital platform will enhance service efficiency, increase transparency, and improve citizen satisfaction, thereby supporting the modernization and digital transformation of public service delivery in Nepal.

How to Generate Financial Statements in QuickBooks Like a Pro (1).pdfQuickBooks Training

Are you preparing your budget for the next year, applying for a business credit card or loan, or opening a company bank account? If so, you may find QuickBooks financial statements to be a very useful tool. These statements offer a brief, well-structured overview of your company’s finances, facilitating goal-setting and money management. Don’t worry if you’re not knowledgeable about QuickBooks financial statements. These statements are complete reports from QuickBooks that provide an overview of your company’s financial procedures. They thoroughly view your financial situation by including important features: income, expenses, investments, and disadvantages. QuickBooks financial statements facilitate your financial management and assist you in making wise determinations, regardless of your experience as a business owner.

Generative Artificial Intelligence and its ApplicationsSandeepKS52

The exploration of generative AI begins with an overview of its fundamental concepts, highlighting how these technologies create new content and ideas by learning from existing data. Following this, the focus shifts to the processes involved in training and fine-tuning models, which are essential for enhancing their performance and ensuring they meet specific needs. Finally, the importance of responsible AI practices is emphasized, addressing ethical considerations and the impact of AI on society, which are crucial for developing systems that are not only effective but also beneficial and fair.

AI and Deep Learning with NVIDIA TechnologiesSandeepKS52

Artificial intelligence and deep learning are transforming various fields by enabling machines to learn from data and make decisions. Understanding how to prepare data effectively is crucial, as it lays the foundation for training models that can recognize patterns and improve over time. Once models are trained, the focus shifts to deployment, where these intelligent systems are integrated into real-world applications, allowing them to perform tasks and provide insights based on new information. This exploration of AI encompasses the entire process from initial concepts to practical implementation, highlighting the importance of each stage in creating effective and reliable AI solutions.

Automating Map Production With FME and PythonSafe Software

People still love a good paper map, but every time a request lands on a GIS team’s desk, it takes time to create that perfect, individual map—even when you're ready and have projects prepped. Then come the inevitable changes and iterations that add even more time to the process. This presentation explores a solution for automating map production using FME and Python. FME handles the setup of variables, leveraging GIS reference layers and parameters to manage details like map orientation, label sizes, and layout elements. Python takes over to export PDF maps for each location and template size, uploading them monthly to ArcGIS Online. The result? Fresh, regularly updated maps, ready for anyone to grab anytime—saving you time, effort, and endless revisions while keeping users happy with up-to-date, accessible maps.

Rebuilding Cadabra Studio: AI as Our Core FoundationCadabra Studio

Cadabra Studio set out to reconstruct its core processes, driven entirely by AI, across all functions of its software development lifecycle. This journey resulted in remarkable efficiency improvements of 40–80% and reshaped the way teams collaborate. This presentation shares our challenges and lessons learned in becoming an AI-native firm, including overcoming internal resistance and achieving significant project delivery gains. Discover our strategic approach and transformative recommendations to integrate AI not just as a feature, but as a fundamental element of your operational structure. What changes will AI bring to your company?

Agile Software Engineering MethodologiesGaurav Sharma

Design by Contract - Building Robust Software with Contract-First DevelopmentPar-Tec S.p.A.

In the fast-paced world of software development, code quality and reliability are paramount. This SlideShare deck, presented at PyCon Italia 2025 by Antonio Spadaro, DevOps Engineer at Par-Tec, introduces the “Design by Contract” (DbC) philosophy and demonstrates how a Contract-First Development approach can elevate your projects. Beginning with core DbC principles—preconditions, postconditions, and invariants—these slides define how formal “contracts” between classes and components lead to clearer, more maintainable code. You’ll explore: The fundamental concepts of Design by Contract and why they matter. How to write and enforce interface contracts to catch errors early. Real-world examples showcasing how Contract-First Development improves error handling, documentation, and testability. Practical Python demonstrations using libraries and tools that streamline DbC adoption in your workflow.

How to purchase, license and subscribe to Microsoft Azure_PDF.pdfvictordsane

Microsoft Azure is a cloud platform that empowers businesses with scalable computing, data analytics, artificial intelligence, and cybersecurity capabilities. Arguably the biggest hurdle for most organizations is understanding how to get started. Microsoft Azure is a consumption-based cloud service. This means you pay for what you use. Unlike traditional software, Azure resources (e.g., VMs, databases, storage) are billed based on usage time, storage size, data transfer, or resource configurations. There are three primary Azure purchasing models: • Pay-As-You-Go (PAYG): Ideal for flexibility. Billed monthly based on actual usage. • Azure Reserved Instances (RI): Commit to 1- or 3-year terms for predictable workloads. This model offers up to 72% cost savings. • Enterprise Agreements (EA): Best suited for large organizations needing comprehensive Azure solutions and custom pricing. Licensing Azure: What You Need to Know Azure doesn’t follow the traditional “per seat” licensing model. Instead, you pay for: • Compute Hours (e.g., Virtual Machines) • Storage Used (e.g., Blob, File, Disk) • Database Transactions • Data Transfer (Outbound) Purchasing and subscribing to Microsoft Azure is more than a transactional step, it’s a strategic move. Get in touch with our team of licensing experts via [email protected] to further understand the purchasing paths, licensing options, and cost management tools, to optimize your investment.

Leveraging Foundation Models to Infer IntentsKeheliya Gallaba

Invited Talk at RAISE 2025: Requirements engineering for AI-powered SoftwarE Workshop co-located with ICSE, the IEEE/ACM International Conference on Software Engineering. Abstract: Foundation Models (FMs) have shown remarkable capabilities in various natural language tasks. However, their ability to accurately capture stakeholder requirements remains a significant challenge for using FMs for software development. This paper introduces a novel approach that leverages an FM-powered multi-agent system called AlignMind to address this issue. By having a cognitive architecture that enhances FMs with Theory-of-Mind capabilities, our approach considers the mental states and perspectives of software makers. This allows our solution to iteratively clarify the beliefs, desires, and intentions of stakeholders, translating these into a set of refined requirements and a corresponding actionable natural language workflow in the often-overlooked requirements refinement phase of software engineering, which is crucial after initial elicitation. Through a multifaceted evaluation covering 150 diverse use cases, we demonstrate that our approach can accurately capture the intents and requirements of stakeholders, articulating them as both specifications and a step-by-step plan of action. Our findings suggest that the potential for significant improvements in the software development process justifies these investments. Our work lays the groundwork for future innovation in building intent-first development environments, where software makers can seamlessly collaborate with AIs to create software that truly meets their needs.

iOS Developer Resume 2025 | Pramod KumarPramod Kumar

Explore the professional resume of Pramod Kumar, a skilled iOS developer with extensive experience in Swift, SwiftUI, and mobile app development. This portfolio highlights key projects, technical skills, and achievements in app design and development, showcasing expertise in creating intuitive, high-performance iOS applications. Ideal for recruiters and tech managers seeking a talented iOS engineer for their team.

Micro-Metrics Every Performance Engineer Should Validate Before Sign-OffTier1 app

When it comes to performance testing, most engineers instinctively gravitate toward the big-picture indicators—response time, memory usage, throughput. But what about the smaller, more subtle indicators that quietly shape your application’s performance and stability? we explored the hidden layer of performance diagnostics that too often gets overlooked: micro-metrics. These small but mighty data points can reveal early signs of trouble long before they manifest as outages or degradation in production. From garbage collection behavior and object creation rates to thread state transitions and blocked thread patterns, we unpacked the critical micro-metrics every performance engineer should assess before giving the green light to any release. This session went beyond the basics, offering hands-on demonstrations and JVM-level diagnostics that help identify performance blind spots traditional tests tend to miss. We showed how early detection of these subtle anomalies can drastically reduce post-deployment issues and production firefighting. Whether you're a performance testing veteran or new to JVM tuning, this session helped shift your validation strategies left—empowering you to detect and resolve risks earlier in the lifecycle.

Software Engineering Process, Notation & Tools Introduction - Part 3Gaurav Sharma

Integration Ignited Redefining Event-Driven Architecture at Wix - EventCentricNatan Silnitsky

At Wix, we revolutionized our platform by making integration events the backbone of our 4,000-microservice ecosystem. By abandoning traditional domain events for standardized Protobuf events through Kafka, we created a universal language powering our entire architecture. We'll share how our "single-aggregate services" approach—where every CUD operation triggers semantic events—transformed scalability and extensibility, driving efficient event choreography, data lake ingestion, and search indexing. We'll address our challenges: balancing consistency with modularity, managing event overhead, and solving consumer lag issues. Learn how event-based data prefetches dramatically improved performance while preserving the decoupling that makes our platform infinitely extensible. Key Takeaways: - How integration events enabled unprecedented scale and extensibility - Practical strategies for event-based data prefetching that supercharge performance - Solutions to common event-driven architecture challenges - When to break conventional architectural rules for specific contexts

IBM Rational Unified Process For Software Engineering - IntroductionGaurav Sharma

Providing Better Biodiversity Through Better DataSafe Software

This session explores how FME is transforming data workflows at Ireland’s National Biodiversity Data Centre (NBDC) by eliminating manual data manipulation, incorporating machine learning, and enhancing overall efficiency. Attendees will gain insight into how NBDC is using FME to document and understand internal processes, make decision-making fully transparent, and shine a light on underlying code to improve clarity and reduce silent failures. The presentation will also outline NBDC’s future plans for FME, including empowering staff to access and query data independently, without relying on external consultants. It will also showcase ambitions to connect to new data sources, unlock the full potential of its valuable datasets, create living atlases, and place its valuable data directly into the hands of decision-makers across Ireland—ensuring that biodiversity is not only protected but actively enhanced.

Essentials of Resource Planning in a DownturnOnePlan Solutions

How John started to like TDD (instead of hating it) (ViennaJUG, June'25)Nacho Cougil

How Insurance Policy Administration Streamlines Policy Lifecycle for Agile Op...Insurance Tech Services

Build Smarter, Deliver Faster with Choreo - An AI Native Internal Developer P...WSO2

Online Queue Management System for Public Service Offices [Focused on Municip...Rishab Acharya

How to Generate Financial Statements in QuickBooks Like a Pro (1).pdfQuickBooks Training

Generative Artificial Intelligence and its ApplicationsSandeepKS52

AI and Deep Learning with NVIDIA TechnologiesSandeepKS52

Automating Map Production With FME and PythonSafe Software

Rebuilding Cadabra Studio: AI as Our Core FoundationCadabra Studio

Agile Software Engineering MethodologiesGaurav Sharma

Design by Contract - Building Robust Software with Contract-First DevelopmentPar-Tec S.p.A.

How to purchase, license and subscribe to Microsoft Azure_PDF.pdfvictordsane

Leveraging Foundation Models to Infer IntentsKeheliya Gallaba

iOS Developer Resume 2025 | Pramod KumarPramod Kumar

Micro-Metrics Every Performance Engineer Should Validate Before Sign-OffTier1 app

Software Engineering Process, Notation & Tools Introduction - Part 3Gaurav Sharma

Integration Ignited Redefining Event-Driven Architecture at Wix - EventCentricNatan Silnitsky

IBM Rational Unified Process For Software Engineering - IntroductionGaurav Sharma

Providing Better Biodiversity Through Better DataSafe Software

Essentials of Resource Planning in a DownturnOnePlan Solutions