Just finished reading the third Murderbot Diaries "book" (in quotes because it's a short story, but charged at (high) full book prices), and it was as consistently good as the first couple
I've been thinking about showing dates as year-day of year, but I'm not sure. I've just had a "
I think it's about showing how far through the year it is. I'll think about that as a separate page, although getting fp ported over is current priority.
If I remember right, I've pulled webmail out into its own project, integrated the shared stuff from common and webmail.content. Time to fire it up and see what's broken.
I'll need to pull a copy of the db from legacy and setup a spare domain for testing.
The more i think about this blog thing, the more I want to stick it into a database and stop messing about. The "keep it in files so that I can recover it for next time" stuff is interesting, and i should probably add an export function, but if I use sqlite i should be able to do a dump anyway.
Actually, that export data idea sounds better every time I think about it, especially after having got data exports from a bunch of different places (Amazon, Netflix, Facebook, Twitter) this week.
However. Today is about webmail, and getting out of Bytemark.
wepiu has the basics installed, but not configured. It's got a vmail user with a nearly empty home dir. It's also got a webmail user, I guess I'm planning on using that one for the webmail?
Ok, so webmail doesn't build. Last time I'd been deleting "stuff I don't need anymore", and I've been a bit over the top. Or possibly not deleted enough. Looks like some of the 'Friends' stuff is still hanging about.
find . -type f -name "*.cs" -exec sed -i 's/using Common/using Webmail/' {} \;
Who says you need an ide!
(Having said that, there are times when they're useful)
Whoop! It starts!
(Yeah, yeah, SQL errors, I'm on it.)
Bash arrays
arr=() Create an empty array
arr=(1 2 3) Initialize array
${arr[2]} Retrieve third element
${arr[@]} Retrieve all elements
${!arr[@]} Retrieve array indices
${#arr[@]} Calculate array size
arr[0]=3 Overwrite 1st element
arr+=(4) Append value(s)
str=$(ls) Save ls output as a string
arr=( $(ls) ) Save ls output as an array of files
${arr[@]:s:n} Retrieve n elements starting at index s
Note: JavaScript doesn't have a native day of the year function, so I'd have to write one (based on the number of days in the month code above) if I wanted to do anything client side.
(Alright, I'm wrong. Subtract midnight 1st Jan from your date to get ms since the start of the year and divide by (1000*60*60*24) to get days)
Incomplete idea
New webmail idea: Save inbound emails as parsed html as they come in. have a background thread (per user) that's connected and listening for emails.
Listening per user isn't fantastically efficient, but since it's only the two of us if should be fine.
(on a larger scale I'd probably have something on the end of a pipe, but I'm going to ignore that for now)
What do I need to save?
- Headers (At least from, to, date, subject, maybe type)
- Structure (From a template based on the content type. Recursive for multiparts)
- Content (The body and it's various parts)
- The original message (so I can see the 'raw' version)
Assuming all this stuff is going to also be saved by the mail system, I don't need to be able to round trip it. Folders need to be updated on change.
I should check the stats, but my feeling is that it's probably not worth it. A good chunk of mail is never opened (See: spam management), and updating folders leads to irritating locking issues (that dovecot also has but has already dealt with).
It's a cute idea, but unfortunately not worth it.