Newsfeeds

My POSSE plan for evolving my site

Dries Buytaert - 16 February 2018 - 1:23am

In an effort to reclaim my blog as my thought space and take back control over my data, I want to share how I plan to evolve my website. Given the incredible feedback on my previous blog posts, I want to continue the conversation and ask for feedback.

First, I need to find a way to combine longer blog posts and status updates on one site:

  1. Update my site navigation menu to include sections for "Blog" and "Notes". The "Notes" section would resemble a Twitter or Facebook livestream that catalogs short status updates, replies, interesting links, photos and more. Instead of posting these on third-party social media sites, I want to post them on my site first (POSSE). The "Blog" section would continue to feature longer, more in-depth blog posts. The front page of my website will combine both blog posts and notes in one stream.
  2. Add support for Webmention, a web standard for tracking comments, likes, reposts and other rich interactions across the web. This way, when users retweet a post on Twitter or cite a blog post, mentions are tracked on my own website.
  3. Automatically syndicate to 3rd party services, such as syndicating photo posts to Facebook and Instagram or syndicating quick Drupal updates to Twitter. To start, I can do this manually, but it would be nice to automate this process over time.
  4. Streamline the ability to post updates from my phone. Sharing photos or updates in real-time only becomes a habit if you can publish something in 30 seconds or less. It's why I use Facebook and Twitter often. I'd like to explore building a simple iOS application to remove any friction from posting updates on the go.
  5. Streamline the ability to share other people's content. I'd like to create a browser extension to share interesting links along with some commentary. I'm a small investor in Buffer, a social media management platform, and I use their tool often. Buffer makes it incredibly easy to share interesting articles on social media, without having to actually open any social media sites. I'd like to be able to share articles on my blog that way.

Second, as I begin to introduce a larger variety of content to my site, I'd like to find a way for readers to filter content:

  1. Expand the site navigation so readers can filter by topic. If you want to read about Drupal, click "Drupal". If you just want to see some of my photos, click "Photos".
  2. Allow people to subscribe by interests. Drupal 8 make it easy to offer an RSS feed by topic. However, it doesn't look nearly as easy to allow email subscribers to receive updates by interest. Mailchimp's RSS-to-email feature, my current mailing list solution, doesn't seem to support this and neither do the obvious alternatives.

Implementing this plan is going to take me some time, especially because it's hard to prioritize this over other things. Some of the steps I've outlined are easy to implement thanks to the fact that I use Drupal. For example, creating new content types for the "Notes" section, adding new RSS feeds and integrating "Blogs" and "Notes" into one stream on my homepage are all easy – I should be able to get those done my next free evening. Other steps, like building an iPhone application, building a browser extension, or figuring out how to filter email subscriptions by topics are going to take more time. Setting up my POSSE system is a nice personal challenge for 2018. I'll keep you posted on my progress – much of that might happen via short status updates, rather than on the main blog. ;)

Categories: Drupal

Gizra.com: Travis - The Need for Speed

Planet Drupal - 15 February 2018 - 10:00pm

Chances are that you already use Travis or another cool CI to execute your tests, and everyone politely waits for the CI checks before even thinking about merging, right? More likely, waiting your turn becomes a pain and you click on the merge: it’s a trivial change and you need it now. If this happens often, then it’s the responsibility of those who worked on those scripts that Travis crunches to make some changes. There are some trivial and not so trivial options to make the team always be willing to wait for the completion.

This blog post is for you if you have a project with Travis integration, and you’d like to maintain and optimize it, or just curious what’s possible. Users of other CI tools, keep reading, many areas may apply in your case too.

Unlike other performance optimization areas, doing before-after benchmarks is not so crucial, as Travis mostly collects the data, you just have to make sure to do the math and present the numbers proudly.

Caching

To start, if your .travis.yml lacks the cache: directive, then you might start in the easiest place: caching dependencies. For a Drupal-based project, it’s a good idea to think about caching all the modules and libraries that must be downloaded to build the project (it uses a buildsystem, doesn’t it?). So even a variant of:

cache: directories: - $HOME/.composer/cache/files

or for Drush

cache: directories: - $HOME/.drush/cache

