Create file /etc/systemd/system/docker-compose@.service. SystemD calling binaries using an absolute path. In my case is prefixed by /usr/local/bin, you should use paths specific for your environment.
[Unit]
Description=%i service with docker compose
PartOf=docker.service
After=docker.service
I'm a Scala noob.
I am deploying some Spark jobs which need to talk to various services in our production environment. These services are managed by a ZooKeeper installation that registers their host and ports for service discovery. Hence, our Scala code needs to interact with ZooKeeper to discover the host and ports to use when making HTTPS calls to these internal services.
There is some ScalaDoc for util-zk that describes the classes, objects and function signatures but those don't help me very much since I'm a newb and none of it really makes a ton of sense right now.
So I am writing this document with my discoveries about how the util-zk library behaves empirically.
| # set the base image to Debian | |
| # https://hub.docker.com/_/debian/ | |
| FROM debian:latest | |
| # replace shell with bash so we can source files | |
| RUN rm /bin/sh && ln -s /bin/bash /bin/sh | |
| # update the repository sources list | |
| # and install dependencies | |
| RUN apt-get update \ |
| #!/bin/sh | |
| # Purpose: This script starts and stops the Zookeeper daemon | |
| # chkconfig: - 90 10 | |
| # description: Zookeeper daemon | |
| # Source function library | |
| . /etc/init.d/functions | |
| APP=/opt/zookeeper/bin/zkServer.sh |
| DAEMON_PATH=/opt/kafka/bin | |
| DAEMON_NAME=kafka | |
| # Check that networking is up. | |
| #[ ${NETWORKING} = "no" ] && exit 0 | |
| PATH=$PATH:$DAEMON_PATH | |
| # See how we were called. | |
| case "$1" in | |
| start) |
This entire guide is based on an old version of Homebrew/Node and no longer applies. It was only ever intended to fix a specific error message which has since been fixed. I've kept it here for historical purposes, but it should no longer be used. Homebrew maintainers have fixed things and the options mentioned don't exist and won't work.
I still believe it is better to manually install npm separately since having a generic package manager maintain another package manager is a bad idea, but the instructions below don't explain how to do that.
Installing node through Homebrew can cause problems with npm for globally installed packages. To fix it quickly, use the solution below. An explanation is also included at the end of this document.
| crypto = require('crypto'); | |
| #Quick MD5 of text | |
| text = "MD5 this text!" | |
| md5hash1 = crypto.createHash('md5').update(text).digest("hex") | |
| #MD5 of text with updates | |
| m = crypto.createHash('md5') | |
| m.update("MD5 ") | |
| m.update("this ") |
| git archive --format zip --output /full/path/to/zipfile.zip master |
