WordPress Handson on WordCamp Kansai 2015 - Let's begin the WordPress translation!
This session is to experience the Japanese translation from English on WordPress for beginners.
The aim is to raise the translation activity for WordPress!!
Running Multiple Multilingual Websites at Kyoto University on WordCamp Kansai 2015.
Concretely, the case example is at Center for Southeast Asian Studies, Kyoto University. Various countries researchers have frequently come to the Center, so a multiple multilingual system construction is very important issue!
WordPress Handson on WordCamp Kansai 2015 - Let's begin the WordPress translation!
This session is to experience the Japanese translation from English on WordPress for beginners.
The aim is to raise the translation activity for WordPress!!
Running Multiple Multilingual Websites at Kyoto University on WordCamp Kansai 2015.
Concretely, the case example is at Center for Southeast Asian Studies, Kyoto University. Various countries researchers have frequently come to the Center, so a multiple multilingual system construction is very important issue!
The document discusses plenv and perl-build, tools for managing multiple Perl versions. It describes plenv's architecture where plenv invokes perl-build to install Perl versions. perl-build works by getting binary tarball URLs from various sources, but some of these sources like search.cpan.org will be retired, so the document recommends updating perl-build to version 1.20+ which will fetch URLs from the MetaCPAN API instead. It also mentions that the plenv and perlbrew developers work at LINE.
Promgen is a Prometheus management tool that allows web-based management of server configurations and alerting rules. It addresses the need for an easier way to manage Prometheus server configurations than manually editing YAML files. Promgen stores configuration data in a MySQL database and generates YAML files from the stored configurations. It aims to provide a simple interface for configuring Prometheus exporters, ports, alerts and other settings across multiple servers and projects.
This document discusses writing a web application in Perl6. It summarizes implementing key functions like forking and waiting for child processes using NativeCall to call libc methods. It also proposes writing a C DLL for a Raw::Socket module to provide a BSD socket wrapper and using that to build an httpd with features like request parsing and pre-forking.
This document discusses using Perl 6 with the Java Virtual Machine (JVM). It provides instructions for installing Perl 6 with JVM support and demonstrates various features like JSON processing, HTTP client/server, database access using SQLite and MySQL, calling Java methods, and building a basic GUI. Performance tests show startup is slow but HTTP server throughput is faster with JVM backend compared to MoarVM backend. Overall, the author finds Perl 6 on JVM to be practical for Java developers needing to access Java libraries and calls it potentially useful.
Server::Starter is a daemon that allows hot-deployment of server programs. It was originally designed for Perl web applications but can now also be used to run Java web apps by having the Java Virtual Machine inherit the listening socket from the parent Server::Starter process. This new capability allows easy upgrading of the JVM version and shutdown of old processes when new ones are launched, though it does not currently work on Mac OS X.
This document discusses Perl testing libraries and frameworks. It provides an overview of the history of Perl testing including Test::More and Test::Class. It also introduces some newer testing libraries like Test::Pretty, Test::Ika, and Test::Kantan that aim to improve on Test::Builder and provide additional features like BDD-style testing and improved output. The document encourages trying out these new testing libraries and frameworks.
This document discusses using the Devel::NYTProf profiler module to profile Perl code running under the Apache web server. It explains how to configure Apache and Devel::NYTProf to collect profiling data, run Apache to generate the data, and then process the results to produce HTML reports analyzing the profiling run. The document encourages measuring performance instead of guessing and asks if there are any questions.
This document discusses using MySQL locks at the application level with MoFedge to prevent bad flows like double submissions. It recommends using the Mysql::NameLocker module to lock a session ID during validation and unlock it after dispatch by calling GET_LOCK() and RELEASE_LOCK() on the database handle. Examples are provided of how to initialize and unset the locker in the valid_add and post_dispatch_add subroutines. More information is available in the CVS repository and SourceForge link provided.
The document outlines the flow of a web application from start to finish in 6 steps: BEFORE_DISPATCH, BEFORE_INIT, AFTER_INIT, initialize objects, AFTER_DISPATCH, dispatch_ valid_ post_dispatch_.