A bit of a different format for BathCamp in June. We’ll be cage fighting.
No.
Actually, it’s a sort of follow on from our previous BathCamp – a comparison of as many CMS systems as we can get people to talk about.
Obviously any comparison of CMS system is heavily caveated with an “it depends…” but nonetheless we think it’ll be interesting to hear from people talking about the good, the bad and the ugly of the systems they use.
The format of the talks will be “5 things I love about this CMS and 5 things I hate”, followed by time for questions and general CMS-like banter.
We’ve got the following lined up:
WordPress
Drupal
Expression Engine
Plone
PyroCMS
Perch
Umbraco
Defacto
Jekyll is a simple, static site generator that allows users to easily create blogs and websites that can be hosted on GitHub. It provides benefits over traditional blogging platforms by allowing users to focus on content instead of design or programming. Jekyll works by converting Markdown and HTML files into static HTML files that can be hosted anywhere without a database.
The document discusses 10 common gotchas or mistakes when using the Mongoid ORM for MongoDB in production applications. It begins with introductions and then lists the 10 gotchas as follows: MongoDB is not relational, MongoDB only uses one index per query, nil does not unset a field, nil is not the opposite of exist, BigDecimal type sorts alphabetically, embedded objects must have an embedded_in declared, indexes don’t get created on embedded objects, scopes should go on the parent object, callbacks on embedded objects are not run by default, and don’t try to perform two atomic operations on the same field in the same call. It concludes by thanking the audience and providing links to additional resources.
Most people know how to organize their code with one app. But...what about when you are managing many different apps? Do you use one monorepo or many smaller repos? Where does your shared code live? How do you manage breaking changes across your apps?
In this talk, I draw from my own experience to lay out the different options available and provide my recommendations for best practices with the management of many different apps under the same umbrella.
Joomla! Pizza Bugs and Fun 2014 pre-event SeminarGunjan Patel
Joomla! Issue Bug Tracking process
Joomla! Pizza Bugs and Fun event 17th Oct 2014 on Friday. Presenting Joomla! Bug Squad workflow and Bug tracking process to the world. It's an pre-event preparation for participating companies like Tailored Solutions Pvt. Ltd. iJoomer, xpertphp, Percept info.
Static site generators and the JAMStack are all the rage right now. After trying several different tools to generate Static Sites, I recently discovered Eleventy and after building a few websites with it I feel like I am in love! In this presentation, I will try to explain why is that!
This document discusses version control and Git. It explains that version control allows developers to maintain stability and continuity in websites/applications by saving versions. Git tracks differences between commits, is distributed for less server overhead, and makes complex workflows easier to manage. The document provides examples of basic Git commands and realistic workflows for development, deployment, using branches, merging, and other "cool stuff" like hooks, stash, and reset. Resources are also included for learning more about Git vs Subversion and deploying with Git.
A bit of a different format for BathCamp in June. We’ll be cage fighting.
No.
Actually, it’s a sort of follow on from our previous BathCamp – a comparison of as many CMS systems as we can get people to talk about.
Obviously any comparison of CMS system is heavily caveated with an “it depends…” but nonetheless we think it’ll be interesting to hear from people talking about the good, the bad and the ugly of the systems they use.
The format of the talks will be “5 things I love about this CMS and 5 things I hate”, followed by time for questions and general CMS-like banter.
We’ve got the following lined up:
WordPress
Drupal
Expression Engine
Plone
PyroCMS
Perch
Umbraco
Defacto
Jekyll is a simple, static site generator that allows users to easily create blogs and websites that can be hosted on GitHub. It provides benefits over traditional blogging platforms by allowing users to focus on content instead of design or programming. Jekyll works by converting Markdown and HTML files into static HTML files that can be hosted anywhere without a database.
The document discusses 10 common gotchas or mistakes when using the Mongoid ORM for MongoDB in production applications. It begins with introductions and then lists the 10 gotchas as follows: MongoDB is not relational, MongoDB only uses one index per query, nil does not unset a field, nil is not the opposite of exist, BigDecimal type sorts alphabetically, embedded objects must have an embedded_in declared, indexes don’t get created on embedded objects, scopes should go on the parent object, callbacks on embedded objects are not run by default, and don’t try to perform two atomic operations on the same field in the same call. It concludes by thanking the audience and providing links to additional resources.
Most people know how to organize their code with one app. But...what about when you are managing many different apps? Do you use one monorepo or many smaller repos? Where does your shared code live? How do you manage breaking changes across your apps?
In this talk, I draw from my own experience to lay out the different options available and provide my recommendations for best practices with the management of many different apps under the same umbrella.
Joomla! Pizza Bugs and Fun 2014 pre-event SeminarGunjan Patel
Joomla! Issue Bug Tracking process
Joomla! Pizza Bugs and Fun event 17th Oct 2014 on Friday. Presenting Joomla! Bug Squad workflow and Bug tracking process to the world. It's an pre-event preparation for participating companies like Tailored Solutions Pvt. Ltd. iJoomer, xpertphp, Percept info.
Static site generators and the JAMStack are all the rage right now. After trying several different tools to generate Static Sites, I recently discovered Eleventy and after building a few websites with it I feel like I am in love! In this presentation, I will try to explain why is that!
This document discusses version control and Git. It explains that version control allows developers to maintain stability and continuity in websites/applications by saving versions. Git tracks differences between commits, is distributed for less server overhead, and makes complex workflows easier to manage. The document provides examples of basic Git commands and realistic workflows for development, deployment, using branches, merging, and other "cool stuff" like hooks, stash, and reset. Resources are also included for learning more about Git vs Subversion and deploying with Git.
Heroku is a cloud-based hosting platform for Ruby on Rails applications. It allows developers to deploy their Rails apps through Git and manage hosting without having to deal with servers. Developers can run rake tasks, access the application console, interact with databases, add gems, and scale dynos and workers as needed when traffic increases. Heroku also offers add-ons for services like databases, email delivery, search, and caching.
Contributing to WordPress - Software Freedom Day 2015 (Mumbai)Alexander Gounder
The document discusses different ways to contribute to the WordPress open source project, including development, design, documentation, translation, and community support. It provides links to resources on the WordPress site for contributing code, testing, reporting bugs, writing documentation, and participating in language translation projects. The document encourages contributing to WordPress and provides reminders about following GPL licensing and asking for help.
Web, Native iOS and Native Android with One Ember.js AppFITC
FITC events. For digital creators.
Save 10% off ANY FITC event with discount code 'slideshare'
See our upcoming events at www.fitc.ca
Web, Native iOS and Native Android with One Ember.js App
with Alexander Blom
OVERVIEW
Many companies maintain a separate repo for web and native mobile applications, and sometimes yet another for mobile web. Historically you may hear that ‘wrapped applications’ are slower and choppy. This is no longer the case – if your application is structured correctly.
By using Ember.js with Cordova, it is possible to have a single code base powering all four (desktop web, mobile web, native iOS and native Android). Outside of the immediate cost/programming time savings, this technique enables you to build future iterations faster and stop the out of sync issues plaguing many code bases (e.g. the Android app has different features to iOS).
OBJECTIVE
Learn how to write a single code base which works on all platforms without the presumed drawbacks.
TARGET AUDIENCE
Developers/managers working on one of the three mentioned platforms, and who wish to no longer maintain separate code bases for each platform.
ASSUMED AUDIENCE KNOWLEDGE
A general knowledge of how either backend, front-end or mobile applications are developed is helpful.
FIVE THINGS AUDIENCE MEMBERS WILL LEARN
How to build a single code base working on all platforms
What changes (if any) are required in the code base to achieve this
How to avoid common draw-backs of wrapped applications, such as perceived slowness
How to access native phone functions without muddling up the code base
How such applications are packaged and deployed
The document discusses plans to merge jQuery UI and jQuery Mobile to create code that works across all devices and environments. Key points include:
1) Creating a shared CSS framework and responsive widgets for layouts and user interfaces.
2) Developing techniques like SVG icons with PNG fallbacks to optimize performance across different platforms and devices.
3) Building a common widget factory and APIs to create reusable and customizable interface elements that work with or without JavaScript.
4) Continuing to improve form controls and other widgets to provide consistent styling and interactions across all form factors.
This document discusses strategies for adopting Agile practices stealthily within an organization. It suggests avoiding mentioning Agile publicly and focusing Agile efforts on critical code through techniques like test-driven development, pair programming, and code dojos. Other recommendations include iterative planning over long-term planning and motivating employees intrinsically rather than through bonuses. The overall aim is to gain benefits of Agile while keeping costs low initially during cultural transition.
Our CSS sucks. We've been building sites for over a decade using crappy, ornamentation techniques and shoddy selectors. Our styles unintentional bleed across the site. Our stylesheets are fragile and unmaintainable and full of specificity landmines. Pandas wander alone in the wilderness.
But there's no need to drown ourselves in beer. New technologies like Web Components and new techniques like OOCSS, SMACSS and BEM show us that planning before building can make our projects maintainable, easier to debug, and smaller with reduced CSS file sizes.
This session will introduce the basic techniques for CSS layering and using design components, the heart of any front-end CSS project. We will also discuss CSS/Sass organization and tips to more easily implement these ideas.
Style Guide Driven Development: All Hail the Robot Overlords!John Albin Wilkins
This document discusses style guide driven front-end development. It promotes building websites using modular, reusable design components and maintaining automated style guides to document components. Components are named using conventions like BEM to ensure they are self-contained and nestable. Automated style guides help designers, developers and others understand the design system. Maintaining up-to-date documentation is important for effective collaboration across teams.
Building Mobile Apps using HTML CSS & JavascriptMoses Ngone
The document discusses how to build an app using HTML, CSS, and JavaScript. It recommends getting multiple devices, choosing a mobile platform like Android or iOS, and a development tool like PhoneGap. It lists common mobile platforms and tools for app development. The goal is to frequently test apps on devices until the developer's skills improve.
The document lists the various software and tools used during a film production project. Blogger was the primary website for uploading work. Microsoft Word was used for documents like treatments, research, and audience analysis. Scribd converted Word docs to HTML for posting on Blogger. Bubbl.us created brainstorms and PowToon was used for presentations instead of PowerPoint. Gmail facilitated communication and sharing files. Social media like Instagram, Twitter, and Facebook promoted the film. Prezi and Final Cut Pro were also utilized for presentations and editing respectively.
Cordova 3.x is a hybrid mobile app development framework that allows building apps that can run on multiple platforms including Android, iOS, and Windows Phone. Key differences between Cordova 2.x and 3.x include plugins no longer being included and changes to platforms. Cordova uses a command line interface to automate project setup and requires configuration files and packages.json. The config.xml file follows W3C widget standards and is important for native platform configuration. Developers can use IDEs like Eclipse or Xcode for native tools or cloud-based build services like PhoneGap Build.
The second most important thing you can do is ship something good. The most important thing you can do? Ship something. I love testing and performance optimization and pixel tweaking as much as the next person, but if you never ship then you might as well have never started.
This document summarizes Tracy Lee's presentation on her three favorite CLI tools: Create React App, Angular CLI, and Ember CLI. She discusses how CLI tools make web development accessible, allow automatic set up of development environments, and handle tasks like compiling and testing. Tracy explains how the tools architect applications, provide live reloading, and allow adding addons. She demonstrates creating new projects with each CLI tool and shares some projects she built with them.
An introduction to Angular Material (2) using Angular Material, Angular (2x), and Angular-CLI. Github repo as started + finished branches: https://github.com/ladyleet/ng-vikings-one
http://twitter.com/ladyleet for questions! :)
An Introduction Into Using Angular’s Material DesignTracy Lee
Angular Material 2 has been evolving over the course of the past year, and it has finally become stable enough to use in production. Get familiar with the various components of Angular Material, how to use them in your app, and a few tips and tricks to getting started.
The document provides guidelines for creating page objects that are DRY (Don't Repeat Yourself) when testing web applications. Page objects should provide an API of page actions without exposing web elements, initialize themselves, follow the builder pattern, and avoid duplication to keep code DRY. The document ends by inviting further discussion on page object best practices on the #selenium chat or via Twitter.
Headless Drupal is very easy to understand concept. The 2 key differences of headless Drupal from Drupal are: Instead of converting data to HTML, Drupal converts it into in JSON format. AngularJS, EmberJS or React, kind of frontend frameworks then render the data to create a webpage.
Run stuff, Deploy Stuff, Jax London 2017 EditionKris Buytaert
This document summarizes a presentation on DevOps by Kris Buytaert. It discusses how development and operations teams used to have different goals, leading to blame between teams. DevOps aims to change culture to emphasize automation, measurement, and sharing between teams. It also discusses challenges like code that is difficult to deploy, configure, run, cluster, secure or monitor in production. The presenter advocates for defining requirements like monitoring and logs to consider work "done", and measuring everything to improve.
Heroku is a cloud-based hosting platform for Ruby on Rails applications. It allows developers to deploy their Rails apps through Git and manage hosting without having to deal with servers. Developers can run rake tasks, access the application console, interact with databases, add gems, and scale dynos and workers as needed when traffic increases. Heroku also offers add-ons for services like databases, email delivery, search, and caching.
Contributing to WordPress - Software Freedom Day 2015 (Mumbai)Alexander Gounder
The document discusses different ways to contribute to the WordPress open source project, including development, design, documentation, translation, and community support. It provides links to resources on the WordPress site for contributing code, testing, reporting bugs, writing documentation, and participating in language translation projects. The document encourages contributing to WordPress and provides reminders about following GPL licensing and asking for help.
Web, Native iOS and Native Android with One Ember.js AppFITC
FITC events. For digital creators.
Save 10% off ANY FITC event with discount code 'slideshare'
See our upcoming events at www.fitc.ca
Web, Native iOS and Native Android with One Ember.js App
with Alexander Blom
OVERVIEW
Many companies maintain a separate repo for web and native mobile applications, and sometimes yet another for mobile web. Historically you may hear that ‘wrapped applications’ are slower and choppy. This is no longer the case – if your application is structured correctly.
By using Ember.js with Cordova, it is possible to have a single code base powering all four (desktop web, mobile web, native iOS and native Android). Outside of the immediate cost/programming time savings, this technique enables you to build future iterations faster and stop the out of sync issues plaguing many code bases (e.g. the Android app has different features to iOS).
OBJECTIVE
Learn how to write a single code base which works on all platforms without the presumed drawbacks.
TARGET AUDIENCE
Developers/managers working on one of the three mentioned platforms, and who wish to no longer maintain separate code bases for each platform.
ASSUMED AUDIENCE KNOWLEDGE
A general knowledge of how either backend, front-end or mobile applications are developed is helpful.
FIVE THINGS AUDIENCE MEMBERS WILL LEARN
How to build a single code base working on all platforms
What changes (if any) are required in the code base to achieve this
How to avoid common draw-backs of wrapped applications, such as perceived slowness
How to access native phone functions without muddling up the code base
How such applications are packaged and deployed
The document discusses plans to merge jQuery UI and jQuery Mobile to create code that works across all devices and environments. Key points include:
1) Creating a shared CSS framework and responsive widgets for layouts and user interfaces.
2) Developing techniques like SVG icons with PNG fallbacks to optimize performance across different platforms and devices.
3) Building a common widget factory and APIs to create reusable and customizable interface elements that work with or without JavaScript.
4) Continuing to improve form controls and other widgets to provide consistent styling and interactions across all form factors.
This document discusses strategies for adopting Agile practices stealthily within an organization. It suggests avoiding mentioning Agile publicly and focusing Agile efforts on critical code through techniques like test-driven development, pair programming, and code dojos. Other recommendations include iterative planning over long-term planning and motivating employees intrinsically rather than through bonuses. The overall aim is to gain benefits of Agile while keeping costs low initially during cultural transition.
Our CSS sucks. We've been building sites for over a decade using crappy, ornamentation techniques and shoddy selectors. Our styles unintentional bleed across the site. Our stylesheets are fragile and unmaintainable and full of specificity landmines. Pandas wander alone in the wilderness.
But there's no need to drown ourselves in beer. New technologies like Web Components and new techniques like OOCSS, SMACSS and BEM show us that planning before building can make our projects maintainable, easier to debug, and smaller with reduced CSS file sizes.
This session will introduce the basic techniques for CSS layering and using design components, the heart of any front-end CSS project. We will also discuss CSS/Sass organization and tips to more easily implement these ideas.
Style Guide Driven Development: All Hail the Robot Overlords!John Albin Wilkins
This document discusses style guide driven front-end development. It promotes building websites using modular, reusable design components and maintaining automated style guides to document components. Components are named using conventions like BEM to ensure they are self-contained and nestable. Automated style guides help designers, developers and others understand the design system. Maintaining up-to-date documentation is important for effective collaboration across teams.
Building Mobile Apps using HTML CSS & JavascriptMoses Ngone
The document discusses how to build an app using HTML, CSS, and JavaScript. It recommends getting multiple devices, choosing a mobile platform like Android or iOS, and a development tool like PhoneGap. It lists common mobile platforms and tools for app development. The goal is to frequently test apps on devices until the developer's skills improve.
The document lists the various software and tools used during a film production project. Blogger was the primary website for uploading work. Microsoft Word was used for documents like treatments, research, and audience analysis. Scribd converted Word docs to HTML for posting on Blogger. Bubbl.us created brainstorms and PowToon was used for presentations instead of PowerPoint. Gmail facilitated communication and sharing files. Social media like Instagram, Twitter, and Facebook promoted the film. Prezi and Final Cut Pro were also utilized for presentations and editing respectively.
Cordova 3.x is a hybrid mobile app development framework that allows building apps that can run on multiple platforms including Android, iOS, and Windows Phone. Key differences between Cordova 2.x and 3.x include plugins no longer being included and changes to platforms. Cordova uses a command line interface to automate project setup and requires configuration files and packages.json. The config.xml file follows W3C widget standards and is important for native platform configuration. Developers can use IDEs like Eclipse or Xcode for native tools or cloud-based build services like PhoneGap Build.
The second most important thing you can do is ship something good. The most important thing you can do? Ship something. I love testing and performance optimization and pixel tweaking as much as the next person, but if you never ship then you might as well have never started.
This document summarizes Tracy Lee's presentation on her three favorite CLI tools: Create React App, Angular CLI, and Ember CLI. She discusses how CLI tools make web development accessible, allow automatic set up of development environments, and handle tasks like compiling and testing. Tracy explains how the tools architect applications, provide live reloading, and allow adding addons. She demonstrates creating new projects with each CLI tool and shares some projects she built with them.
An introduction to Angular Material (2) using Angular Material, Angular (2x), and Angular-CLI. Github repo as started + finished branches: https://github.com/ladyleet/ng-vikings-one
http://twitter.com/ladyleet for questions! :)
An Introduction Into Using Angular’s Material DesignTracy Lee
Angular Material 2 has been evolving over the course of the past year, and it has finally become stable enough to use in production. Get familiar with the various components of Angular Material, how to use them in your app, and a few tips and tricks to getting started.
The document provides guidelines for creating page objects that are DRY (Don't Repeat Yourself) when testing web applications. Page objects should provide an API of page actions without exposing web elements, initialize themselves, follow the builder pattern, and avoid duplication to keep code DRY. The document ends by inviting further discussion on page object best practices on the #selenium chat or via Twitter.
Headless Drupal is very easy to understand concept. The 2 key differences of headless Drupal from Drupal are: Instead of converting data to HTML, Drupal converts it into in JSON format. AngularJS, EmberJS or React, kind of frontend frameworks then render the data to create a webpage.
Run stuff, Deploy Stuff, Jax London 2017 EditionKris Buytaert
This document summarizes a presentation on DevOps by Kris Buytaert. It discusses how development and operations teams used to have different goals, leading to blame between teams. DevOps aims to change culture to emphasize automation, measurement, and sharing between teams. It also discusses challenges like code that is difficult to deploy, configure, run, cluster, secure or monitor in production. The presenter advocates for defining requirements like monitoring and logs to consider work "done", and measuring everything to improve.
The document discusses the frontend single point of failure (SPOF) problem caused by blocking JavaScript and CSS files. It provides examples of popular websites, code libraries, widgets, and content management systems that contribute to frontend SPOFs. The document recommends solutions for browsers, widget owners, CMS developers, and site owners to address this issue through asynchronous loading of resources and better monitoring of frontend performance.
Continuous Integration, the minimum viable productJulian Simpson
What does it mean to 'do' Continuous Integration? It used to be enough to execute your unit tests in CI. But the bar is steadily raising for engineering practices. In the last decade we've seen tremendous improvements inacceptance testing. JavaScript is now a platform in it's own right. Cloudcomputing is now vital. There's growing interest in deployment to prod.So Continuous Integration is under more pressure than ever. As the bar slowly raises for engineering practices, we ll present 2011's minimum viable feature set for Continuous Integration
Essential Plone development tools - Plone conf 2012Kim Chee Leong
Slides for the talk given at Plone Conference 2012. In the following collective package further explaination can be found about the tools discussed: https://github.com/collective/collective.exampledevtools
Integrating multiple CDN providers at Etsy - Velocity Europe (London) 2013Marcus Barczak
The document discusses Etsy's experience integrating multiple content delivery network (CDN) providers. Etsy began using a single CDN in 2008 but then investigated using multiple CDNs in 2012 to improve resilience, flexibility, and costs. They developed an evaluation criteria and testing process to initially configure and test the CDNs with non-critical traffic before routing production traffic. Etsy then implemented methods for balancing traffic across CDNs using DNS and monitoring the performance of the CDNs and origin infrastructure.
Is Docker really the security risk that is generally raged about? Or, is this more about understanding where and when a business should consider adoption new and revolutionary infrastructure?
This document contains the agenda for a Docker Meetup event. It lists the scheduled talks and their topics, which include introductions to Docker, Kubernetes, and using containers with an ELK stack. It also provides logistical details like the date, location, and organizers of the meetup. Finally, it includes introductory information about Docker concepts like images, containers, and running a simple "whalesay" demo container.
jQTouch – Mobile Web Apps with HTML, CSS and JavaScriptPhilipp Bosch
The document discusses jQTouch, a plugin for jQuery that allows developers to build mobile web apps with HTML, CSS, and JavaScript. It works by turning regular web pages into touch-friendly "apps" that can be added to a mobile device's home screen. Key points covered include:
- jQTouch uses jQuery and adds iPhone-style UI elements and themes
- It supports animations between "pages" and touch events
- Combined with PhoneGap, web apps built with jQTouch can be wrapped into native mobile apps and distributed through app stores
- The presentation demonstrates jQTouch's capabilities and provides information on getting started and further resources
This document discusses how to approach UX design in an Agile development process. It acknowledges that Agile processes do not typically allow for big upfront design efforts. It then provides suggestions for integrating UX work into Agile planning and iterations, including aligning UX strategies with Agile concepts, exploiting automation for certain tests, and addressing UX debt periodically. The document emphasizes continuous collaboration between designers and other roles to ensure user needs are considered throughout planning and development.
Drupal powers many small-to-medium websites, from personal blogs to company intranets. Drupal also powers big sites like The Economist and The White House. How are the big sites different from the small ones? What are the main issues to consider when adopting Drupal for the enterprise? What skillset do developers need to build them?
This document discusses ways to enhance security for the OpenSSH secure shell program. It provides tips for securing the OpenSSH server configuration by using allow/deny rules, matching rules, and alternatives to trusting hosts on first use. It also discusses securing SSH access with authorized keys by automating key distribution and restricting key options. The document focuses on common sense approaches and avoiding security fatigue when configuring OpenSSH.
2014 09-10-12 Building Customer Profiles - Move from clicks to facesVinoaj Vijeyakumaar
This document contains a presentation by Vinoaj Vijeyakumaar on building customer profiles using Google Analytics demographic reports. The presentation discusses how to use demographic reports to gain insights into customers' gender, age, interests and behaviors in order to better target and engage valuable customer segments. It provides steps to identify differences in customer patterns, drill down into customer interests, segment customers, and retarget valuable segments through various online and offline channels.
- Mojolicious is a web development framework for Perl that aims to rethink web development
- It provides a powerful routing system, full HTTP implementation, simple templating, built-in JSON support, elegant plugin system, and class reloader
- Installation is simple using CPAN and has no dependencies beyond Perl 5.8.1
- It includes classes for requests, responses, templates, JSON encoding/decoding, and more
- Plugins can hook into various stages of the request lifecycle
- Supports generating applications, running commands, and provides a simple but powerful way to build web applications and services in Perl
The document discusses the author's experience developing a simple 3D engine called A3. It provides biographical information about the author and explains his motivations for creating the engine, including learning opportunities and a desire to share his work. It outlines goals such as keeping the API and codebase lean, generating documentation automatically, and recording tutorial videos. Key features implemented so far include geometry, lighting, texturing and cameras. Sample applications are provided. The conclusion encourages setting goals, refactoring, asking for help, writing samples, sharing work, and pursuing ambitious ideas.
Emacs verilog-mode is coming to Debian, againKiwamu Okabe
The document discusses bringing the Emacs verilog-mode package to Debian. It details that verilog-mode provides syntax highlighting and other features for editing Verilog code. The author files an ITP (Intent to Package) request to add verilog-mode to Debian. Instructions are provided on using git-buildpackage to manage the package sources and releases from the upstream GitHub repository. This will make verilog-mode easily available to Emacs users on Debian systems.
Automating MySQL operations with PuppetKris Buytaert
This document summarizes a presentation about automating MySQL operations with Puppet. It discusses:
- Why automation is important for consistency, security, and disaster recovery. Manual changes can introduce bugs and inconsistencies.
- Puppet is an open source configuration management tool that can be used to automate MySQL configuration, users, backups, replication, and high availability clustering with tools like Corosync/Pacemaker.
- Puppet modules define the desired state and Puppet ensures the actual state matches by making necessary changes. This provides auditability and change tracking through version control of Puppet code.
Web technologies are evolving at such a frenetic pace that it becomes almost mandatory to learn on your own. A lot of us still depend on other people to do this learning for us, and we tend to use their answers to solve our everyday problems.
Inconsistent implementations, rapidly evolving specs, questionable performance impacts and maintenance implications mean we cannot always depend on others for answers but must involve ourselves actively in the process of developing specifications for new Web technologies. But how do we go about it?
There are some simple rituals we can all do, which can have us be better-informed and also better inform the people and groups who are most directly involved in the development of new Web technologies.
Icinga Web 2 is more - Module magic at Icinga Camp San FranciscoIcinga
The document discusses Icinga Web 2 and its features. It describes several existing and prototype modules, including graphs, trouble tickets, and monitoring additional entity types beyond just hosts and services. It encourages developers to build their own modules and provides an overview of how to structure modules and leverage the front-end framework for CSS, JavaScript, translations and more. A live demo is promised to illustrate Icinga Web 2's capabilities.
Continuous Integration with Open Source Tools - PHPUgFfm 2014-11-20Michael Lihs
Presentation about open source tools to set up continuous integration and continuous deployment. Covers Git, Gitlab, Chef, Vagrant, Jenkins, Gatling, Dashing, TYPO3 Surf and some other tools. Shows some best practices for testing with Behat and Functional Testing.
Discover the benefits of outsourcing SEO to Indiadavidjhones387
"Discover the benefits of outsourcing SEO to India! From cost-effective services and expert professionals to round-the-clock work advantages, learn how your business can achieve digital success with Indian SEO solutions.
Ready to Unlock the Power of Blockchain!Toptal Tech
Imagine a world where data flows freely, yet remains secure. A world where trust is built into the fabric of every transaction. This is the promise of blockchain, a revolutionary technology poised to reshape our digital landscape.
Toptal Tech is at the forefront of this innovation, connecting you with the brightest minds in blockchain development. Together, we can unlock the potential of this transformative technology, building a future of transparency, security, and endless possibilities.
HijackLoader Evolution: Interactive Process HollowingDonato Onofri
CrowdStrike researchers have identified a HijackLoader (aka IDAT Loader) sample that employs sophisticated evasion techniques to enhance the complexity of the threat. HijackLoader, an increasingly popular tool among adversaries for deploying additional payloads and tooling, continues to evolve as its developers experiment and enhance its capabilities.
In their analysis of a recent HijackLoader sample, CrowdStrike researchers discovered new techniques designed to increase the defense evasion capabilities of the loader. The malware developer used a standard process hollowing technique coupled with an additional trigger that was activated by the parent process writing to a pipe. This new approach, called "Interactive Process Hollowing", has the potential to make defense evasion stealthier.
Gen Z and the marketplaces - let's translate their needsLaura Szabó
The product workshop focused on exploring the requirements of Generation Z in relation to marketplace dynamics. We delved into their specific needs, examined the specifics in their shopping preferences, and analyzed their preferred methods for accessing information and making purchases within a marketplace. Through the study of real-life cases , we tried to gain valuable insights into enhancing the marketplace experience for Generation Z.
The workshop was held on the DMA Conference in Vienna June 2024.
1. blog for the price of a
domain
Jan Collijs
@visibilityspots
2. Jan CollijsJan Collijs
● linux & Open-Source enthousiastlinux & Open-Source enthousiast
● made my hobby my profession about 7 yearsmade my hobby my profession about 7 years
ago @inuitsago @inuits
● want to drink cocktails on the beach whilewant to drink cocktails on the beach while
everything is automatedeverything is automated
3. storystory
● http://scoutsnieuwenrode.behttp://scoutsnieuwenrode.be
•
html → joomla → drupalhtml → joomla → drupal
● http://visibilityspots.comhttp://visibilityspots.com
•
html → wordpresshtml → wordpress
● https://visibilityspots.orghttps://visibilityspots.org
•
pelican on AWSpelican on AWS
● https://lns-events.behttps://lns-events.be
•
pelican on AWS → …pelican on AWS → …