https://unix.stackexchange.com/a/204896 sudo update-alternatives --config editor

Chrome Remote Desktopを導入したUbuntu 20.04に自動ログインを設定すると、 初回の認証はkeyringのロックを解除する認証だが、ほかにも5回程度繰り返し認証を求められる。 以下のようなメッセージが表示される。 Authentication is required to create a color managed device 以下のファイルのうち、いずれかを作成することで、追加の認証をスキップできる。 /etc/polkit-1/localauthority.conf.d/02-allow-colord.conf https://god-support.blogspot.com/2019/11/ubuntu1804-xrdp-authentication-is.html polkit.addRule(function(action, subject) { if (( action.id == "org.freedesktop.color-manager.create-device" || action.id == "org.freedesktop.color-manager.create-profile" || action.id == "org.freedesktop.color-manager.delete-device" || action.id == "org.freedesktop.color-manager.delete-profile" || action.id == "org.freedesktop.color-manager.modify-device" || action.id == "org.freedesktop.color-manager.modify-profile" ) && subject.isInGroup("{users}") ) { return polkit.Result.YES; } }); /etc/polkit-1/localauthority/50-local.d/45-allow-colord.pkla https://www.cagylogic.com/archives/2021/03/23145121/11743.php [Allow Colord all Users] Identity=unix-user:* Action=org.freedesktop.color-manager.create-device;org.freedesktop.color-manager.create-profile;org.freedesktop.color-manager.delete-device;org.freedesktop.color-manager.delete-profile;org.freedesktop.color-manager.modify-device;org.freedesktop.color-manager.modify-profile ResultAny=no ResultInactive=no ResultActive=yes

https://remotedesktop.google.com/access https://qiita.com/ninose14/items/473369d76814174dd58f インストール https://remotedesktop.google.com/headless rm -f ~/.chrome-remote-desktop-session スクリプトの改変 cd /opt/google/chrome-remote-desktop cp chrome-remote-desktop chrome-remote-desktop.bak /opt/google/chrome-remote-desktop/chrome-remote-desktop chrome-remote-desktop 106.0.5249.37 #FIRST_X_DISPLAY_NUMBER = 20 FIRST_X_DISPLAY_NUMBER = 0 ※ 0の部分には、デスクトップ環境でターミナルを開き、echo $DISPLAYで表示される値を入れる。 def launch_session(self, server_args, backoff_time): """Launches process required for session and records the backoff time for inhibitors so that process restarts are not attempted again until that time has passed.""" logging.info("Setting up and launching session") self._init_child_env() self.setup_audio() self._setup_gnubby() #self._launch_server(server_args) #if not self._launch_pre_session(): # # If there was no pre-session script, launch the session immediately. # self.launch_desktop_session() display = self.get_unused_display_number() self.child_env['DISPLAY'] = f':{display}' self.server_inhibitor.record_started(MINIMUM_PROCESS_LIFETIME, backoff_time) self.session_inhibitor.record_started(MINIMUM_PROCESS_LIFETIME, backoff_time) sudo systemctl restart chrome-remote-desktop@${USER}.service

https://wiki.archlinux.jp/index.php/Davfs2 /etc/fstab https://nextcloud.example.com/remote.php/dav/files/myuser/ /mnt/nextcloud davfs rw,nofail,user,uid=myuser 0 0 /etc/davfs2/secrets https://nextcloud.example.com/remote.php/dav/files/myuser/ myuser APP_PASSWORD

https://launchpad.net/~nextcloud-devs/+archive/ubuntu/client sudo apt install software-properties-common sudo add-apt-repository ppa:nextcloud-devs/client sudo apt update sudo apt install nextcloud-desktop nautilus-nextcloud

https://hub.docker.com/_/wordpress docker-compose.yml version: "3.9" services: wordpress: image: wordpress:5.8.2-apache restart: always ports: - "${SERVER_PORT}:80" environment: WORDPRESS_DB_HOST: db WORDPRESS_DB_USER: wordpress WORDPRESS_DB_PASSWORD: wordpress WORDPRESS_DB_NAME: wordpress volumes: - wordpress:/var/www/html db: image: mariadb:10.7 restart: always environment: MYSQL_DATABASE: wordpress MYSQL_USER: wordpress MYSQL_PASSWORD: wordpress MYSQL_RANDOM_ROOT_PASSWORD: '1' volumes: - db:/var/lib/mysql volumes: wordpress: db: .env SERVER_PORT=127.0.0.1:8000

ビルドコマンド https://stackoverflow.com/questions/58592259/how-do-you-enable-buildkit-with-docker-compose DOCKER_BUILDKIT=1 COMPOSE_DOCKER_CLI_BUILD=1 docker-compose build Dockerfile https://www.docker.com/blog/introduction-to-heredocs-in-dockerfiles/ # syntax=docker/dockerfile:1.3-labs

