Elsewhere

Dimitri John Ledkov: Four gunmen outside

Planet Debian - sam, 30/01/2016 - 02:39

There are four gunmen outside of my hotel. They are armed with automatic rifles and pistols. I am scared for my life having sneaked past them inside. Everyone else is acting as if everything is normal. Nobody is scared or running for cover. Nobody called the police. I've asked the reception to talk to the gunmen and ask them to leave. They looked at me as if I am mad. Maybe I am. Is this what shizophrenia feels like?! Can you see them on the picture?! Please help. There are four gunmen outside of my hotel. I am not in central Beirut, I am in central Brussels.

Catégories: Elsewhere

Promet Source: How to Integrate Association Management Systems with Drupal

Planet Drupal - ven, 29/01/2016 - 22:17

Association websites should be built to handle everything from membership drives to billing activities. Having a website by itself isn't enough; associations also need robust member management databases running behind their websites. There are many vendors who specialize in products that meet this need. These products are commonly referred to as an Association Management System (AMS) and it's rare to find a large organization that doesn't use one.

Catégories: Elsewhere

Drupal core announcements: Help finalizing Migrate at the Global Sprint Weekend

Planet Drupal - ven, 29/01/2016 - 22:12

The Migrate team would like to finish up the Migrate subsystem for next month's release of Drupal 8.1.0. They've collected a number of issues for the upcoming global sprint weekend:

Global Sprint Weekend Migrate Issues

There are issues available for all levels of expertise. If you need help, the Migrate maintainers are in #drupal-migrate on irc.freenode.net as usual and are happy to answer questions.

Catégories: Elsewhere

Jan Wagner: Oxidized - silly attempt at (Really Awesome New Cisco confIg Differ)

Planet Debian - ven, 29/01/2016 - 21:46

Since ages I wanted have replaced this freaking backup solution of our Network Equipment based on some hacky shell scripts and expect uploading the configs on a TFTP server.

Years ago I stumbled upon RANCID (Really Awesome New Cisco confIg Differ) but had no time to implement it. Now I returned to my idea to get rid of all our old crap.
I don't know where, I think it was at DENOG2, I saw RANCID coupled with a VCS, where the NOC was notified about configuration (and inventory) changes by mailing the configuration diff and the history was indeed in the VCS.
The good old RANCID seems not to support to write into a VCS out of the box. But for the rescue there is rancid-git, a fork that promises git extensions and support for colorized emails. So far so good.

While I was searching for a VCS capable RANCID, somewhere under a stone I found Oxidized, a 'silly attempt at rancid'. Looking at it, it seems more sophisticated, so I thought this might be the right attempt. Unfortunately there is no Debian package available, but I found an ITP created by Jonas.

Anyway, for just looking into it, I thought the Docker path for a testbed might be a good idea, as no Debian package ist available (yet).

For oxidized configuration is only a configfile needed and as nodes source a rancid compatible router.db file can be used (beside SQLite and http backend). A migration into a production environment seems pretty easy. So I gave it a go.

I assume Docker is installed already. There seems to be a Docker image on Docker Hub, that looks official, but it seems not maintained (actually). An issue is open for automated building the image.

Creating Oxidized container image

The official documentation describes the procedure. I used a slightly different approach.

docking-station:~# mkdir -p /srv/docker/oxidized/ docking-station:~# git clone https://github.com/ytti/oxidized \ /srv/docker/oxidized/oxidized.git docking-station:~# docker build -q -t oxidized/oxidized:latest \ /srv/docker/oxidized/oxidized.git

I thought it might be a good idea to also tag the image with the actual version of the gem.

docking-station:~# docker tag oxidized/oxidized:latest \ oxidized/oxidized:0.11.0 docking-station:~# docker images | grep oxidized oxidized/oxidized latest 35a325792078 15 seconds ago 496.1 MB oxidized/oxidized 0.11.0 35a325792078 15 seconds ago 496.1 MB

Create initial default configuration like described in the documentation.

docking-station:~# mkir -p /srv/docker/oxidized/.config/ docking-station:~# docker run -e CONFIG_RELOAD_INTERVAL=600 \ -v /srv/docker/oxidized/.config/:/root/.config/oxidized \ -p 8888:8888/tcp -t oxidized/oxidized:latest oxidized Adjusting configuration

After this I adjusted the default configuration for writing a log, the nodes config into a bare git, having nodes secrets in router.db and some hooks for debugging.

