This is guide about how to configure multiple SSH keys for some Git host websites such as Github, Gitlab, among others.
Discover gists
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
while True: | |
try: | |
x = int(input("How long do you want your popper to be? ").strip()) | |
break | |
except ValueError: | |
print("Not an int") | |
continue | |
s = input("what should your custom word be? ") |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
version: '3.4' | |
services: | |
sql.data: | |
image: mcr.microsoft.com/mssql/server:2017-latest | |
container_name: dev_sql | |
environment: | |
- SA_PASSWORD=yourStrong(!)Password | |
- ACCEPT_EULA=Y | |
healthcheck: |
Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.
- Follow standard conventions.
- Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
- Boy scout rule. Leave the campground cleaner than you found it.
- Always find root cause. Always look for the root cause of a problem.
See how a minor change to your commit message style can make a difference.
Tip
Have a look at git-conventional-commits , a CLI util to ensure these conventions and generate verion and changelogs
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
local state, data, reactor, turbine, info_window, rules_window | |
local STATES = { | |
READY = 1, -- Reactor is off and can be started with the lever | |
RUNNING = 2, -- Reactor is running and all rules are met | |
ESTOP = 3, -- Reactor is stopped due to rule(s) being violated | |
UNKNOWN = 4, -- Reactor or turbine peripherals are missing | |
} | |
------------------------------------------------ |
In the apps config/puma.rb
file:
Change to match your CPU core count
# Check using this on the server => grep -c processor /proc/cpuinfo
workers 4
# Min and Max threads per worker
threads 1, 6
app_dir = File.expand_path('../..', FILE)
- You can still selfhost the bot (view
selfhosting-guide
in the support server)
INFO
The only selfhosted Loggers listed here will be from trusted members of the Logger support server. If you're selfhosting and a trusted member and want your selfhosted Logger to be listed then we'll reach out to you directly, don't ask to be listed here.NewerOlder