- esxi host
- dns or ip for both - esx and vcenter
- correct time settings (ntp automates this, can be enabled on the esx-host)
- use vcsa-cli installer (the iso contains vcsa-cli for win/lin/mac os)
- "skipManifestCheck": "true" because of reasons (the installer repeatedly failed to verify integrity hashes of the created vm)
- "os.password" and "sso.password" HAVE to pass vmware's pw rules PLUS their dictionary! (verification will pass with a pw in their dictionary but setup will not be able to complete! - we stumbled across this by pure chance after trying for 2 whole days!)
Moved to Shopify/graphql-design-tutorial
| #!/bin/bash | |
| # This script purges the local history older than 90 days in some rooms, that you can define in an array | |
| # | |
| # crontab -e | |
| # 23 4 * * * bash /home/irc-bridge/.synapse/EIGENE_purge_history_daily > /dev/null 2>&1 | |
| cd /home/irc-bridge/.synapse/ | |
| DOMAIN="matrix.yourserver.org" | |
| ADMIN="@some_adminuser:matrix.yourserver.org" |
| #!/bin/bash | |
| name=$RANDOM | |
| url='http://localhost:9093/api/v1/alerts' | |
| echo "firing up alert $name" | |
| # change url o | |
| curl -XPOST $url -d "[{ | |
| \"status\": \"firing\", |
This is a guide that I wrote to improve the default security of my website https://fortran.io , which has a certificate from LetsEncrypt. I'm choosing to improve HTTPS security and transparency without consideration for legacy browser support.
WARNING: if you mess up settings, lose your certificates, or decide to no longer maintain HTTPS certs, these steps can and will make your domain inaccessible.
I would recommend these steps only if you have a specific need for information security, privacy, and trust with your users, and/or maintain a separate secure.example.com domain which won't mess up your main site. If you've been thinking about hosting a site on Tor, then this might be a good option, too.
The best resources that I've found for explaining these steps are https://https.cio.gov , https://certificate-transparency.org , and https://twitter.com/konklone
While I'm learning how to use Nginx, I was instructed to update the server_names_hash_bucket_size (/etc/nginx/nginx.conf) value from 32 to 64, but I don't understand why should I increase the value to 64.
References that have been read so far:
- See the Server names, Optimization section.
- See setting up hashes
| # import config. | |
| # You can change the default config with `make cnf="config_special.env" build` | |
| cnf ?= config.env | |
| include $(cnf) | |
| export $(shell sed 's/=.*//' $(cnf)) | |
| # import deploy config | |
| # You can change the default deploy config with `make cnf="deploy_special.env" release` | |
| dpl ?= deploy.env | |
| include $(dpl) |