| // SPDX-License-Identifier: MIT | |
| // This doesn't work properly in all cases. You would be better off using https://gist.github.com/Alyinghood/21bdb81d6f83114604082bd019482ae3 instead | |
| // See https://forums.nrvnqsr.com/showthread.php/9708-Mahoutsukai-no-Yoru-HD-PC-file-format-deciphering | |
| #include <string.h> | |
| #include <stdio.h> | |
| #include <stdbool.h> | |
| #include <stdlib.h> | |
| #include <stdint.h> |
| # EditorConfig helps keep your project formatting consistent. | |
| # See https://EditorConfig.org | |
| # | |
| # This is a modified version of the WordPress coding standards. | |
| # | |
| # Author: Sal Ferrarello (@salcode) | |
| # https://salferrarello.com/wordpress-editorconfig/ | |
| # | |
| # You can download this file directly | |
| # to your project from the command-line with |
Let Tomcat is download and installed under /opt/tomcat.
Also, let tomcat be a non-provileged user under which the server will be running.
We assume that we keep server's binaries under /opt/tomcat and we will create a server instance named foo under /var/tomcat/ (carrying its own conf, logs, webapps, work, lib directories).
See also https://dzone.com/articles/running-multiple-tomcat.
Create a template service unit file at /etc/systemd/system/[email protected]:
If you are like me you find yourself cloning a repo, making some proposed changes and then deciding to later contributing back using the GitHub Flow convention. Below is a set of instructions I've developed for myself on how to deal with this scenario and an explanation of why it matters based on jagregory's gist.
To follow GitHub flow you should really have created a fork initially as a public representation of the forked repository and the clone that instead. My understanding is that the typical setup would have your local repository pointing to your fork as origin and the original forked repository as upstream so that you can use these keywords in other git commands.
Clone some repo (you've probably already done this step)
git clone [email protected]
| # Convert p12 to pem | |
| openssl pkcs12 -in certificate.p12 -out certificate.pem -clcerts -nodes | |
| # Convert pem to p12 | |
| openssl pkcs12 -export -in certificate.pem -out certificate.p12 -passout pass:password |
| <?php | |
| /* | |
| Plugin Name: A faster load_textdomain | |
| Version: 0.0.1 | |
| Description: While we're wating for https://core.trac.wordpress.org/ticket/32052. | |
| Author: Per Soderlind | |
| Author URI: https://soderlind.no | |
| Plugin URI: https://gist.github.com/soderlind/610a9b24dbf95a678c3e | |
| License: GPL |
| - name: Make sure the sites-available, sites-enabled and conf.d directories exist | |
| file: | |
| path: "{{nginx_dir}}/{{item}}" | |
| owner: root | |
| group: root | |
| mode: 0755 | |
| recurse: yes | |
| state: directory | |
| with_items: ["sites-available", "sites-enabled", "conf.d"] |
The philosophy behind Documentation-Driven Development is a simple: from the perspective of a user, if a feature is not documented, then it doesn't exist, and if a feature is documented incorrectly, then it's broken.
