Commits
- Commit:
fb8a219e2a3363c6ac9f5e819b45cca7ca4a1086- From:
- Oliver Lowe <o@olowe.co>
- Date:
link to the new general mailing list
because there's so many subscribers... lol
- Commit:
87154adc3ffe738b0e1223d666c0ae63e1926399- From:
- Oliver Lowe <o@olowe.co>
- Date:
Run a full test on builds.sr.ht for every commit
On OpenBSD. Why not?
- Commit:
b717ce9bd51371aefd55ccd6ddf623f83aed8e29- From:
- Oliver Lowe <o@olowe.co>
- Date:
Test against a fake in-processs icinga server
A lot of the testing doesn't really flex what a real icinga2 server
does. We can implement a simple fake server with about 250 lines of
Go, then we get all the benefits of really quick feedback and no
dependency on an icinga2 server (which isn't super easy to set up) for
most tests. More complicated tests are still performed against a real
server listening on loopback (if available).
- Commit:
dd1562c064ef82c610805dfd8cdaca5af54f6d22- From:
- Oliver Lowe <o@olowe.co>
- Date:
Always format generated code
While here document what is needed to actually run go generate.
- Commit:
7aa5b0553214edbb1a6e71187215972e1e4877c6- From:
- Oliver Lowe <o@olowe.co>
- Date:
doc: Keep the getting started tutorial in 1 place
- Commit:
2ad5e459c8480946f8762ea1617512d6bfd489bf- From:
- Oliver Lowe <o@olowe.co>
- Date:
Clearer contribution details in README
- Commit:
26fb88e9ebc4192da36411de66032158b424369d- From:
- Oliver Lowe <o@olowe.co>
- Date:
Generate CRUD code using go generate
Explanation for use is in the README
- Commit:
6456042b9dd325c6b9b1e246acac3a21bfae58fe- From:
- Oliver Lowe <o@olowe.co>
- Date:
Complete the README with a tutorial and a "why?"
- Commit:
9ab732cda40be5693e3f1ddba1a5ebf7de9e1bd5- From:
- Oliver Lowe <o@olowe.co>
- Date:
README: use http.DefaultClient in example
The Go devs set useful things for us that we shouldn't lose just
because we're something insecure.
- Commit:
2c4d16aea2e6138d88d6ecb7cec9d9af2e793593- From:
- Oliver Lowe <o@olowe.co>
- Date:
initial commit