It’s explained well in the verbose documentation at Travis-ci.com. Before your script is executed, Travis populates the cache directories automatically from a successful previous build. If your project has only a few packages, it won’t help much, and actually it can make things even slower. What’s critical is that we need to cache slow-to-generate, easy-to-download materials. Caching a large ZIP file would not make sense for example, caching many small ones from multiple origin servers would be more beneficial.

From this point, you could just read the standard documentation instead of this blog post, but we also have icing on the cake for you. A Drupal installation can take several minutes, initializing all the modules, executing the logic of the install profile and so on. Travis is kind enough to provide a bird’s-eye view on what eats up build time:

Execution speed measurements built in the log

Mind the bottleneck when making a decision on what to cache and how.

For us, it means cache of the installed, initialized Drupal database and the full document root. Cache invalidation is hard, we can’t change that, but it turned out to be a good compromise between complexity and execution speed gain, check our examples:

Do your homework and cache what’s the most resource-consuming to generate, SQL database, built source code or compiled binary, Travis is here to assist with that.

Software Versions

There are two reasons to pay attention to software versions.

Use Pre-installed Versions

Travis uses containers of different distributions, let’s say you use trusty, the default one these days, then if you choose PHP 7.0.7, it’s pre-installled, in case of 7.1, it’s needed to fetch separately and that takes time for every single build. When you have production constraints, that’s almost certainly more important to match, but in some cases, using the pre-installed version can speed things up.

And moreover, let’s say you prefer MariaDB over MySQL, then do not sudo and start to install it with the package manager, as there is the add-on system to make it available. The same goes for Google Chrome, and so on. Stick to what’s inside the image already if you can. Exploit that possibility of what Travis can fetch via the YML definition!

Use the Latest and (or) Greatest

If you ever read an article about the performance gain from migrating to PHP 7, you sense the importance of selecting the versions carefully. If your build is PHP-execution heavy, fetching PHP 7.2 (it’s another leap, but mind the backward incompatibilities) could totally make sense and it’s as easy as can be after making your code compatible:

language: php php: - '7.2'

Almost certainly, a similar thing could be written about Node.js, or relational databases, etc. If you know what’s the bottleneck in your build and find the best performing versions – newer or older – it will improve your speed. Does that conflict with the previous point about pre-installed versions? Not really, just measure which one helps your build the most!

Make it Parallel

When a Travis job is running, 2 cores and 4 GBytes of RAM is available – that’s something to rely on! Downloading packages should happen in parallel. drush make, gulp and other tools like that might use it out of the box: check your parameters and configfiles. However, on the higher level, let’s say you’d like to execute a unit test and a browser-based test, as well. You can ask Travis to spin up two (or more) containers concurrently. In the first, you can install the unit testing dependencies and execute it; then the second one can take care of only the functional test. We have a fine-grained example of this approach in our Drupal-Elm Starter, where 7 containers are used for various testing and linting. In addition to the great execution speed reduction, the benefit is that the result is also more fine-grained, instead of having a single boolean value, just by checking the build, you have an overview what can be broken.

All in all, it’s a warm fuzzy feeling that Travis is happy to create so many containers for your humble project:

If it's independent, no need to serialize the execution Utilize RAM

The available memory is currently between 4 and 7.5 GBytes , depending on the configuration, and it should be used as much as possible. One example could be to move the database main working directory to a memory-based filesystem. For many simpler projects, that’s absolutely doable and at least for Drupal, a solid speedup. Needless to say, we have an example and on client projects, we saw 15-30% improvement at SimpleTest execution. For traditional RMDBS, you can give it a try. If your DB cannot fit in memory, you can still ask InnoDB to fill memory.

Think about your use case – even moving the whole document root there could be legitimate. Also if you need to compile a source code, doing it there makes sense as well.

Build Your Own Docker Image

If your project is really exotic or a legacy one, it potentially makes sense to maintain your own Docker image and then download and execute it in Travis. We did it in the past and then converted. Maintaining your image means recurring effort, fighting with outdated versions, unavailable dependencies, that’s what to expect. Still, even it could be a type of performance optimization if you have lots of software dependencies that are hard to install on the current Travis container images.

+1 - Debug with Ease

To work on various improvements in the Travis integration for your projects, it’s a must to spot issues quickly. What worked on localhost, might or might not work on Travis – and you should know the root cause quickly.

