brunocarvalhodearaujo

Installing NFS inside LXC Container on Proxmox 5.1

Host Setup:

Create LXC Container as usual, but do not start it yet.

# Install NFS-Kernel on Host
apt install nfs-kernel-server

brunocarvalhodearaujo

#!/bin/bash

git show :group_vars/all.yml | grep ^'$ANSIBLE_VAULT'
export encrypted=$?
if [ $encrypted -ne 0 ]; then
  echo Ansible Vault not encrypted, refusing to commit
  exit 1
fi

brunocarvalhodearaujo

const { makeRemoteExecutableSchema, introspectSchema, mergeSchemas } = require('graphql-tools')
const { createHttpLink } = require('apollo-link-http')
const { setContext } = require('apollo-link-context')
const { ApolloServer } = require('apollo-server-express')
const fetch = require('node-fetch')
const log4js = require('log4js')
const logger = log4js.getLogger('server.js')
logger.level = process.env.LOG_LEVEL || 'debug'
const express = require('express')

brunocarvalhodearaujo

const categories = useMemo(() => {
  return products.reduce((categories, { category }) => {
      return !category || categories.find(({ id }) => category && category.id === id)
        ? categories
        : [
            ...categories,
            {
              id: category.id,
              value: category.id,
              label: category.title,

brunocarvalhodearaujo

require('dd-trace').init({
  hostname: process.env.DD_AGENT_HOST,
  port: 8126,
  env: 'development',
  logInjection: true,
  analytics: true,
});

const { createLogger, format, transports } = require('winston');
const addAppNameFormat = format(info => {

brunocarvalhodearaujo

-- show running queries (pre 9.2)
SELECT procpid, age(clock_timestamp(), query_start), usename, current_query 
FROM pg_stat_activity 
WHERE current_query != '<IDLE>' AND current_query NOT ILIKE '%pg_stat_activity%' 
ORDER BY query_start desc;

-- show running queries (9.2)
SELECT pid, age(clock_timestamp(), query_start), usename, query 
FROM pg_stat_activity 
WHERE query != '<IDLE>' AND query NOT ILIKE '%pg_stat_activity%' 

brunocarvalhodearaujo

// No Security

{
  "rules": {
    ".read": true,
    ".write": true
  }
}

brunocarvalhodearaujo

{
  "chat": {
     // the list of chats may not be listed (no .read permissions here)
     
     // a chat conversation
     "$key": {
         
         // if the chat hasn't been created yet, we allow read so there is a way 
         // to check this and create it; if it already exists, then authenticated 
         // user (specified by auth.id) must be in $key/users

brunocarvalhodearaujo

#!groovy

pipeline {
    agent any

    //These params will be displayed for user input when running a build, They are also accepted by the API
    parameters {
        string(name: 'BUILD_HOSTNAME', description: 'The name of the server to build (from Mdb)')
        string(name: 'ILO_IP', description: 'The IP address for the server ilo')
        booleanParam(name: 'skipOneView', description: 'Skip the OneView stage?', defaultValue: false)

brunocarvalhodearaujo

I had a bit of trouble figuring out how to use bitnami's sealed secrets with helm

Here's a definition of done to help you see what I was trying to achieve.

Definition of done

• Single secret available for a release in a namespace, listing all secret variables
• Regular helm workflow, with no extra kubeseal commands for developers
• Encrypted secrets clearly visible in git
• Sealedsecret managed by helm