Explore >> Select a destination
|
You are here 
|
lukasrotermund.de | ||
| | | | |
benhoyt.com
|
|
| | | | | My re-implementation of the code from the official Go tutorial 'Developing a RESTful API with Go and Gin', using only the standard library, adding tests, and fixing issues. | |
| | | | |
hjr265.me
|
|
| | | | | I wanted to list all the time zones in Go. The standard library in Go comes with the time package. It also comes with the time/tzdata package. The standard time package in Go is very well-thought-out. It makes date-time manipulation deceptively simple. Yet, I could not find a way to list all the time zones. Time Zone Database The documentation for time.LoadLocation describes how Go uses four sources of time zone data: | |
| | | | |
schadokar.dev
|
|
| | | | | In this tutorial we'll learn how to use json in golang. | |
| | | | |
jan.wildeboer.net
|
|
| | | 0. The Journey - The basics and outlook (on the series, not the Microsoft mail client ;) 1. Postfix - the in and out, so to say. The robust, battle-hardened connection point for other mail servers on the internet to send emails to and receive emails from your domain(s). Also known as the MTA, the Mail Transfer Agent. 2. Dovecot - where you and your users talk to to get emails to their mail client, be it your smartphone, a mail client on your computer or just even the command line. It's the IMAP server. 3. DKIM/DMARC/SPF - Just having postfix and dovecot up and running isn't enough. We will also look at user authentication, letsencrypt certificates, DKIM, DMARC, SPF and the daily checks to make sure everything is humming along nicely. 4. The final stuff - How... | ||
