Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • May 30 2018 00:22

    wekempf on develop

    Switch to InvokeBuild, add unit… (compare)

  • May 28 2018 20:21

    wekempf on develop

    Fixing pester tests. (compare)

  • Sep 12 2017 13:55

    wekempf on develop

    WIP (compare)

  • Sep 12 2017 13:33

    wekempf on develop

    WIP (compare)

  • Sep 12 2017 13:31

    wekempf on develop

    WIP (compare)

  • Sep 08 2017 15:41

    wekempf on develop

    Simplify New-Blog cmdlet usage WIP WIP and 1 more (compare)

  • Jan 23 2017 15:04
    wekempf closed #2
  • Jan 23 2017 01:53

    wekempf on develop

    Add Publish-BlogDraft (compare)

  • Jan 22 2017 13:14

    wekempf on develop

    Make Get-BlogPost work with Ite… (compare)

  • Jan 20 2017 19:17

    wekempf on develop

    Implement Get-Blog Move module files into PoshWyam… (compare)

  • Jan 19 2017 22:57

    wekempf on develop

    Add Invoke-Wyam (compare)

  • Jan 19 2017 21:25
    wekempf closed #3
  • Jan 19 2017 21:12

    wekempf on develop

    Add Get-BlogPost and Get-BlogPo… (compare)

  • Jan 19 2017 21:07
    wekempf closed #4
  • Jan 19 2017 21:07

    wekempf on develop

    Add Get-WyamRoot This closes #… (compare)

  • Jan 19 2017 21:03

    wekempf on develop

    Add New-BlogPost This closes #… (compare)

  • Jan 19 2017 21:03
    wekempf closed #5
  • Jan 19 2017 20:57
    wekempf closed #1
  • Jan 19 2017 20:54

    wekempf on develop

    Add module manifest and module … Add New-Blog Fixes #1. (compare)

  • Jan 19 2017 20:32
    wekempf edited #1
