Please note, it's easier to just use a recovery flash drive/dvd disk!
I just wanted a new challenge, and I found it:
My friend has switched from Windows to Fedora. Somehow in the process, Windows Bootloader went missing from EFI partition (I would love to know how did that happen as much as you do or don't, but I wasn't supervising at the moment, so... no idea)
vSphere 6 Enterprise Plus: | |
1C20K-4Z214-H84U1-T92EP-92838 | |
1A2JU-DEH12-48460-CT956-AC84D | |
MC28R-4L006-484D1-VV8NK-C7R58 | |
5C6TK-4C39J-48E00-PH0XH-828Q4 | |
4A4X0-69HE3-M8548-6L1QK-1Y240 | |
vSphere with Operations Management 6 Enterprise: | |
4Y2NU-4Z301-085C8-M18EP-2K8M8 | |
1Y48R-0EJEK-084R0-GK9XM-23R52 |
There is already a guide on scaling your Mastodon server up. This is a short guide on scaling your Mastodon server down.
I.e., maybe you want to run a small instance of <100 active users, and you want to keep your cloud costs reasonable.
So you might be running everything on a single machine, with limited memory and CPU. (In my case, I was using a t3.medium
instance with 2 vCPUs and 4GB of RAM.) How
do you do this?
Note that I'm not a Ruby or Sidekiq expert, and most of this stuff I figured out through trial and error.
They should work. Works for all cores of your host system. Also you can download ESXi from here.
Discord is now slowly rolling out the ability to send colored messages within code blocks. It uses the ANSI color codes, so if you've tried to print colored text in your terminal or console with Python or other languages then it will be easy for you.
To be able to send a colored text, you need to use the ansi
language for your code block and provide a prefix of this format before writing your text:
\u001b[{format};{color}m
#!/bin/bash | |
tail -n +0 $1 \ | |
| nl -ba \ | |
| fzf --multi \ | |
--ansi \ | |
--no-sort \ | |
--reverse \ | |
--tac \ | |
--preview 'sed -n "$(({n}-4)),$(({n}+6))p" '$1' | nl -v $(({n}-4)) -ba' \ |
가끔 kubernetes 같은건 너무 무거워서 단일 호스트에 docker만 띄워서 운영하는 경우같은걸 고민 하게 됩니다. 하지만 그냥 docker만 가지고 사용하면 컨테이너가 죽었을때 관리해 줘야 하는 불편함과 같이 기능을 보다 더 필요로 하게 됩니다. 그래서 이 방법을 소개해 드립니다.
이건 standalone kubelet 이라고 불리는 master 없이 node만 관리해주는 kubelet을 이용해서 container를 관리하는 방법입니다. 이건 k8s 초기 부터 원래 존재했던 컨셉이나 많이 알려져 있지 않아서 모르시는 분들이 많아서 이글을 작성해 봤습니다.
이 방법을 이용하면 실제 master 없이 kubelet 만으로 서비스를 할 수 있습니다. 컨테이너 자동 재시작, port forwarding, resource limit 등 기본적인 kubelet에서 제공하는 다양한 방법으로 컨테이너들을 관리 할 수 있습니다.
// when T is any|unknown, Y is returned, otherwise N | |
type IsAnyUnknown<T, Y, N> = unknown extends T ? Y : N; | |
// when T is never, Y is returned, otherwise N | |
type IsNever<T, Y = true, N = false> = [T] extends [never] ? Y : N; | |
// when T is a tuple, Y is returned, otherwise N | |
// valid tuples = [string], [string, boolean], | |
// invalid tuples = [], string[], (string | number)[] |
#!/bin/bash | |
## This is a setup script for temporary sharing of an internet connection | |
## Configure the variables at the top of this file, then run: | |
## sudo ./internet-sharing.sh setup | |
## And optionally start the DHCP server: | |
## sudo ./internet-sharing.sh dhcp | |
## Connect your other computer or LAN to the second network device. | |
## Dnsmasq will output the IP address(es) of connected clients as they request them. | |
## Press Ctrl-C to quit dnsmasq when you no longer need DHCP. |