The man doveadm-sync pages are cryptic and not very well explained, as well they are missing quality real-world examples.
This gist aims to give some clarity and explanation.
Here is the command I got to successfully transfer (and sync backwards too) an email account from an old Dovecot email server to a new Dovecot email server:
To my knowledge, both servers must have a matching account already setup for this to work:
| My complete configuration is now hosted at https://gitlab.mim-libre.fr/-/snippets/13 |
Deciding how to design your project's architecture is still a complex thing. Everybody while starting a project goes through different articles and blogs to understand the ways to develop your project's architecture.
 |
|---|
| Working on a badly designed project's architecture is as difficult as designing it good. |
The Architecture of your project should be so neat and descriptive such that if a new developer starts working on it, one should not encounter any problem in understanding the patht that the data follows to render the ui.
| #!/bin/bash | |
| # * Set up a temp directory with some stuff in it | |
| # * Preconfigure Salt SSH to run standalone from that temp space | |
| # * Create a roster with minion_ids ($1) and IP's ($2) | |
| # * Run Salt-SSH to Highstate (or $@) the roster | |
| set -x | |
| cd $(dirname $0) | |
| SALT_DIR=${SALT_DIR:-/srv/salt} |
| Work for me with squid 3.4 on debian jessie. | |
| I use it with collectd exec plugin (https://collectd.org/documentation/manpages/collectd-exec.5.shtml) | |
| to collect data from squid, send it over the network to influxdb and visualize with grafana. | |
| Maybe someone will have some use of it. Good luck ;-) | |
| https://gist.github.com/wrzasa/dfd7b554171159a6b2ab24b03b8e30b8/ |
People
 :bowtie: |
😄 :smile: |
😆 :laughing: |
|---|---|---|
😊 :blush: |
😃 :smiley: |
:relaxed: |
😏 :smirk: |
😍 :heart_eyes: |
😘 :kissing_heart: |
😚 :kissing_closed_eyes: |
😳 :flushed: |
😌 :relieved: |
😆 :satisfied: |
😁 :grin: |
😉 :wink: |
😜 :stuck_out_tongue_winking_eye: |
😝 :stuck_out_tongue_closed_eyes: |
😀 :grinning: |
😗 :kissing: |
😙 :kissing_smiling_eyes: |
😛 :stuck_out_tongue: |
| #!/bin/sh | |
| # Credits to: | |
| # - http://vstone.eu/reducing-vagrant-box-size/ | |
| # - https://github.com/mitchellh/vagrant/issues/343 | |
| aptitude -y purge ri | |
| aptitude -y purge installation-report landscape-common wireless-tools wpasupplicant ubuntu-serverguide | |
| aptitude -y purge python-dbus libnl1 python-smartpm python-twisted-core libiw30 | |
| aptitude -y purge python-twisted-bin libdbus-glib-1-2 python-pexpect python-pycurl python-serial python-gobject python-pam python-openssl libffi5 |
| """ | |
| Two things are wrong with Django's default `SECRET_KEY` system: | |
| 1. It is not random but pseudo-random | |
| 2. It saves and displays the SECRET_KEY in `settings.py` | |
| This snippet | |
| 1. uses `SystemRandom()` instead to generate a random key | |
| 2. saves a local `secret.txt` |
| python -c "from random import choice; print ''.join([choice('abcdefghijklmnopqrstuvwxyz0123456789%^*(-_=+)') for i in range(32)])" |
