James Strong strongjz

Introduction

This is a guide to deploying Nextcloud behind a Caddy reverse proxy, both running in Docker containers (an official Nextcloud one and a caddy-docker-proxy one), with the goal of implementing as much as possible via docker-compose files. This is much more difficult than it should be, for a variety of reasons:

As with Docker versions of software in general, documentation of the software does not always apply to the Docker versions, and the Docker documentation does not always include the Docker equivalent ways of doing things.
Docker images do not always expose the desired configuration knobs of the underlying software.
Nextcloud requires special configuration to run correctly behind a reverse proxy (and again, some of the instructions for this configuration requires modification for

Linux Networking Reading List

Currently in no particular order. Most of these are kind of ancient.

Where's all the modern documentation? So much of what I've turned up searching is other folks complaining about having few options beyond reading source code.

The OREILLY books, while dated, seem to be some of the best available. Note that these can be read with a 7-day trial. Do this! At least get through the introduction section and first chapter of each to see if it's what you're after.

https://www.netfilter.org/

Kubernetes Tutorial Install Instructions

If you have any questions or run into any problems, please don't hesitate to contact me here: [email protected]

All Platforms

Ensure your laptop has Virtualization Extensions (Intel VT or AMD-V) enabled and is capable of running a 2 core, 2GB RAM Virtual Machine.

Software to be Installed

You can use CodePipeline and CodeBuild to create a continuous deployment/integration pipeline for serverless applications build on AWS Lambda and Amazon API Gateway. This sample application is written in Go with the Gin framework and uses the eawsy API Gateway proxy shim: https://github.com/eawsy/aws-lambda-go-net

We initially detailed our methodology in this blog post: https://aws.amazon.com/blogs/compute/continuous-deployment-for-serverless-applications/

We have used the shim technology created by eawsy to run Golang applications inside AWS Lambda (https://github.com/eawsy/aws-lambda-go-shim) and created a container that can be used with CodeBuild as part of our original pipeline template.

The container is available on DockerHub and is called sapessi/aws-lambda-go18-codebuild:latest. To use this container, simply change the Image property of the CodeBuild project environment.

The pipeline template, sample app, buildspec and SAM files are attached to this gist.

	1="Unsupported protocol. This build of curl has no support for this protocol."
	2="Failed to initialize."
	3="URL malformed. The syntax was not correct."
	4="A feature or option that was needed to perform the desired request was not enabled or was explicitly disabled at build-time. To make curl able to do this, you probably need another build of libcurl!"
	5="Couldn't resolve proxy. The given proxy host could not be resolved."
	6="Couldn't resolve host. The given remote host was not resolved."
	7="Failed to connect to host."
	8="Weird server reply. The server sent data curl couldn't parse."
	9="FTP access denied. The server denied login or denied access to the particular resource or directory you wanted to reach. Most often you tried to change to a directory that doesn't exist on the server."
	10="FTP accept failed. While waiting for the server to connect back when an active FTP session is used, an error code was sent over the control connection or similar."



	echo ""
	echo "********** Github Dork Links (must be logged in) *****************"
	echo ""
	echo " password"
	echo "https://github.com/search?q="hackertarget.site"+password&type=Code"
	echo "https://github.com/search?q=""hackertarget""+password&type=Code"
	echo ""
	echo " npmrc _auth"

	1="Unsupported protocol. This build of curl has no support for this protocol."
	2="Failed to initialize."
	3="URL malformed. The syntax was not correct."
	4="A feature or option that was needed to perform the desired request was not enabled or was explicitly disabled at build-time. To make curl able to do this, you probably need another build of libcurl!"
	5="Couldn't resolve proxy. The given proxy host could not be resolved."
	6="Couldn't resolve host. The given remote host was not resolved."
	7="Failed to connect to host."
	8="Weird server reply. The server sent data curl couldn't parse."
	9="FTP access denied. The server denied login or denied access to the particular resource or directory you wanted to reach. Most often you tried to change to a directory that doesn't exist on the server."
	10="FTP accept failed. While waiting for the server to connect back when an active FTP session is used, an error code was sent over the control connection or similar."

	#!/bin/bash

	# This script creates a docker config.json file with the auth section
	# as an example of what can be passed into GitLab-CI and used in
	# conjunction with DOCKER_CONFIG - the config file directory location.

	# command line parameter default values
	DOCKER_REGISTRY=""
	DOCKER_USER=""
	DOCKER_PASSWORD=""

	alias kc='kubectl'
	alias kclf='kubectl logs --tail=200 -f'
	alias kcgs='kubectl get service -o wide'
	alias kcgd='kubectl get deployment -o wide'
	alias kcgp='kubectl get pod -o wide'
	alias kcgn='kubectl get node -o wide'
	alias kcdp='kubectl describe pod'
	alias kcds='kubectl describe service'
	alias kcdd='kubectl describe deployment'
	alias kcdf='kubectl delete -f'

	#
	# Avoid the message 'External file changes sync may be slow: The current inotify(7) watch limit is too low.' from JetBrains products.
	#
	# 1. Create the file /etc/sysctl.d/60-jetbrains.conf and paste this code
	# 2. Restart the sysctl service: sudo sysctl -p --system
	# 3. Restart the IDE
	#
	# More info:
	# https://confluence.jetbrains.com/display/IDEADEV/Inotify+Watches+Limit