Recent activity

Re: Hello! 7 months ago

From Daniel Wilkins to ~tekk/old-computer-challenge

On Fri, Oct 07, 2022 at 02:31:04PM +0000, prahou wrote:
> This is my introductory email to the mailing list.
> 
> It's me, prahou. I updated the archive website 
> and added relevant channels on how to join the
> occ club ;)
> 
> https://www.triapul.cz/occ/
> 
> Bye.
Welcome to the list :D

[PATCH] Document 'd' shortcut for sprig, minor cleanups. 1 year, 8 months ago

From Danny Wilkins to ~whereswaldon/arbor-dev

---
 getting-started.md | 13 +++++++------
 1 file changed, 7 insertions(+), 6 deletions(-)

diff --git a/getting-started.md b/getting-started.md
index 7f030b4..6c83c23 100644
--- a/getting-started.md
+++ b/getting-started.md
@@ -26,22 +26,23 @@ To the right of the selected message, there is a `Reply` button. Clicking that r
At the top of the message view, there are four buttons. From left to right:

- Hamburger menu
  - Switch between the settings, the conversation view, and other pages
  - Switch between the settings, the conversation view, and other page.
[message trimmed]

[PATCH] Add a version of giohyperlink that supports BSDs 1 year, 10 months ago

From Danny Wilkins to ~whereswaldon/arbor-dev

---
 go.mod | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/go.mod b/go.mod
index de9b27c..502da43 100644
--- a/go.mod
+++ b/go.mod
@@ -12,7 +12,7 @@ require (
	git.sr.ht/~whereswaldon/forest-go v0.0.0-20210610022432-d59588450728
	git.sr.ht/~whereswaldon/latest v0.0.0-20210304001450-aafd2a13a1bb
	git.sr.ht/~whereswaldon/sprout-go v0.0.0-20210408013049-fedf4ae2e7f8
	github.com/inkeliz/giohyperlink v0.0.0-20201127153708-cb2dff56ac99
	github.com/inkeliz/giohyperlink v0.0.0-20210728190223-81136d95d4bb
[message trimmed]

Deploy Scripts 2 years ago

From Daniel Wilkins to ~whereswaldon/arbor-infra

I'm logging off for the night but the first pass of the deploy is now
available at https://git.sr.ht/~tekk/arbor-infra
The basic workflow:
You make your changes in setup.go
If you need to copy config files, those will go in deploy/files

To test your changes or run a deploy, invoke the deploy.sh shell script
with the IP you want to set up.

The deploy script is more or less trivial. It does the following:
Has mage compile the magefile
Tars up the deploy directory
scps it to the remote server's root home
sshes into the server as root, untars, executes the magefile.

User Password Handling 2 years ago

From Daniel Wilkins to ~whereswaldon/arbor-infra

Working on the deploy scripts I ran into the first thing I want some
opinions on.
First: I figure it's easiest to just have a single admin user who
everyone on The List can log into.
Is anyone opposed to this?

Second: Given this, how do we want to handle sudo?
Does the admin user (who can only be logged in via ssh key) have
passwordless sudo access or should we have a shared password we just
keep secret?

Re: [Arbor Infra SIG] Proposal regarding LXD 2 years ago

From Daniel Wilkins to ~whereswaldon/arbor-infra

Y'all do whatever you think is best, just tell me what I need to do to
support it. I finally have some motivation and time tonight so
arbor-infra ought to get a push or two.

Danny

Josh Whetton wrote:
> It's more important to get _something_ over nothing. We can revisit
> the topic at a later date or when we find we actually need some of the
> features that LXD provides. Thanks for trying to work through the LXD
> stuff!
>
> J
>

Unattended Upgrade Opinions 2 years ago

From Daniel Wilkins to ~whereswaldon/arbor-infra

Hey all,

Since (per the meeting notes) we're doing LXD for the actual runtimes
and we want unattended upgrades, I looked into it a bit. I think that
we may not want to do live-patching after all because it quite
literally prevents us from scaling (3 servers are free, from the 4th
it's $225 per year per server.)

Outside of this it seems like the path for automatic kernel upgrades is
to generate our own patch files and apply them manually through our
automation.


...in light of this and since we intend to be tolerant of a single dead

[PATCH] Break multi-paragraph messages into multiple replies. 2 years ago

From Daniel Wilkins to ~whereswaldon/arbor-dev

---
 reply-view.go | 47 ++++++++++++++++++++++++++---------------------
 1 file changed, 26 insertions(+), 21 deletions(-)

diff --git a/reply-view.go b/reply-view.go
index 6a675d9..41bfac0 100644
--- a/reply-view.go
+++ b/reply-view.go
@@ -305,13 +305,13 @@ func (c *ReplyListView) startReply() {
}

func (c *ReplyListView) sendReply() {
	var newReply *forest.Reply
	var newReplies []*forest.Reply
[message trimmed]

Re: [PATCH] Automatically split paragraphs 2 years ago

From Daniel Wilkins to ~whereswaldon/arbor-dev

On Tue, Sep 22, 2020 at 08:34:19AM -0400, Chris Waldon wrote:
> Hey Danny,
>
> This patch only applies with `patch` (not `git apply`) because completely
> empty lines in the diff have no leading space in the "gutter" to indicate
> that there was no change on that line. Did you generate this with `diff`?
No, it was generated with git diff. That was just to work around my
workflow being bad and not email friendly (which I'm planning on fixing.)

Basically I'm used to merging, which is all well and good at work but when
I'm sending patches via email it results in all of the merged patches
getting included in git-send-email, hence my need to use git diff for this
one.

[PATCH] Automatically split paragraphs 2 years ago

From Daniel Wilkins to ~whereswaldon/arbor-dev

Alright, let's see if this patch works.
Had to generate it manually, hoping it applies cleanly