William Kempf
@wekempf
What I want is for it to work without installing anything. The Cake bootstrapper helps here. With a default cake script we'll get everything installed that's necessary just by running the build. The only thing the cmdlet needs to do is generate the initial files and create the directory structures.
Thoughts?
Dave Glick
@daveaglick
@wekempf You're asking the wrong person about wordiness - I've been told I'm far too verbose for my own good :pencil:
That said, I appreciate detail oriented content for myself if nothing else - you never know when you're going to forget that one little important detail
William Kempf
@wekempf
@daveaglick I don't have write access to the repo?
Dave Glick
@daveaglick
You should - lemme check, the GitHub permission scheme has gotten kind of complicated...
Ahh - you have an outstanding invitation to join the org, need to accept that first
@wekempf If you're missing the invitation, it says you can also just go straight to https://github.com/Wyamio
William Kempf
@wekempf
OK, that mostly worked. What I don't have access to is the project settings. Can you make develop the default branch?
Dave Glick
@daveaglick
Yep! And also just made you guys admins on the repo, hopefully that gives you full access to everything
William Kempf
@wekempf
@daveaglick Great. Thanks. I just made several commits, and unfortunately in my zeal to learn GitHup commit message fu, I closed out some issues that I should have just associated to. I'll work on that later.
So, I've got the skeletons of most of the commands I could think of here, and some of them are even implemented.
In particular, New-Blog scaffolds a blog project. This differs slightly from wyam new in that it includes Cake build scripts and creates a project that's ready to go without needing to install any other applications.
@gep13 I've just used my own Cake script here, but I'd love to see you "fix" it with some of the ideas you had in Wyam.Recipe.
I'm thinking we want to support Git in this workflow, but we won't actually make it a Git repo by default. Allow the user to do that. This means the Cake script should do the git publishing stuff optionally somehow.
Gary Ewan Park
@gep13
@wekempf I can certainly try to add something here. The way that my Cake script works is to use Kudu to synchronise the output folder with a branch of a Git repository, so in theory, it could be used to publish to any repository, be it GitHub, Bitbucket, etc. It would be good for Cake.Wyam.Recipe (assuming that is what we call it) to support publishing to Netlify as well
William Kempf
@wekempf
Yeah, it would be great if we could get publishing to work pretty much anywhere, but tackling those that we use personally first makes sense. So Pages and Netlify?
Gary Ewan Park
@gep13
@wekempf for commit messages, I typically use (GH-1) that way issues aren't automatically closed, but are linked to commits
That makes sense to me
William Kempf
@wekempf
Thanks. I've used GH a lot as a lone developer, but this will be my first on a team, so details like this I have to learn.
Gary Ewan Park
@gep13
@daveaglick what are your thoughts? Should Cake.Wyam.Recipe be a thing? i.e. a collection of re-usable scripts specifically for building Wyam projects with Cake?
William Kempf
@wekempf
For Get-Blog I'm going to have to parse the front matter. Not sure how I want to go about that. I could take the cheap way out and "hand parse" only what we care about. Or I could use powershell-yaml from PSGallery (and have to figure out how to deal with module dependencies when using PSGallery). Final option would be to use the same .NET library that Wyam uses, though dependency management there could be fun as well.
I'm leaning towards using the same library Wyam uses, just in case there's differences in parsing. Thoughts?
Along the thought of dependencies, I've considered adding an Invoke-Wyam cmdlet. The purpose would be to bootstrap the tools in the same way the cake script does, so nothing needs to be installed. Not exactly sure how I'd bootstrap that, though. Obviously using NuGet.exe, but I'm not sure what details about that I need to consider so that this cmdlet and Cake do the same thing?
William Kempf
@wekempf
If I can bootstrap Wyam in, I could actually use Wyam code directly to obtain the front matter (that is, once I figure out what C# code from Wyam to use to do that).
Dave Glick
@daveaglick
@gep13 Sure! I find myself essentially reusing the same build script recently, so having a standard one that everyone can use sounds great.
Gary Ewan Park
@gep13
@daveaglick so, another repo in the Org? Or how would you like to handle this?
Dave Glick
@daveaglick
@wekempf Wyam uses YamlDotNet and is a pretty thin wrapper. Replicating that shouldn't be too hard.
Bigger question might be splitting the front matter to treat as YAML from the rest of a file in the same way Wyam does - --- is the convention, but it'll actually split on shorter sets of dashes and can optionally have a set of dashes on top too
The code that does the splitting lives here - if it would be helpful we could generalize it and place it somewhere like Wyam.Common
@gep13 Would it be appropriate to put in under the normal Cake.Recipe repo? I.e., that becomes a spot not just for the "main" Cake.Recipe but for other convention-based common build scripts as well
I imagine there are other cases like this where a common build script may be warranted, but it's niche enough that it shouldn't be part of the main Cake.Recipe
Gary Ewan Park
@gep13
@daveaglick yeah, you might be right. Let me have a think about it
William Kempf
@wekempf
@daveaglick Yes, having a method to call to return the yaml front matter would be helpful. Just to ensure the scripts do exactly the same parsing that Wyam does.
William Kempf
@wekempf
OK, I checked in an Invoke-Wyam cmdlet. It's preliminary, but seems to work correctly. This "bootstraps" in Wyam if it's not there in tools yet.
I could leverage a new method in Wyam.Common.dll by loading the assembly from there, which would work nicely. One issue I thought of, though, is that once loaded if you switch to another project I can't reload the DLL from it's location. I don't think that will be a problem, but it is something to consider.
William Kempf
@wekempf
@/all So, while it's not production ready just yet, all of the cmdlets I though about adding have been added and implemented. Good time for people to take it for a spin and provide feedback. What doesn't work as you expect it to, what functionality do you think is missing, etc.
Next step after fixing bugs/adding what people think is missing is to polish the documentation, including an about_PoshWyam document and then we should be ready to push to the PowerShell Gallery.
BTW, on the front matter, I decided to hand parse for now.
William Kempf
@wekempf
No internet, I'm at my son's Rubik's cube competition, but I've created a publish-blogdraft cmdlet and improved piping support. I think it's coming along nicely for three days effort.
Gary Ewan Park
@gep13
@wekempf great work! I haven't had a chance to look at this yet, been working on a few other things, but I will take a look when I can.
William Kempf
@wekempf
Yeah I've seen the activity elsewhere. Cool annoucement about @daveglick and the cake website.
Gary Ewan Park
@gep13
@wekempf yup, it really is great news! @daveaglick has done a lot of work for us, and it is a testimony to how flexible and configurable Wyam is
Dave Glick
@daveaglick
@wekempf Nice! I'm not a big PowerShell user so probably won't have much feedback there, but I'll be happy to take the cmdlets for a spin
William Kempf
@wekempf
@/all Just published http://www.digitaltapestry.net/posts/poshwyam. Hoping to get a bit more visibility and usage so we can polish things up before publishing to PowerShell Gallery.
Dave Glick
@daveaglick
Great, nice work - I'll Tweet this out tomorrow to try and get some eyeballs
Jamie Phillips
@phillipsj
Nice I will start giving it a try
Mordechai Zuber
@M-Zuber
Tweeted that out
Gary Ewan Park
@gep13
@wekempf this is definitely on my radar to take a look at