How to import and indicate empty request or reply messages:
import "google/protobuf/empty.proto";
service SomeService {
rpc SomeOperation (google.protobuf.Empty) returns (google.protobuf.Empty) {}
}
How to import and indicate empty request or reply messages:
import "google/protobuf/empty.proto";
service SomeService {
rpc SomeOperation (google.protobuf.Empty) returns (google.protobuf.Empty) {}
}
This deployment guide covers the steps required to install and configure a single HashiCorp Consul cluster as defined in the Consul Reference Architecture.
Below are instructions for installing and configuring Consul on Linux hosts running the systemd system and service manager.
This deployment guide is designed to work in combination with the Consul Reference Architecture. Although not a strict requirement to follow the Consul Reference Architecture, please ensure you are familiar with the overall architecture design; for example installing Consul on multiple physical or virtual (with correct anti-affinity) hosts for high-availability.
This deployment guide covers the steps required to install and configure a single HashiCorp Vault cluster as defined in the Vault Reference Architecture.
Below are instructions for installing and configuring Vault on Linux hosts running the systemd system and service manager.
This deployment guide is designed to work in combination with the Vault Reference Architecture and Consul Deployment Guide. Although not a strict requirement to follow the Vault Reference Architecture, please ensure you are familiar with the overall architecture design; for example installing Vault on multiple physical or virtual (with correct anti-affinity) hosts for high-availability and using Consul for the HA and storage backend.
This focuses on generating the certificates for loading local virtual hosts hosted on your computer, for development only.
Do not use self-signed certificates in production ! For online certificates, use Let's Encrypt instead (tutorial).
# Pass the env-vars to MYCOMMAND | |
eval $(egrep -v '^#' .env | xargs) MYCOMMAND | |
# … or ... | |
# Export the vars in .env into your shell: | |
export $(egrep -v '^#' .env | xargs) |
#!/bin/bash | |
set -e | |
update_version(){ | |
if [[ "$DONT_BUMP_VERSION" -ne "1" ]] | |
then | |
echo " Bumping version.. " | |
else | |
echo "Version will not be bumped since variable DONT_BUMP_VERSION is set." | |
exit 0 |
sudo sysctl net.ipv4.conf.all.forwarding=1 | |
sudo sysctl net.bridge.bridge-nf-call-iptables=1 | |
sudo sysctl net.bridge.bridge-nf-call-ip6tables=1 | |
//or | |
/sbin/sysctl -w net.ipv4.conf.all.forwarding=1 | |
/sbin/sysctl -w net.bridge.bridge-nf-call-ip6tables=1 | |
/sbin/sysctl -w net.bridge.bridge-nf-call-iptables=1 |
Vagrant.configure("2") do |config| | |
config.vm.box = "maier/alpine-3.3.1-x86_64" | |
config.vm.network "public_network", ip: "192.168.1.31", auto_config: true | |
config.vm.synced_folder ".", "/vagrant", disabled: true | |
config.vm.provider "virtualbox" do |vb| | |
vb.name = 'Alpine1' | |
vb.cpus = 1 | |
vb.memory = 1024 | |
#vb.customize ["modifyvm", :id, "--natdnshostresolver1", "on"] | |
# Display the VirtualBox GUI when booting the machine |
# Image neeeds to have ssh-client | |
image: docker:git | |
services: | |
- docker:dind | |
stages: | |
- staging | |
before_script: | |
- docker login -u gitlab-ci-token -p $CI_BUILD_TOKEN $CI_REGISTRY |
# Assumes the database container is named 'db' | |
DOCKER_DB_NAME="$(docker-compose ps -q db)" | |
DB_HOSTNAME=db | |
DB_USER=postgres | |
LOCAL_DUMP_PATH="path/to/local.dump" | |
docker-compose up -d db | |
docker exec -i "${DOCKER_DB_NAME}" pg_restore -C --clean --no-acl --no-owner -U "${DB_USER}" -d "${DB_HOSTNAME}" < "${LOCAL_DUMP_PATH}" | |
docker-compose stop db |