codeopensrc

Fix for kubernetes on DigitalOcean Nameserver limits exceeded" err="Nameserver limits were exceeded, some nameservers have been omitted, the applied nameserver line is: 11.111.11.1 11.111.11.2 11.111.11.1" (example IP addresses used)

After ignoring the error for a bit, I finally had to absolutely solve it due to being unable to deploy a prometheus chart inside my kubernetes cluster.

This isn't really a step-by-step but more an accumulation of resources used/found to finally help solve my problem

TL;DR

• Modify /etc/netplan/50-cloud-init.yaml removing some entries from IFACE.nameservers.address
  • netplan apply to apply changes
• resolvctl to see changes to DNS Servers stanza for the IFACE modified

codeopensrc

Common Linux admin commands

User

adduser (useradd older, less user friendly)

deluser $USER (userdel older, less user friendly)

• Delete home directory
  • deluser --remove-home $USER http://unix.stackexchange.com/questions/289590/cant-add-user-because-group-already-exists

If group already exists

• adduser --ingroup $USER $USER

codeopensrc

PATTERN=*.git

find . -iname '$PATTERN' | sed -e s%./%%g | column

codeopensrc

http://serverfault.com/questions/334448/why-is-ssh-password-authentication-a-security-risk?rq=1

##Specify what commands/hosts the key can use
command="/usr/local/bin/your_backup_script.sh", ssh-rsa auiosfSAFfAFDFJL1234214DFAfDFa...
would allow only the command /usr/local/bin/your_backup_script.sh with that particular key.

from="yourclient,yourotherclient", ssh-rsa auiosfSAFfAFDFJL1234214DFAfDFa...
specify the allowed hosts for the key

codeopensrc

Note:

This is my personal preference which may be different from yours. I'm choosing to do the following:

• Let any user within the git group that is NOT the git user, full access to do what they wish with the repositories, including rename, delete, and move.
  • It is possible to only allow the git group to only modify items within the repositories, but I chose not to at this time (its only me anyway). I'll append how to do this at the end at a later time.
• Let the git user have only enough access to push/pull repositories, list the repositories, and add their public ssh key to git users .ssh/authorized_keys directory.
• Allow only the repo/root/sys admin to place repos in the location to serve them publically.
• Allow only specific repo's to be served publically in a seperate folder.
• Have the shortest url using scp syntax git@serverip:repo.git and git://serverip:repo.git.
• Make sure all permissions we set perfectly so from inception of creating the repo, to pushing for the 100th time,

codeopensrc

NOTE:

This solution works however, your containers can no longer connect to the outside world. Currently searching for a solution where I can whitelist ips to specific ports on an external server while blocking all other external ips.

Example: 2-4 web apps accessable to the internet, 1 mongo container. I would like to connect to the mongo container from my ip and from the containers, but disallow anyone else to connect to the mongo container

Currently its possible, but all containers lose ability to ping/connect outside the container with --iptables=false Otherwise all containers are exposed.

codeopensrc

FROM node

RUN apt-get update && apt-get install -y \
    build-essential \
    apt-utils \
    openjdk-7-jdk \
    vim \
    git

RUN npm i node-gyp -g

codeopensrc

Examples for my RealmWrapper.js and RealmSchema.js

You can find the RealmWrapper here and RealmSchema here

//addRealmListener(fn)
this.realm.addRealmListener(this.updateImgs.bind(this));

codeopensrc

Schema example to my RealmWrapper.js and RealmExamples.md

You can find the RealmWrapper here and RealmExamples here

'use strict';


class Assigned {}

codeopensrc

My RealmWrapper.js file. Uses RealmSchema.js for the schema.

You can find the "realmSchema.js" here and examples here

'use strict';

import Realm from 'realm';
import Schemas from "./realmSchemas.js";
const version = 51;