2018-12-14 16:16:16 algitbot: ping 2018-12-14 16:16:38 thats better 2018-12-14 16:17:57 <_ikke_> .ping 2018-12-14 16:18:00 <_ikke_> .uptime 2018-12-14 16:18:00 I've been sitting here for 11 days, 4:54:28 and I keep going! 2018-12-14 16:20:13 http://dev.alpinelinux.org/irclogs/%23alpine-docs-2018-12.log 2018-12-14 16:20:52 <_ikke_> I did see two pongs 2018-12-14 16:21:17 yes, first one was ending in a blackhole 2018-12-14 16:21:40 <_ikke_> http://tpaste.us/5wV9 2018-12-14 16:21:42 i added the logging function without call it :) 2018-12-14 16:22:23 _ikke_, i added logging so it ends up on irclogs dir 2018-12-14 16:22:30 <_ikke_> ok 2018-12-16 00:31:59 ping ncopa - is it ok if I recommend using GNU Parted for manual partitioning? 2018-12-16 00:32:40 IME it's the easiest one to explain, and it's useful both interactively and in scripts (rather than being hyper specialized, as the fdisk | sfdisk separation (and also handles mbr + gpt unlike busybox fdisk)) 2018-12-16 00:32:48 the expectation is that the user already has networking and repos by that point 2018-12-17 04:24:53 decided to go on with it, mostly because the worst case scenario is just *that* specific section needing a rewrite 2018-12-17 10:29:26 SpaceToast: ok with me. if someone disagrees he/she can always send a PR 2018-12-17 11:36:59 SpaceToast: busybox fdisk is the default partitioner on alpine, i had been using that 2018-12-17 11:37:48 AinNero: busybox fdisk cannot handle gpt partitions, and cannot be appropriately used non-interactively (requires stdin trickery) 2018-12-17 11:38:11 setup-alpine (or, rather, setup-disk) uses sfdisk, which can handle gpt partitions, but is really not all that great for non-script usage 2018-12-17 11:38:35 uhm, i dont consider the stdin part trickery, but nice design 2018-12-17 11:39:06 but yeah on GPT 2018-12-17 11:39:07 because inserting hardcoded '\n's to get through interactive confirmation prompts is nice design? 2018-12-17 11:39:25 look: https://github.com/nero/apkovl/blob/master/utils/setup-rpi.sh#L32 2018-12-17 11:40:45 in parted, this looks like so: parted $device -> (either prefix everything with that or do it interactively) "mklabel msdos", "mkpart 1 1 128M", "set 1 boot" 2018-12-17 11:41:13 hm 2018-12-17 11:41:24 the GPT support should be reason enough 2018-12-17 11:41:32 :) 2018-12-17 11:41:54 thing is, interactive "sessions" are difficult to properly convey in documentation 2018-12-17 11:42:13 so being able to convey things non-interactively is important, and having them be compatible with the interactive approach moreso 2018-12-17 11:42:26 and erm... putting the above in docs is guaranteed to cause confusion 2018-12-20 03:30:09 ping - this is just to announce that the latest snapshot is mostly done in terms of content 2018-12-20 03:30:30 I'm going to be making a few quick passes for quality control, start commiting and pushing everything present to build it 2018-12-20 03:30:36 try to figure out what to do regarding the UI 2018-12-20 03:30:48 and then it should be ready for an initial (WIP) publish :D 2018-12-20 03:31:19 (maybe beta.docs.a.o? I don't want users to think it's entirely ready quite yet, but other methods may be ok) 2018-12-20 05:36:56 <_ikke_> SpaceToast: didn't check the content yet, but looks nice 2018-12-20 05:37:30 I'm not particularly happy with the content, but I was asked (and promised) to get the bare minimum acceptable out the gate asap 2018-12-20 05:37:54 re: looks - UI is fully customizable (and we'll need to do that - the top bar is obviously not acceptable in its current state) 2018-12-20 08:28:51 we could also publish it on the vpn only initially 2018-12-20 08:29:02 good idea with beta.docs.a.o. i like that 2018-12-20 08:29:03 <_ikke_> The beta one 2018-12-20 08:29:06 <_ikke_> right 2018-12-21 23:51:35 ping clandmeter - I think I have a "bare minimum" deployable now, for beta.docs.a.o 2018-12-21 23:52:08 the UI is still the default prototyping one, and it's looking like it might be a while before we have anything (I'd need someone else to work on it, or to take a significant break from writing the docs proper to make it, which I'd rather not do) 2018-12-21 23:52:43 so it should stay on beta.docs.a.o until that's done (and ideally the user handbook, as a minimum, is fully done (aka the "Working With" section, and everything is fully style-verified, corrected, so on)) 2018-12-21 23:53:43 please poke me if/when you wanna do that, so we can figure out how to handle updates etc 2018-12-22 09:17:09 olla 2018-12-22 09:18:27 SpaceToast, if you want we can create a dedicated repo for it. 2018-12-22 09:18:39 this way we can monitor updates via mqtt 2018-12-22 14:04:25 moin 2018-12-22 14:04:41 clandmeter: sure, though it'll be several repos (due to how it works :) ) 2018-12-22 14:05:02 so right now it'd be docs/user-handbook and docs/docs.a.o then 2018-12-22 15:06:00 Are they on github? 2018-12-22 15:06:10 yes, but prefixed with alpine- right no 2018-12-22 15:06:17 (just to keep my namespace clean) 2018-12-22 15:06:40 I'll create a docs prefix 2018-12-22 15:06:53 I mean directory 2018-12-22 15:07:30 yeah, I get it 2018-12-22 15:07:42 I've used gitolite before :) (though I don't really like it, it's fine) 2018-12-22 15:16:02 I'll try to fix it later 2018-12-22 15:16:28 Currently in a bar :) 2018-12-22 15:16:41 : ) no worries, I'm just waking up 2018-12-22 15:16:49 ping when you're back home and we'll get the whole thing set up eh? 2018-12-22 15:17:13 re: gitolite - it's one of the reasons I'm semi in-favor of moving to self-hosted gitlab / sr.ht (so on) 2018-12-22 15:17:35 but I'm not so daft as to make demands because I have preferences ^^;; 2018-12-22 15:24:15 <_ikke_> SpaceToast: I can probably also assist in setting something up 2018-12-22 15:24:46 _ikke_: it's mostly just a matter of access, but there's no rush or anything :) 2018-12-22 15:27:35 <_ikke_> I don't have access to configure git, but I can setup a container to publish the site 2018-12-22 15:28:09 ok, basically anything running alpine will do 2018-12-22 15:28:21 all that's really needed is yarn (/npm but yarn is preferred) and git 2018-12-22 15:28:47 (and obviously an httpd, a light one will do since, as I understand, we do TLS through a reverse proxy) 2018-12-22 15:29:54 <_ikke_> correct 2018-12-22 15:30:13 I was planning on providing a Dockerfile in the playbook repo, but I decided to wait on that until antora 2.0 is released proper 2018-12-22 15:30:44 <_ikke_> We don't have a lot of infrastructure for hosting docker atm 2018-12-22 15:31:03 I understand, I was just mentioning that the consideration took place 2018-12-22 15:40:30 _ikke_, there is already a container 2018-12-22 15:55:43 <_ikke_> clandmeter: alright 2018-12-22 16:26:35 SpaceToast, which key would you like to use on git.a.o? 2018-12-22 16:26:47 can i reuse your github one? 2018-12-22 16:27:04 clandmeter: http://sprunge.us/tizzb1 - here is my current list of keys 2018-12-22 17:18:32 SpaceToast, can you try to push things to git@git.alpinelinux.org:docs/ 2018-12-22 17:19:49 clandmeter: looks like it worked, supposedly initialized in /var/lib/git/repositories/docs/user-handbook.git/ 2018-12-22 17:20:06 not showing up on cgit yet though 2018-12-22 17:20:34 no that needs manual config 2018-12-22 17:20:42 ah ok 2018-12-22 17:21:08 well, cloning works too 2018-12-22 17:21:35 let me patch out the playbook and get that in there too 2018-12-22 17:22:21 can you give me a repo desc?\ 2018-12-22 17:23:02 clandmeter: "Antora component for the Alpine Linux User Handbook." 2018-12-22 17:23:06 (or variations thereof) 2018-12-22 17:25:02 ok, git@git.alpinelinux.org:docs/docs.a.o is up as well - "Antora playbook for docs.alpinelinux.org" 2018-12-22 18:36:17 clandmeter: any updates on docs.a.o visibility on cgit and beta.docs.a.o (DNS etc)? 2018-12-22 18:39:37 <_ikke_> SpaceToast: https://git.alpinelinux.org/cgit/docs/docs.a.o/ 2018-12-22 18:39:48 <_ikke_> https://git.alpinelinux.org/cgit/docs/user-handbook/ 2018-12-22 18:39:54 Oh I see that, but it's not under Docs/ in https://git.alpinelinux.org/ yet 2018-12-22 18:40:04 (that's why I only asked about the former, and not the latter :) ) 2018-12-22 18:40:07 <_ikke_> The last one is 2018-12-22 18:40:15 yes, and has been for a while 2018-12-22 18:40:22 which is why I asked about updates regarding the *former* 2018-12-22 18:40:42 <_ikke_> 3k 2018-12-22 18:42:26 ? 2018-12-22 18:43:56 <_ikke_> ok* 2018-12-22 18:44:12 ah 2018-12-22 22:29:31 SpaceToast, fixed 2018-12-22 22:29:54 clandmeter: ty :) 2018-12-22 22:30:00 now, wanna put it up on beta.docs.a.o? 2018-12-22 22:30:17 (the instructions for doing it should be in the docs.a.o repo, or I can do it relatively quickly) 2018-12-22 22:47:20 oh, we do want @beta versions though (it's in rc2 and stable, just means no erm... questionable git bindings) 2018-12-23 08:38:36 SpaceToast, its running now internally, i need to generate a separate LE cert to add it to our www proxy (doesnt fit our wldcard cert). 2018-12-23 08:38:42 ill do that a little later. 2018-12-23 08:38:54 or else tomorrow. 2018-12-23 11:55:01 ok 2018-12-23 11:55:03 :) 2018-12-23 18:54:39 SpaceToast, nodegit is PITA. maybe we should add some info on the readme to help others to get antora working? 2018-12-23 18:55:49 P.S. Having the readme in md will make cgit display it. 2018-12-23 21:09:10 clandmeter: you need to use the @beta version 2018-12-23 21:09:18 they migrated off nodegit to isomorphic git 2018-12-23 21:09:27 that'd be the reason why :) 2018-12-23 21:09:40 and ok, I'll move/rewrite the READMEs into md later 2018-12-23 21:09:54 (sorry about delay, I keep passing out today) 2018-12-23 21:12:18 ah, looks like the @beta tag was removed, but the current version is 2.0.0-rc.2 (and it'll soon just be plain 2.0.0) 2018-12-23 21:13:36 so it'll be `yarn global add @antora/cli@2.0.0-rc.2 @antora/site-generator-default@2.0.0-rc.2` with an upgrade cycle once that stabilizes 2018-12-23 23:32:35 SpaceToast, this seems even more problematic :| 2018-12-23 23:32:47 how so? 2018-12-23 23:34:27 ah, found the issue - let me just change that to use https 2018-12-23 23:35:58 and with http it's just "plain" http 2018-12-23 23:36:31 its not that simple :| 2018-12-23 23:37:11 Remote does not support the "smart" HTTP protocol, and isomorphic-git does not support the "dumb" HTTP protocol, so they are incompatible 2018-12-23 23:37:23 yes, that's... what I just said 2018-12-23 23:37:35 "plain" here being ~= "dumb" 2018-12-23 23:38:03 as a temporary workaround we can use "author mode" (site-workspace), but this clearly needs to be addressed 2018-12-23 23:38:43 so it doesnt support git urls? 2018-12-23 23:38:52 i couldnt find any information about it 2018-12-23 23:39:00 it doesn't seem to, I'm asking them right now 2018-12-23 23:42:57 it might be possible to use author mode as a workaround until we have an infra change (it's being discussed relatively often, and I believe all 3 options (gitlab, github, sr.ht) support "smart" https), but I'm submitting a bug report to isomorphic-git right now 2018-12-23 23:44:04 dont expect us to change our git infra anytime soon. 2018-12-23 23:44:40 we do mirror our repo's on github, so that could be an alternative. 2018-12-23 23:45:15 mhm, could do that, yeah 2018-12-23 23:45:27 currently they are not yet mirrored 2018-12-23 23:45:48 the person who managed that is not around much anymore. 2018-12-23 23:46:19 i need to probalby move that back to our own infra. 2018-12-23 23:46:35 https://github.com/isomorphic-git/isomorphic-git/issues/665 2018-12-23 23:47:30 i think we can also look into adding smart support to git.a.o 2018-12-23 23:47:54 I'm not really sure what that would involve, so please do :) (but I won't be much help) 2018-12-23 23:48:48 its just a matter of finding time. 2018-12-23 23:49:00 which is what is missing atm :) 2018-12-23 23:49:25 clandmeter: anyway, in the meanwhile (if we're in a hurry), we can use author mode - inside of `docs.a.o`, do the following: `mkdir workspace; git clone git://git.alpinelinux.org/docs/user-handbook workspace/user-handbook; antora site-workspace.yml --your-other-flags` 2018-12-23 23:49:29 I can tell ;) 2018-12-23 23:49:36 once 3.9 is out hopefully things calm down a bit :) 2018-12-23 23:50:03 clandmeter: alternatively, I can host everything on my own infra, and you can set beta.docs.a.o to just redirect there, if you'd like 2018-12-23 23:51:30 (actually, I should probably host it anyway, so let me do that real quick) 2018-12-23 23:54:27 ok its up now 2018-12-23 23:54:43 https://beta.docs.alpinelinux.org 2018-12-23 23:54:46 :) ty 2018-12-23 23:54:54 is mqtt set up? 2018-12-23 23:55:09 not yet 2018-12-23 23:55:13 ok 2018-12-23 23:55:24 ill add it to cron for now. 2018-12-23 23:55:27 i need to go to bed. 2018-12-23 23:55:31 good night then 2018-12-23 23:57:56 ok for now it will run every 15 min to update 2018-12-23 23:58:33 ones we fix git we can hook up mqtt. 2018-12-24 00:01:09 ok sounds good 2018-12-24 00:01:17 I'll get back to actually writing the other 90% of the docs now :D 2018-12-24 00:56:43 antora's stance is that they support what isomorphic-git supports; isomorphic-git wants to support everything that git(1) supports, though, which I'll try and remind them of 2018-12-24 09:56:29 great job with beta.docs.a.o! 2018-12-24 22:30:15 ncopa: tyty, currently working on the next section of the user stuff - working with alpine, any idea who I can ask for details re: apk internals? (e.g what "search" actually is capable of looking up, etc (I know it can look up binaries, for example)) 2018-12-25 09:13:21 you can ask either me or fabled 2018-12-26 14:21:42 clandmeter: just as a reference, antora 2.0.0 (stable) is now out 2018-12-26 15:13:22 interestingly, the official docker image for antora uses alpine 2018-12-26 15:14:32 ncopa: yes, that's their primary official platform 2018-12-26 15:14:46 they also test on ubuntu and co, but alpine is a 1st class target 2018-12-27 16:05:14 SpaceToast: have you started writing the actual man pages for the different apk files and tools? 2018-12-27 16:05:35 no, that's the last step (after user and developer guides) 2018-12-27 16:05:49 user guide is currently coming along relatively well though 2018-12-27 16:05:59 all right, just checking 2018-12-27 16:06:02 ideally I'd like to start the developer guide soon after 3.9 is out (but not before) 2018-12-27 16:06:08 is there any specific reason you're asking? 2018-12-27 16:13:04 i'm going to convert some personal notes on apk to asciidoc form and make a branch for it 2018-12-27 16:14:15 danieli: I'm about to start writing the general "usage guide" for apk (not a man page, that's later), so if you could do send it here later :) 2018-12-27 16:14:50 I'm purely writing a man page, nothing else 2018-12-27 16:15:03 that's still helpful~ 2018-12-27 16:16:14 danieli: also, here's a reference for how to make your asciidoc document compatible with both web rendering and troff conversion: https://asciidoctor.org/docs/user-manual/#man-pages