Creating node configuration docking-station:~# echo "7204vxr.lab.cyconet.org:cisco:admin:password:enable" >> \ /srv/docker/oxidized/.config/router.db docking-station:~# echo "ccr1036.lab.cyconet.org:routeros:admin:password" >> \ /srv/docker/oxidized/.config/router.db Starting the oxidized beast docking-station:~# docker run -e CONFIG_RELOAD_INTERVAL=600 \ -v /srv/docker/oxidized/.config/:/root/.config/oxidized \ -p 8888:8888/tcp -t oxidized/oxidized:latest oxidized Puma 2.16.0 starting... * Min threads: 0, max threads: 16 * Environment: development * Listening on tcp://127.0.0.1:8888

If you want to have the container get started with the docker daemon automatically, you can start the container with --restart always and docker will take care of it. If I wanted to make it running permanent, I would use a systemd unitfile.

Reload configuration immediately

If you don't want to wait to automatically reload of the configuration, you can trigger it.

docking-station:~# curl -s http://localhost:8888/reload?format=json \ -O /dev/null docking-station:~# tail -2 /srv/docker/oxidized/.config/log/oxidized.log I, [2016-01-29T16:50:46.971904 #1] INFO -- : Oxidized starting, running as pid 1 I, [2016-01-29T16:50:47.073307 #1] INFO -- : Loaded 2 nodes Writing nodes configuration docking-station:/srv/docker/oxidized/.config/oxidized.git# git shortlog Oxidizied (2): update 7204vxr.lab.cyconet.org update ccr1036.lab.cyconet.org

Writing the nodes configurations into a local bare git repository is neat but far from perfect. It would be cool to have all the stuff in a central VCS. So I'm pushing it every 5 minutes into one with a cron job.

docking-station:~# cat /etc/cron.d/doxidized # m h dom mon dow user command */5 * * * * root $(/srv/docker/oxidized/bin/oxidized_cron_git_push.sh) docking-station:~# cat /srv/docker/oxidized/bin/oxidized_cron_git_push.sh #!/bin/bash DOCKER_OXIDIZED_BASE="/srv/docker/oxidized/" OXIDIZED_GIT_DIR=".config/oxidized.git" cd ${DOCKER_OXIDIZED_BASE}/${OXIDIZED_GIT_DIR} git push origin master --quiet

Now having all the nodes configurations in a source code hosting system, we can browse the configurations, changes, history and even establish notifications for changes. Mission accomplished!

Now I can test the coverage of our equipment. The last thing that would make me super happy, a oxidized Debian package!

Catégories: Elsewhere

Acquia Developer Center Blog: Drupal Global Sprint 2016, New England-Style

Planet Drupal - ven, 29/01/2016 - 21:43
DC Denison

Tom Kraft and Renato Francia were conferring in the kitchen, laptops open, “trying to make the Feeds module work better out of the box.”

In a nearby conference room, Dan Feidt was juggling a bunch of open windows on his laptop screen, tackling “a little puzzle around virtualization and Vagrant.”

Kay VanValkenburgh, who was in charge of beginners and onboarding, was roaming, talking to attendees, “removing barriers.”

Tags: acquia drupal planet
Catégories: Elsewhere

DrupalCon News: Staying for the Community: Stories From Our Organizers

Planet Drupal - ven, 29/01/2016 - 20:13

Some of our very own DrupalCon Asia organizers are members of the Drupal Association. We spoke to them about why membership is so important to them, and their answers were so great we had to share. As DrupalCon Asia gets closer, we invite you to read why they support the community and the Drupal project with us:

Catégories: Elsewhere

ImageX Media: Can These "Under the Radar" Keyword Tools Help You Optimize Your Content Marketing Strategy? We’ll Help You Find Out.

Planet Drupal - ven, 29/01/2016 - 20:02

 

Thanks to new innovations in the search engine optimization space, there’s more tools than ever before. This article explores 5 powerful keyword research tools that might not even be on your competitors’ radar yet.
 

Catégories: Elsewhere

InternetDevels: Reasons to Upgrade Your Site From Drupal 6 to Drupal 7

Planet Drupal - ven, 29/01/2016 - 16:05

We had a discussion in one of our previous blogs that Drupal 6 is “dead”,
however if you’re a site owner and still not sure whether you need Drupal 7,
we’ve prepared this article specifically for you.

Read more
Catégories: Elsewhere

Acquia Developer Center Blog: Maintainer's Toolbox: git blame

Planet Drupal - ven, 29/01/2016 - 15:04
Jess (xjm)

