Just a little demo how to use bootstraps toasts component with HTMX and custom triggers. Toasts are stackable and grouped by message (so the same message doesn't pop up several times, when already open.
A Pen by Marcus at Localhost on CodePen.
Just a little demo how to use bootstraps toasts component with HTMX and custom triggers. Toasts are stackable and grouped by message (so the same message doesn't pop up several times, when already open.
A Pen by Marcus at Localhost on CodePen.
version: '4.5' | |
services: | |
# GITLAB | |
gitlab-web: | |
image: 'gitlab/gitlab-ce:latest' | |
restart: always | |
container_name: gitlab-web | |
hostname: '192.168.0.14' | |
environment: |
Pip is a package manager of python. You can download Python
libraries from some Python
repositories like PyPI
. You can also download libraries from a git
repository. This is gonna be the issue to be explained in this article.
I don't like to memorize things all the time. So, I guess, I couldn't be working without internet :). Whenever I need to install some python libraries from a git repositories, I see a lot of way to do it. It is really confusing. This should be the reason why I can't memorize it. I can see how a very simple requirement is handled with to many confusing way. There shouldn't be to many way. Some of them is not working neither. At last, I decided to blog it.
As you may know, you can use two protocols which are http
and ssh
to do something on git
repositories. Using protocol ssh
instead of http
may provide some ease of use. Because of nature of ssh
, you can do something with your primary/public keys. So, you don't have to input your credentials all the time. But I'll be
from abc import ABCMeta | |
from dramatiq import actor, Message, get_broker | |
def implementation_do_call(self, *args, **kwargs): | |
return self.perform(*args, **kwargs) | |
class BaseActorInterfaceMeta(ABCMeta): | |
DEFAULT_QUEUE_NAME = 'default' |
kubectl get pods | grep Evicted | awk '{print $1}' | xargs kubectl delete pod |
In order to run this image do:
docker-compose up -d
to get all up.
On first run DB initialization and initial user setup is done like so:
First start a bash in the container: docker-compose exec sentry /bin/bash
.
Then, inside bash, do sentry upgrade
wait until it asks you for an inital user.
When finished exit
the bash.
When in doubt check with docker-compose ps
if all went fine.
$ brew install dnsmasq
...
$ cp /usr/local/opt/dnsmasq/dnsmasq.conf.example /usr/local/etc/dnsmasq.conf
/usr/local/etc/dnsmasq.conf
address=/local/127.0.0.1