Mithradates528

extends Node2D

# Data for the pie chart
export var data := [
	{"Name":"Trade", "value": 8.0, "color": Color.burlywood},    
	{"Name":"Pupets", "value": 16.0, "color": Color.deeppink},    
	{"Name":"Production", "value": 26.0, "color": Color.greenyellow},     
	{"Name":"Taxes", "value": 35.0, "color": Color.aqua},    
	{"Name":"Occupation", "value": 50.0, "color": Color.cornflower}     
]

superseb

Restore Rancher 2 cluster/node agents on clusters

This is an unsupported scenario, see rancher/rancher#14731 when there is an official solution.

When cattle-cluster-agent and/or cattle-node-agent are accidentally deleted, or when server-url/cacerts are changed.

Generate definitions

• Generate API token in the UI (user -> API & Keys) and save the Bearer token
• Find the clusterid in the Rancher UI (format is c-xxxxx), its in the address bar when the cluster is selected

janeczku

Steps to change the URL of Rancher installation and switch from a self-signed certificate to a certificate signed by recognized CA.

1. Change the Rancher server-url setting to the new URL:
   • Navigate to https://<old_rancher_hostname>/g/settings/advanced
   • Edit server-url to https://<new_rancher_hostname>
2. Clear the private CA certificate for the old certificate
   • Navigate to https://<old_rancher_hostname>/g/settings/advanced
   • Next to cacerts click context menu -> View in API
   • Click Edit
   • Clear the content of the value field

carloscarnero

---
kind: ClusterRole
apiVersion: rbac.authorization.k8s.io/v1beta1
metadata:
  name: traefik-ingress-controller
rules:
- apiGroups:
  - ""
  resources:
  - services

eddy8

<?php
/**
 * 异常处理类
 */

use \Illuminate\Contracts\Debug\ExceptionHandler;

class MyQueueException implements ExceptionHandler
{
    /**

max-mapper

Ham5ter

Set up HAProxy with Pacemaker/Corosync on Ubuntu 16.04

This Document roughly describes a HAProxy Cluster Setup on Ubuntu 16.04 based on an example Configuration with 3 Nodes

This Document is still work in Progress the Following Stuff still needs to be done:

• Explain the crm configure steps
• explain Miscellaneous CRM Commands for Cluster Management
• Add all the external ressources used.
• Add a simple HAProxy Configuration for testing purpouse

Ham5ter

apt update && apt upgrade -y && apt remove unattended-upgrades -y && apt autoremove -y
apt-get clean
echo "blacklist floppy" | sudo tee /etc/modprobe.d/blacklist-floppy.conf
sudo rmmod floppy
sudo update-initramfs -u

h-collector

<?php

namespace Jobs;

use Illuminate\Queue\InteractsWithQueue;
use Illuminate\Redis\Database as Redis;

class Foo extends Job
{
    use InteractsWithQueue;

julianlam

Provisioning and usage of unprivileged LXC containers via indirect login or script

As I've discovered, managing LXC containers is fairly straightforward, but when building out a system for provisioning out user maintained instances of NodeBB, it was imperative that unprivileged LXC containers were used, so that in the event of shell breakout from NodeBB followed by privilege escalation of the saas user, the root user in the LXC container would only be an unprivileged user on the host machine.

During the course of development, I ran into numerous blockers when it came to managing LXC containers in unexpected circumstances. Namely:

• Using LXC in a subshell is not directly supported. This usually happens under one of the following two circumstances:
  • After switching users via su or executing lxc-* commands as another user via sudo
  • Executing lxc-* commands via a program, application, or script. In my case, a Node.js application.