aschiavon91

• Enable SecureBoot with default options.
• Wait for Windows installation normally.
• After windows setup finishes, enter in BIOS and complettly disable secure boot.
• cleanup all SecureBoot keys from BIOS, disable plataform key injection and then disable SecureBoot, be sure all keys are delete before continue.
• Install PopOS normally.
• After PopOS setup finishes, ensure that the boot order in bios is setted to firstly boot to the disk used to install PopOS not to the system partition.
• Boot into PopOS and install/reinstall shim-signed, mokutil and sbctl.
• check sbctl status, u should see something like:

  # sbctl status

george124816

# interactive command
gpg2 --full-generate-key

# get keyID
gpg2 --list-secret-keys --keyid-format=long


att .gitconfig with KEYID

`git config --global user.signingkey 3AA5C34371567BD2`

ananthakumaran

(defface tree-sitter-hl-face:warning
  '((default :inherit font-lock-warning-face))
  "Face for parser errors"
  :group 'tree-sitter-hl-faces)

(defun hook/tree-sitter-common ()
  (unless font-lock-defaults
    (setq font-lock-defaults '(nil)))
  (setq tree-sitter-hl-use-font-lock-keywords nil)
  (tree-sitter-mode +1)

edsoncelio

Usando o projeto https://github.com/dockersamples/example-voting-app, fazer as seguintes alterações:
Importante: criar uma branch para cada alteração abaixo

Deployment by docker-compose

1. No arquivo docker-compose.yml:
   • Verificar quais imagens são usados como base, e fazer o build externo e salvando em um registry (aplicando boas práticas de tageamento)
   • Retirar todos os builds e alterar para apontar para as imagens no registry usado
   • Usar docker volumes para persistir os dados
2. Configurar CI com os seguintes requisitos (usar Github Actions ou TravisCI):

wosephjeber

Renaming table in Ecto migration

I recently wanted to rename a model and its postgres table in a Phoenix app. Renaming the table was simple and documented, but the table also had constraints, sequences, and indexes that needed to be updated in order for the Ecto model to be able to rely on default naming conventions. I couldn't find any examples of what this would look like but was eventually able to figure it out. For anyone else in the same situation, hopefully this example helps.

In the example below, I'm renaming the Permission model to Membership. This model belongs to a User and an Account, so it has foreign key constraints that need to be renamed.

defmodule MyApp.Repo.Migrations.RenamePermissionsToMemberships do
  use Ecto.Migration

streetturtle

#!/bin/bash

#
# This is sp, the command-line Spotify controller. It talks to a running
# instance of the Spotify Linux client over dbus, providing an interface not
# unlike mpc.
#
# Put differently, it allows you to control Spotify without leaving the comfort
# of your command line, and without a custom client or Premium subscription.
#

codenirvana

notify-send -u normal -i /usr/share/icons/Paper/64x64/apps/email.png "New Email" "${USER^} you have a new email!" && paplay /usr/share/sounds/freedesktop/stereo/message-new-instant.oga 

rdeavila

#!/bin/bash
# Adicione um novo remote; pode chamá-lo de "upstream":

git remote add upstream https://github.com/usuario/projeto.git

# Obtenha todos os branches deste novo remote,
# como o upstream/master por exemplo:

git fetch upstream

wandernauta

#!/usr/bin/env bash

#
# This is sp, the command-line Spotify controller. It talks to a running
# instance of the Spotify Linux client over dbus, providing an interface not
# unlike mpc.
#
# Put differently, it allows you to control Spotify without leaving the comfort
# of your command line, and without a custom client or Premium subscription.
#