This blog post is part of a series on everyday tools and strategies for code review, drawn from Drupal contribution experiences. xjm is a Drupal 8 core maintainer and release manager.

If you have spent much time developing software with others, you've probably asked yourself some of these questions at one time or another:

Tags: acquia drupal planet
Catégories: Elsewhere

Steinar H. Gunderson: En route to FOSDEM

Planet Debian - ven, 29/01/2016 - 15:04

FOSDEM is almost here! And in an hour or so, I'm leaving for the airport.

My talk tomorrow is about Nageru, my live video mixer. HDMI/SDI signals in, stream that doesn't look like crap out. Or, citing the abstract for the talk:

Nageru is an M/E (mixer/effects) video mixer capable of high-quality output on modest hardware. We'll go through the fundamental goals of the project, what we can learn from the outside world, performance challenges in mixing 720p60 video on an ultraportable laptop, and how all of this translates into a design and implementation that differs significantly from existing choices in the free software world.

Saturday 17:00, Open Media devroom (H.2214). Feel free to come and ask difficult questions. :-) (I've heard there's supposed to be a live stream, but there's zero public information on details yet. And while you can still ask difficult questions while watching the stream, it's unlikely that I'll hear them.)

Catégories: Elsewhere

Iain R. Learmonth: FOSDEM 2016

Planet Debian - ven, 29/01/2016 - 14:27

FOSDEM 2016 starts tomorrow and I will be attending. I've not got off to a brilliant start with my flight being cancelled, though SAS have now rebooked me onto a later flight and I'm going to arrive in time for the start tomorrow morning. Unfortunately, I am going to miss the Friday beer event.

On the Saturday, the real-time communications devroom will be happening, and I am one of the devroom admins that helped to organise this. There will be a full day of talks and demonstrations about real-time communications using open standards and free software. I'm rather excited about this.

On the Sunday, I'll be giving a talk and quick demonstration in the distributions devroom about real-time communications in free software communities and why it is useful for your community.

If you're considering setting up some real-time communications infrastructure for your community but you're not going to be along to FOSDEM, there is a great guide for getting started at rtcquickstart.org.

Catégories: Elsewhere

DrupalCon News: DrupalCon New Orleans is on the Horizon

Planet Drupal - ven, 29/01/2016 - 07:58

This year, DrupalCon North America heads to New Orleans, and I can't tell you how excited I am. Together with all the other members of our local Louisiana Drupal user group, we are truly looking forward to hosting the Drupal community as much as you all are excited to come experience everything New Orleans has to offer. For those visiting for the first time, I hope your expectations are exceeded. For those of you who are familiar with New Orleans, we welcome you back, and I hope you will be comforted with old haunts.

Catégories: Elsewhere

Drupal core announcements: Proposal: New release schedule for Drupal 7 core

Planet Drupal - ven, 29/01/2016 - 05:43

There is a discussion underway about adopting a similar release schedule for Drupal 7 that Drupal 8 is using (i.e., a six-month feature release schedule, with pseudo-semantic versioning).

This is not a major change to current policy, but it would mean that new features or other potentially disruptive patches to Drupal 7 core would be limited to two windows per year, with the corresponding releases given a round number (for example, Drupal 7.50, Drupal 7.60, etc.) to indicate their importance.

I'd like to bring the discussion to a close soon so that if we do adopt the new schedule, the first such release can be slated for April 20 (the same day as the Drupal 8.1.0 release).

If you have any feedback on this proposal, please try to comment within the next week here: https://www.drupal.org/node/2598382

Catégories: Elsewhere

PreviousNext: So many ways to hide

Planet Drupal - jeu, 28/01/2016 - 23:35

Generally speaking hiding content goes alongside a bit of javascript that unhides the content under certain circumstances (think hamburger menu).

Sometimes the content improves accessibility but is considered visual noise (says the designer).

So as the developer you have a lot of ways to... pat the cat(?) But not all cats react the same to being patted :D

Catégories: Elsewhere

Sean Whitton: Becoming a Debian contributor

Planet Debian - jeu, 28/01/2016 - 20:00

Over the past two months or so I have become a contributor to the Debian Project. This is something that I’ve wanted to do for a while. Firstly, just because I’ve got so much out of Debian over the last five or six years—both as a day-to-day operating system and a place to learn about computing—and I wanted to contribute something back. And secondly, in following the work of Joey Hess for the past three or four years I’ve come to share various technical and social values with Debian. Of course, I’ve long valued the project of making it possible for people to run their computers entirely on Free Software, but more recently I’ve come to appreciate how Debian’s mature technical and social infrastructure makes it possible for a large number of people to work together to produce and maintain high quality packages. The end result is that the work of making a powerful software package work well with other packages on a Debian system is carried out by one person or a small team, and then as many users who want to make use of that software need only apt-get it. It’s hard to get the systems and processes to make this possible right, especially without a team being paid full-time to set it all up. Debian has managed it on the backs of volunteers. That’s something I want to be a part of.

So far, most of my efforts have been confined to packaging addons for the Emacs text editor and the Firefox web browser. Debian has common frameworks for packaging these and lots of scripts that make it pretty easy to produce new packages (I did one yesterday in about 30 minutes). It’s valuable to package these addons because there are a great many advantages for a user in obtaining them from their local Debian mirror rather than downloading them from the de facto Emacs addons repository or the Mozilla addons site. Users know that trusted Debian project volunteers have reviewed the software—I cannot yet upload my packages to the Debian archive by myself—and the whole Debian infrastructure for reporting and classifying bugs can be brought to bear. The quality assurance standards built into these processes are higher than your average addon author’s, not that I mean to suggest anything about authors of the particular addons I’ve packaged so far. And automating the installation of such addons is easy as there are all sorts of tools to automate installations of Debian systems and package sets.

I hope that I can expand my work beyond packaging Emacs and Firefox addons in the future. It’s been great, though, to build my general knowledge of the Debian toolchain and the project’s social organisation while working on something that is both relatively simple and valuable to package. Now I said at the beginning of this post that it was following the work of Joey Hess that brought me to Debian development. One thing that worries me about becoming involved in more contentious parts of the Debian project is the dysfunction that he saw in the Debian decision-making process, dysfunction which eventually led to his resignation from the project in 2014. I hope that I can avoid getting quagmired and demotivated.

Catégories: Elsewhere

Pronovix: PDF is dead; long live PDF! New standards with new applications - PDF in Drupal part 2

Planet Drupal - jeu, 28/01/2016 - 15:10

It’s strange but true: seven years after the PDF reference was published as an ISO standard (ISO-32000-1), there are still developers who think that the Portable Document Format is a closed document format owned by Adobe. PDF is often perceived as a strange, impenetrable document format. It’s high time we bury that idea and take a look at what’s going on in the world of PDF today...

Catégories: Elsewhere

Darren Mothersele: Drupal Predictions for 2016

Planet Drupal - jeu, 28/01/2016 - 15:00

This will be a momentus year for Drupal.

David H, Drupal.org webmaster, was soliciting responses to this thread on Twitter. I kept my predictions brief, but thought I would post here to elaborate.

Some people may be predicting a year of security vulnerabilities. I believe we have a year of innovation ahead of us.

Drupal's ecosystem of contributed modules is playing catch-up since the release of version 8. It has been years since CCK and Views were just experiments in the contrib module space. They are now established as foundation of Drupal core. Contrib (the wider community of Drupal developers) can now get back to innovating.

"Get back to innovating" isn't much of a prediction. I thought about it some more and came up with three things I think are likely to happen in 2016...

CMS-as-a-Service

The era of the monolythic, does-it-all, CMS is coming to an end. The Drupal community talk a lot about progressive decoupling [1] [2]. But, the idea of a fully decoupled backend is becoming established in other areas. Services like Contentful already provide a fully decoupled, headless CMS.

Systems become decoupled, we move to a microservice architecture, and evaluate server-less options. It is conceivable that a Content API could become part of the infrastructure. Amazon are the leading Infrastructure-as-a-Service provider. A Content API (or CMS-as-a-Service) would fit in their suite of cloud computing services.

I did an experiment recently where I put Amazon's API Gateway in front of an EC2 instance running Drupal. This gives a more robust API on top of Drupal 8's Rest support. Monitoring, traffic management, and flexible security controls are standard. This approach offers several advantages, including: Swagger support; CloudFront caching for performance; and input/output translation with data models defined with JSON schema.

Acquia IPO

Going public was always on the cards for Acquia, but they said they are in no rush to IPO. This could be the year. Adoption of D8 will being changes to the user base and continued adoption at the enterprise level.

This will be accompanied by more consolidation in the Drupal world. One of the biggest risks I see is with Drupal companies taking on bigger projects. A single client becomes a large contributer to their revenue, in some cases I've heard as much as 70%. This is a risky situation to be in, if you rely on one client for a majority of your business. The solution is for Drupal companies to come together to form larger entities.

This is just a continuation of an existing trend. Wunderkraut, was the most high-profile merger in the community. Followed by many more, involving companies such as FFW, MediaCurrent, Phase2, and i-Kos.

Composer Support and Decoupled Components

Composer support in Drupal needs some work. There are some big wins to be had by embracing the Composer (and Packagist) workflow.

Commerce Guys are leading the way with Drupal Commerce. They have been factoring out components into separate libraries. Other PHP projects beyond Drupal are making use of them, and contributing to their development. Expect more contrib projects to factor out separate PHP packages of re-usable code. Then Drupal modules become just a thin layer of glue.

There has been a trend for PHP Frameworks to decouple their core components. The Symfony Components split from the full stack framework has meant much wider adoption. They are used in many PHP projects, including Drupal.

PHP-FIG exists to promote interoperability between frameworks. This year will see further initiatives to clean up Drupal's code. Such as, removal of anti-patterns like service locator. The eventual aim will be to decoupling components from Drupal core.

Can you imagine using Views on a non-drupal project?

Catégories: Elsewhere

Matt Glaman: Profiling Drupal Commerce with Blackfire

Planet Drupal - jeu, 28/01/2016 - 14:46

The process of debugging can be a difficult one, and the process of troubleshooting performance even more so. Luckily there are some great tools out there to help with improving the performance of web applications. Previously I wrote about to visual stacktraces and identify bottlenecks. Flamegraphs are very helpful, but still require you to setup XHProf, download the tools for making the flamegraph SVG, and appropriately change your code to save the XHProf data. Luckily there is one of my favorite tools, , that provides continuous PHP performance testing.

One second can define a conversion or not, and this is highly critical when it comes to eCommerce. Bottlenecks can happen in your catalog, viewing products, or even the Drupal Commerce order's life cycle. A great example can be found on this Drupal commerce issue: https://www.drupal.org/node/2653904. It's a patch to improve the deletion of line item references from orders to cut down on number of saves for orders. There's profiling done with both XHProf and Blackfire.

What is Blackfire?

What about Blackfire makes it my favorite? Blackfire provides on-demand profiling, unlike XHProf, which is always collecting data. Blackfire has a PHP extension called Probe that collects raw performance data when requested. Then the Agent sends that data to Blackfire's website for processing and viewing. Companion is a browser extension (Chrome only currently) that will trigger the Probe to collect performance data on a page.

What you get

It speaks for itself. Here is a Blackfire profiling result from a catalog page in the Commerce Kickstart 2 demo store (Drupal without caches enabled.)

As you can see, we spend a lot of time in Views. Enabling Views cache for our catalog (and anonymous page cache) would greatly speed up our page's load time. Here are results with page caching enabled, and search based Views caching. From 1.88s to 55ms!

How to get started

While there is some Blackfire's components, I'll provide a quick start guide. Well, it's a quick start if you use Docker! Blackfire provides an image for their probe and agent. All you need to do is link it to your php-fpm (or whatever container serves your PHP.) 

 If you use Docker Compose, you would need to add the following configuration, and add a new link to this container from your PHP container. You will just need to get your API credentials from your Blackfire account. Restart your app and you're good to go!

blackfire: image: blackfire/blackfire ports: ['8707'] environment: BLACKFIRE_SERVER_ID: xx-xx-xx-xx-xxxx BLACKFIRE_SERVER_TOKEN: dsfsd! BLACKFIRE_LOG_LEVEL: 4

See the full documentation for Docker integration: https://blackfire.io/docs/integrations/docker

Catégories: Elsewhere

Holger Levsen: 20160128-reproducible-ecosystem-at-fosdem

Planet Debian - jeu, 28/01/2016 - 14:29
Reproducible builds ecosystem at FOSDEM

Last years FOSDEM featured one talk about Reproducible Builds, while this year there will be four at least:

On Saturday, there will Reproducible and Customizable Deployments with GNU Guix by Ludovic Courtès which which I definitly will be attending!

And on Sunday there will three talks and I plan to attend them all: a rather general one about the Reproducible ecosystem by myself, followed by ElectroBSD - Getting a reproducible BSD out of the door by Fabian Keil and finally Reproducible builds in FreeBSD packages by Baptiste Daroussin.

The FOSDEM organizers also reached out to me for an interview with me about all this reproducible stuff. I hope you'll like my answers as I enjoyed the questions

But there are many more interesting talks (hundreds they say) and so I'd appreciate if you could share your pointers and explainations, whether here on planet, or on IRC or IRL!

Catégories: Elsewhere

Pages

Subscribe to jfhovinne agrégateur - Elsewhere