I think you have looked at the tutorial from Mr. Heinemeier Hansson at least once or twice and have a similar setup.
rails new kamal_pg --css tailwind --skip-test --database=postgresql
cd kamal_pg
This is a collection of the things I believe about software development. I have worked for years building backend and data processing systems, so read the below within that context.
Agree? Disagree? Feel free to let me know at @JanStette.
Keep it simple, stupid. You ain't gonna need it.
Tava precisando migrar um sistema da Amazon para a Digital Ocean, e para clonar o sistema todo, usei rsync
.
Conectei na máquina a ser migrada/clonada e mandei o seguinte comando:
sudo rsync --numeric-ids -aHAXSve ssh \
--exclude={"/dev/*","/proc/*","/sys/*","/tmp/*","/run/*","/mnt/*","/media/*","/lost+found"} \
/ root@NewServer:/destination/directory
#!/usr/bin/env bash | |
# Script to create ansible playbook directories | |
# With thanks to https://gist.github.com/skamithi/11200462 for giving me the idea | |
# We attempt to lay everything out according to Ansible best practices: | |
# https://docs.ansible.com/ansible/latest/user_guide/playbooks_best_practices.html#playbooks-best-practices#directory-layout | |
gitinit(){ | |
# Start with sensible .gitignore defaults |
/* | |
The MIT License (MIT) | |
Copyright (c) 2016 Andre Leiradella | |
Permission is hereby granted, free of charge, to any person obtaining a copy | |
of this software and associated documentation files (the "Software"), to deal | |
in the Software without restriction, including without limitation the rights | |
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell | |
copies of the Software, and to permit persons to whom the Software is |
You can find a bunch of articles about debugging Gitlab CI jobs locally. My top results from google:
But in all that articles the described way is to install Docker and gitlab-runner
executable,
run gitlab-runner exec docker JOB_NAME_FROM_GITLAB_CI_YML
after that in your repo.
I don't like this approach because I want a simpler way to run appropriate gitlab-runner
executable and don't
A mod is a set of code and assets that changes or augments the way a game is run. Examples of mods are:
# Shell script for automatically creating file collections | |
# initally written to reduce the number of games when downloading | |
# retropie rom collections | |
#!/bin/bash | |
version="0.3.1" | |
collection=() | |
collectionname="" | |
collsize=0 |
#!/bin/bash | |
set -euo pipefail | |
# Here strings are noted to be faster for a small amount of | |
# data as compared to pipes where the setup cost dominates. | |
# https://unix.stackexchange.com/a/219806/158139 | |
response=$(w3m -dump "http://explainshell.com/explain?cmd="$(echo $@ | tr ' ' '+'})) | |
cat -s <(grep -v -e explainshell -e • -e □ -e "source manpages" <<< "$response") |