In the past, we propagated video recording, now I’d recommend something else. You have a web application, for all the backend errors, there’s a tool to access the logs, at Drupal, you can use Drush. But what about the frontend? Headless Chrome is neat, it has built-in debugging capability, the best of which is that you can break out of the box using Ngrok. Without any X11 forwarding (which is not available) or a local hack to try to mimic Travis, you can play with your app running in the Travis environment. All you need to do is to execute a Debug build, execute the installation part (travis_run_before_install, travis_run_install, travis_run_before_script), start Headless Chrome (google-chrome --headless --remote-debugging-port=9222), download Ngrok, start a tunnel (ngrok http 9222), visit the exposed URL from your local Chrome and have fun with inspection, debugger console, and more.

Takeaway

Working on such improvements has benefits of many kinds. The entire development team can enjoy the shorter queues and faster merges, and you can go ahead and apply part of the enhancements to your local environment, especially if you dig deep into database performance optimization and make the things parallel. And even more, clients love to hear that you are going to speed up their sites, as this mindset should be also used at production.

Continue reading…

Categories: Drupal

REST Password Request

New Drupal Modules - 15 February 2018 - 6:26pm

New Rest Plugin to use REST for forgot Password Request.

We could not find a way that core Rest could send a password retrieval link via Rest resource.

This simply ads a resource to allow A New POST Request to
endpoint "/user/lost-password:"

with the key of "mail" (and optional "lang" for localization )

To Set up:

Please install Rest UI, then install the module in the normal way... then in rest ui -> find "Lost password" and enable.

Categories: Drupal

GrapesJS

New Drupal Modules - 15 February 2018 - 5:36pm
Categories: Drupal

Agiledrop.com Blog: AGILEDROP: Time to move forward?

Planet Drupal - 15 February 2018 - 4:10pm
When is the right time to let it go and move forward? Yes, we are talking about migrating to Drupal 8 version. Drupal 8 was released in November 2015, so it has been more than two years now. No matter what kind of website you have, whether you have an online shop, small brochure website or an extensive and complex website, if its build on Drupal 6, it's almost urgent you move forward and upgrade it to Drupal 8. Why? The Drupal community no longer (officially) supports Drupal 6 since three months after Drupal 8 came out. That means that bugs are no longer getting fixed. Drupal 6 is simply long… READ MORE
Categories: Drupal

Osprey Games Announces Wildlands Miniatures Board Game

Tabletop Gaming News - 15 February 2018 - 3:00pm
Osprey Games is working on their first miniatures board game. It’s called Martin Wallace’s Wildlands (but everyone can play, not just him). Players will team up and compete against each-other, each team trying to reclaim the glory of what had been a mighty kingdom, but is now just the wildlands. Defeat enemy characters, gather resources, […]
Categories: Game Theory & Design

Game Nite Magazine Issue 21 Now Available

Tabletop Gaming News - 15 February 2018 - 2:00pm
When you want to fill up your day with gaming, a gaming magazine is hard to beat. Filled with great articles on all sorts of topics, they can keep you interested for hours. In this instance, it’s Game Nite magazine. Issue 21 is now available for your downloading and reading pleasure. It’s free, so there’s […]
Categories: Game Theory & Design

Acro Media: Drupal Commerce 2: How to Add and Modify Product Content

Planet Drupal - 15 February 2018 - 1:13pm

In part one  and two of this Acro Media Tech Talk video series, we covered how you set up a new product attribute and used rendered fields, in Drupal Commerce 2. Parts three and four then to set up a product variation type and a product type, both with custom fields. This completes our new product configuration.

In part five, the last of this series, we'll finally get to try out the new product! We'll add a product to the store as if we are a store administrators (end user) who is creating content. We'll try out all of the fields and properties we've configured, make a product, and view it on the site. Afterwards, we'll cover how an administrator can then go in and edit the product to make content changes.

This entire video series, parts one through five, show you how to set up a new product in Drupal Commerce 2, from start to finish. The video is captured using our Urban Hipster Commerce 2 demo site.

Its important to note that this video was recorded before the official 2.0 release of Drupal Commerce and so you may see a few small differences between this video and the official release now available.

Urban Hipster Commerce 2 Demo site