https://unix.stackexchange.com/questions/470709/how-do-i-stop-disable-unattended-upgrades-from-being-launched-automatically 勝手にnvidia driverの更新が走って、 カーネルに読み込まれているdriverバージョンと、 ディスク上にあるdriverバージョンが一致しなくなって、 デスクトップアプリが起動しなくなったりする。 どうせ結構な頻度でapt upgradeするし、 再起動が保証されないタイミングで更新されて、 不安定になるのはいただけない。 sudo dpkg-reconfigure -plow unattended-upgrades これでTUIが起動するので、<No>を選ぶ。

https://github.com/ArchiveBox/ArchiveBox https://hub.docker.com/r/archivebox/archivebox curl -O 'https://raw.githubusercontent.com/ArchiveBox/ArchiveBox/master/docker-compose.yml' docker-compose.yml # Usage: # docker-compose run archivebox init --setup # docker-compose up # echo "https://example.com" | docker-compose run archivebox archivebox add # docker-compose run archivebox add --depth=1 https://example.com/some/feed.rss # docker-compose run archivebox config --set PUBLIC_INDEX=True # docker-compose run archivebox help # Documentation: # https://github.com/ArchiveBox/ArchiveBox/wiki/Docker#docker-compose version: "3.9" services: archivebox: image: archivebox/archivebox:sha-f809e3b command: server --quick-init 0.0.0.0:8000 ports: - "${SERVER_PORT:-8000}:8000" environment: ALLOWED_HOSTS: "*" MEDIA_MAX_SIZE: 2g # SEARCH_BACKEND_ENGINE: sonic # uncomment these if you enable sonic below # SEARCH_BACKEND_HOST_NAME: sonic # SEARCH_BACKEND_PASSWORD: SecretPassword volumes: - "${DATA_ROOT:-./data}:/data" # To run the Sonic full-text search backend, first download the config file to sonic.cfg # curl -O https://raw.githubusercontent.com/ArchiveBox/ArchiveBox/master/etc/sonic.cfg # after starting, backfill any existing Snapshots into the index: docker-compose run archivebox update --index-only # sonic: # image: valeriansaliou/sonic:v1.3.0 # environment: # SEARCH_BACKEND_PASSWORD: SecretPassword # volumes: # - ./sonic.cfg:/etc/sonic.cfg:ro # - ./data/sonic:/var/lib/sonic/store ### Optional Addons: tweak these examples as needed for your specific use case # Example: Run scheduled imports in a docker instead of using cron on the # host machine, add tasks and see more info with archivebox schedule --help # scheduler: # image: archivebox/archivebox:latest # command: schedule --foreground --every=day --depth=1 'https://getpocket.com/users/USERNAME/feed/all' # environment: # USE_COLOR: True # SHOW_PROGRESS: False # volumes: # - ./data:/data .env SERVER_PORT=127.0.0.1:8000 DATA_ROOT=./data 初期設定 管理ユーザの作成、プライベートサーバ化、再起動。 ...

https://github.com/itzg/docker-minecraft-server https://feedback.minecraft.net/hc/en-us/sections/360001186971-Release-Changelogs docker-compose.yml version: "3.9" services: minecraft: image: itzg/minecraft-server ports: - "${SERVER_PORT}:25565" environment: EULA: "TRUE" OVERRIDE_SERVER_PROPERTIES: 'false' # overwrite on every container start if true TZ: ${TZ} TYPE: ${TYPE} # https://github.com/itzg/docker-minecraft-server#server-types VERSION: ${VERSION} # https://feedback.minecraft.net/hc/en-us/sections/360001186971-Release-Changelogs SERVER_NAME: ${SERVER_NAME} MOTD: ${MOTD} ENABLE_WHITELIST: ${ENABLE_WHITELIST} WHITELIST: ${WHITELIST} OPS: ${OPS} SPAWN_PROTECTION: ${SPAWN_PROTECTION} VIEW_DISTANCE: ${VIEW_DISTANCE} SEED: ${SEED} DIFFICULTY: ${DIFFICULTY} MODE: ${MODE} PVP: ${PVP} LEVEL_TYPE: ${LEVEL_TYPE} GENERATOR_SETTINGS: ${GENERATOR_SETTINGS} ONLINE_MODE: ${ONLINE_MODE} tty: true stdin_open: true restart: unless-stopped volumes: - ./data:/data .env SERVER_PORT=0.0.0.0:25565 TZ=Asia/Tokyo TYPE=VANILLA VERSION=1.17.1 SERVER_NAME=MyServer MOTD=A Vanilla Minecraft Server powered by Docker ENABLE_WHITELIST=true WHITELIST=user1,user2 OPS=user1 SPAWN_PROTECTION=0 VIEW_DISTANCE= SEED= DIFFICULTY=normal MODE=survival PVP=true LEVEL_TYPE= GENERATOR_SETTINGS= ONLINE_MODE=true スーパーフラット https://github.com/itzg/docker-minecraft-server#level-type-and-generator-settings https://minecraft.fandom.com/wiki/Superflat ※ 1.17.1でうまく動きませんでした（常にデフォルトのフラットワールドが生成される）。 代わりに、クライアントでワールドを生成してからサーバにコピーする方法が使えます。 ...