This could be related to GitHub rate limits being reached. Specify your GitHub API token to avoid it.
For example by the following command:
composer config --global github-oauth.github.com <TOKEN>
or inside your composer.json file:
#!/usr/bin/env -S bash -c "docker run -p 8080:8080 -it --rm \$(docker build --progress plain -f \$0 . 2>&1 | tee /dev/stderr | grep -oP 'sha256:[0-9a-f]*')" | |
# syntax = docker/dockerfile:1.4.0 | |
FROM node:20 | |
WORKDIR /root | |
RUN npm install sqlite3 |
modules: | |
https_2xx: | |
prober: http | |
timeout: 5s | |
http: | |
method: GET | |
no_follow_redirects: false | |
fail_if_ssl: false | |
fail_if_not_ssl: true | |
preferred_ip_protocol: "ipv4" |
Info: https://www.nginx.com/resources/admin-guide/nginx-https-upstreams/
Source: http://nategood.com/client-side-certificate-authentication-in-ngi
This is SSL, so you'll need an cert-key pair for you/the server, the api users/the client and a CA pair. You will be the CA in this case (usually a role played by VeriSign, thawte, GoDaddy, etc.), signing your client's certs. There are plenty of tutorials out there on creating and signing certificates, so I'll leave the details on this to someone else and just quickly show a sample here to give a complete tutorial. NOTE: This is just a quick sample of creating certs and not intended for production.
FROM alpine:3.4 | |
##################### Base dependencies ################################# | |
RUN apk --no-cache add ruby ruby-irb ruby-json git ruby-bigdecimal ruby-rake \ | |
ruby-io-console ruby-bundler libstdc++ tzdata postgresql-client nodejs \ | |
libxml2 libxslt libgcrypt sqlite-libs pcre curl postgresql bash procps openssh \ | |
&& cp /usr/bin/pg_dump /usr/bin/pg_restore /tmp/ \ | |
&& apk del --purge postgresql \ | |
&& mv /tmp/pg_dump /tmp/pg_restore /usr/bin/ \ | |
&& echo "gem: --no-document" > /etc/gemrc |
#!/bin/sh | |
# Make sure to: | |
# 1) Name this file `backup.sh` and place it in /home/ubuntu | |
# 2) Run sudo apt-get install awscli to install the AWSCLI | |
# 3) Run aws configure (enter s3-authorized IAM user and specify region) | |
# 4) Fill in DB host + name | |
# 5) Create S3 bucket for the backups and fill it in below (set a lifecycle rule to expire files older than X days in the bucket) | |
# 6) Run chmod +x backup.sh | |
# 7) Test it out via ./backup.sh |
[Unit] | |
Description=Bitcoin's distributed currency daemon | |
After=network.target | |
[Service] | |
User=pi | |
Group=pi | |
Type=forking | |
PIDFile=/var/lib/bitcoind/bitcoind.pid |
CloudFormation snippet to create a VPC to be used for lambda functions. Qualities of the VPC:
Notes:
#!/bin/bash | |
# Flushing all rules | |
iptables -F FORWARD | |
iptables -F INPUT | |
iptables -F OUTPUT | |
iptables -X | |
# Setting default filter policy | |
iptables -P INPUT DROP | |
iptables -P OUTPUT DROP | |
iptables -P FORWARD DROP |