This video was created using the Urban Hipster Commerce 2 demo site. We've built this site to show the adaptability of the Drupal 8, Commerce 2 platform. Most of what you see is out-of-the-box functionality combined with expert configuration and theming.

More from Acro Media Drupal modules used in this video

Categories: Drupal

The Reckoners Board Game Up On Kickstarter

Tabletop Gaming News - 15 February 2018 - 1:00pm
It’s always cool when a bit of media you love gets turned into a game you can immerse yourself in. You get to join in with the actions and adventures of your favorite characters and do your own part to shape the world. That’s what you get in The Reckoners, a new cooperative board game […]
Categories: Game Theory & Design

Arcknight Running Patreon Campaign

Tabletop Gaming News - 15 February 2018 - 12:00pm
Patreon’s a crowdfunding source that more gaming companies are looking into. For a monthly pledge (basically, you could think of it as a subscription fee), you get access to special material and extras that may or may not be available to the general public down the line. In this instance, it’s Arcknight that’s got a […]
Categories: Game Theory & Design

New discount and price-based filters hit Steam Wishlists

Social/Online Games - Gamasutra - 15 February 2018 - 11:39am

The options let players sort their lists in new ways and give them filter to automatically hide titles based on price, discount, or release type. ...

Categories: Game Theory & Design

Opinion: Why there's no such thing as 'the game industry'

Social/Online Games - Gamasutra - 15 February 2018 - 11:06am

Necrosoft Games founder and Gamasutra contributor Brandon Sheffield makes the case (complete with multiple sources of data) that there is no longer a single 'game industry', if there ever was. ...

Categories: Game Theory & Design

Thursday Terrain Corner

Tabletop Gaming News - 15 February 2018 - 11:00am
Happy Cheap Candy Day! Quick! Before the stores swap out everything for Easter stuff, go grab yourself some red-tinted and heart-shaped boxes of goodies for less than you’d usually spend! And with the money you saved on that candy, you can go get yourself some new terrain for your gaming table. Today in the Terrain […]
Categories: Game Theory & Design

Entity tracker

New Drupal Modules - 15 February 2018 - 10:51am
Categories: Drupal

Chat app-maker Kakao secures $130M investment for its game business

Social/Online Games - Gamasutra - 15 February 2018 - 10:50am

The noted Chinese tech giant Tencent led the funding round, held just ahead of the game division's planned IPO. ...

Categories: Game Theory & Design

Contrib Team for Drupal Diversity & Inclusion

New Drupal Modules - 15 February 2018 - 10:19am

Learn more about the Drupal Diversity & Inclusion their Drupal.org project. We have begun our initial migration from the Github repository. This will take some time and is considered a work-in-progress.

Categories: Drupal

Way of the Fighter Now Available

Tabletop Gaming News - 15 February 2018 - 10:00am
If your Valentine’s day didn’t quite turn out like you’d hoped, I still hope it didn’t end up with you squaring off with an opponent, prepping your various martial arts moves in the attempt to knock the other fighter into unconsciousness… unless, of course, that was just you and your significant other playing some Way […]
Categories: Game Theory & Design

Commerce ML Starter

New Drupal Modules - 15 February 2018 - 9:16am

Drupal Commerce + 1C Starter Kit

Categories: Drupal

New Avanti Releases Available From Battlefront

Tabletop Gaming News - 15 February 2018 - 9:00am
As Battlefront points out in their post, February is already halfway done. We’re just motoring our way through. They’re certainly not sitting back and relaxing. They’ve got minis to release! And that’s just what they’re letting you know about, with new Avanti releases, as well as updates about Team Yankee and a reminder about the […]
Categories: Game Theory & Design

Mediacurrent: Accommodating Drupal In Your Components

Planet Drupal - 15 February 2018 - 8:44am

Last fall at BADCamp it was exciting to see that a component-driven approach to building Drupal 8 themes is becoming the standard. Many people are doing great things to advance this approach, including reducing duplication and simplifying data structures. In the day-long front end summit, and in many sessions and BOFs during BADCamp, great tips were shared for making the most of helper modules, such as the UI Patterns module, as well as techniques that make the most of Pattern Lab, KSS, and other front end systems.

Categories: Drupal

Pages

Subscribe to As If Productions aggregator