Configure DNS

When installing Cnavas-lms on docker, I got error below: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 $ source ~/env1/bin/activate $ ./script/docker_dev_setup.sh ________ ________ ________ ___ ___ ________ ________ |\ ____\|\ __ \|\ ___ \|\ \ / /|\ __ \|\ ____\ \ \ \___|\ \ \|\ \ \ \\ \ \ \ \ / / | \ \|\ \ \ \___|_ \ \ \ \ \ __ \ \ \\ \ \ \ \/ / / \ \ __ \ \_____ \ \ \ \____\ \ \ \ \ \ \\ \ \ \ / / \ \ \ \ \|____|\ \ \ \_______\ \__\ \__\ \__\\ \__\ \__/ / \ \__\ \__\____\_\ \ \|_______|\|__|\|__|\|__| \|__|\|__|/ \|__|\|__|\_________\ \|_________| Welcome!

Invalidating files in CloudFront

Problem After updating web content in S3 bucket, the page is was not reflected because CloudFront has file cache (for 24 hours by default). The file path is: 1 2 3 ./index.html ./error.html ./css/style.css Solution Ref. AWS CloudFront - Developer Guide - Invalidating Files CloudFront が、Amazon S3 から古いコンテンツを提供し続けるのはなぜですか? The document suggests 2 ways to update(invalidate) the cache on CloudFront. Invalidating Files Using Versioned File Names Note 1000 times invalidation / month is free for each AWS account.

Host HTTPS Website by AWS CloudFront

1. Requirement AWS S3 Bucket (with enabling static website hosting) Bucket endpoint (at “static website hosting” at S3 console) permission to public reading access to the Bucket 2. Create a CloudFront web distribution Sign in to CloudFront console “Create distribution” > “Get Started” Specify settings for the distribution Origin Domain Name : “S3 bucket endpoint” Viewer Protocol Policy : “HTTPS Only” Allowed HTTP Method : “GET, HEAD” Alternate Domain Names : blank (change later) SSL certificate : Default CloudFont Certificate(change later) Supported HTTP version : “HTTP/2, HTTP/1.

Hosting static site on AWS S3

1. Consideration 1.1. Use S3 At first, I tried to host Github Pages for a home page. However, github says I need to upgrade github account or make repository public to host web page. So, I decided host my minimal page to Amazon S3. 1.2. HTTPS According to Amazon S3 ユーザーガイド S3 を使用して静的ウェブサイトをホスティングする, Amazon S3 ウェブサイトエンドポイントは HTTPS をサポートしていません。Amazon S3 バケットで HTTPS を使用する方法については、以下を参照してください。 CloudFront を使用して Amazon S3 バケットに対する HTTPS リクエストを処理するにはどうすればよいですか?

Custom Domain for GitLab Pages

I want to migrate my former site on wordpress to here (Hugo on gitlab.io) with keeping domain. I tried several ways, but the best is just following official GitLab Docs - Custom domains and SSL/TLS Certificates]. Existing my domain Website () 1. Requirements: A GitLab Pages website up and running, served under the default Pages domain (*.gitlab.io, for GitLab.com) A custom domain name example.com or subdomain subdomain.

Ubuntu SSH Server Configuration

1. Environment Server: 1 2 3 4 5 6 lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic Client: Macbook Pro 2. Install Open SSH Server Check ssh client (installed by default on Ubuntu 18.04 TLS) 1 2 3 $ dpkg -l | grep ssh ii libssh-4:amd64 0.8.0~20170825.94fa1e38-1ubuntu0.7 amd64 tiny C SSH library (OpenSSL flavor) ii openssh-client 1:7.