With Audio and Screen Sharing Enabled
Add the i386
architecture to the list of dpkg
architectures :
sudo dpkg --add-architecture i386
/* | |
This is a version (aka dlmalloc) of malloc/free/realloc written by | |
Doug Lea and released to the public domain, as explained at | |
http://creativecommons.org/licenses/publicdomain. Send questions, | |
comments, complaints, performance data, etc to dl@cs.oswego.edu | |
* Version 2.8.4 Wed May 27 09:56:23 2009 Doug Lea (dl at gee) | |
Note: There may be an updated version of this malloc obtainable at | |
ftp://gee.cs.oswego.edu/pub/misc/malloc.c |
#!/bin/bash | |
# How to use | |
# 1. Replace the "YOURIP" to yourIP | |
#sed -i -e 's/YOURIP/192.168.x.x/g' setup-taiga-centos.sh | |
# 2. Run at the root | |
#source setup-taiga-centos.sh |
## RetroArch keybind config template | |
## Can be copypasted into an existing config, appended with --apppendconfig, used as a core or game override, or used with the include directive in an existing config | |
# Keyboard input. Will recognize letters (a to z) and the following special keys (where kp_ | |
# is for keypad keys): | |
# | |
# left, right, up, down, enter, kp_enter, tab, insert, del, end, home, | |
# rshift, shift, ctrl, alt, space, escape, add, subtract, kp_plus, kp_minus, | |
# f1, f2, f3, f4, f5, f6, f7, f8, f9, f10, f11, f12, | |
# num0, num1, num2, num3, num4, num5, num6, num7, num8, num9, pageup, pagedown, |
<?php | |
function processMessage($message) { | |
$groupchat = '-XXXX'; // Group chat id | |
// process incoming message | |
$message_id = $message["message_id"]; | |
$chat_id = $message["chat"]["id"]; | |
$response = array("chat_id" => $chat_id); | |
$plextoken = "YYYY"; // Plex token | |
$plexbaseurl = "https://ASFASFASF.plex.direct:32400"; // PLEX DIRECT URL |
Coding practices are a source of a lot of arguments among programmers. Coding standards, to some degree, help us to put certain questions to bed and resolve stylistic debates. No coding standard makes everyone happy. (And even their existence is sure to make some unhappy.) What follows are the standards we put together on the Core team, which have become the general coding standard for all programming teams on new code development. We’ve tried to balance the need for creating a common, recognizable and readable code base with not unduly burdening the programmer with minor code formatting concerns.
apiVersion: v1 | |
kind: ConfigMap | |
metadata: | |
name: nginx-conf | |
data: | |
nginx.conf: | | |
user nginx; | |
worker_processes 3; | |
error_log /var/log/nginx/error.log; | |
events { |