Version 1 Alpha 1

[stuyam]

1.0.0.alpha1 was just released. RubyGem can be found here and new setup guide here Setup as well as a What's New Section.

There are new docs for the alpha that are still being polished and adding more content: https://v1.bootstrapemail.com. Any feedback there is also welcome.

There is a new CLI and vanilla ruby implementation that can be used which no longer requires Rails to be the sole way to use Bootstrap Email!

Drop any feedback here on this first alpha release 🙌

[ComtelJeremy]

Hi @stuyam, this is great news! We will start trying it out in our pipeline shortly. Will keep you posted.

[stuyam]

Just released a new version 1.0.0.alpha1.1, try to reinstall and try again! 🙏 https://rubygems.org/gems/bootstrap-email/versions/1.0.0.alpha1.1

[ComtelJeremy]

Progress... Runs, but I get this now (seems like the path is building funny)...

Traceback (most recent call last):
        7: from C:/Ruby27-x64/bin/bootstrap-email:23:in `<main>'
        6: from C:/Ruby27-x64/bin/bootstrap-email:23:in `load'
        5: from C:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/bootstrap-email-1.0.0.alpha1.1/bin/bootstrap-email:2:in `<top (required)>'
        4: from C:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/bootstrap-email-1.0.0.alpha1.1/bin/bootstrap-email:2:in `require_relative'
        3: from C:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/bootstrap-email-1.0.0.alpha1.1/lib/bootstrap-email/bootstrap_email_cli.rb:84:in `<top (required)>'
        2: from C:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/bootstrap-email-1.0.0.alpha1.1/lib/bootstrap-email/bootstrap_email_cli.rb:84:in `new'
        1: from C:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/bootstrap-email-1.0.0.alpha1.1/lib/bootstrap-email/compiler.rb:14:in `initialize'
C:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/bootstrap-email-1.0.0.alpha1.1/lib/bootstrap-email/compiler.rb:14:in `read': Invalid argument @ rb_sysopen - C:/Users/USER/Downloads/C:/Users/USER/Downloads/SimpleValidationEmail.html (Errno::EINVAL)

You'll notice the root path (I am running the CMD window at C:/Users/USER/Downloads) is being repeated?

[ComtelJeremy]

I am on Windows 10, if that matters.

[ComtelJeremy]

If I run it with no arguments and do the entire folder, it works! Perhaps there is an issue somewhere here:

bootstrap-email/lib/bootstrap-email/bootstrap_email_cli.rb

Line 83 in 2ed9419

path = File.expand_path(input, Dir.pwd)

where the path is combined, or something like that?

I am unable to run it specifying a file or path, or output file. I'll try some of the other switches as I have time.

[stuyam]

Off to a bumpy start but this is all super valuable thank you. You are right about that line, it was basically doubling up on the working directory path. I added some more tests to also cover more CLI use cases pointed out here so that is great! Just pushed a new release 1.0.0.alpha1.2, want to make sure the core things are working 👍

[ComtelJeremy]

Also, a question... for the pattern option, can we specify a relative path for the destination... for example:
emails/* with the destination emails/compiled/* (if you catch my meaning)?
I do think we might need an option to rename the outputted file (as we might want it in the original folder with a new name - for example with a suffix). I imagine we could do this with a Powershell script, or something, or maybe a Ruby script? Just starting to figure out how to work this into a build step.

[stuyam]

The path and destination example you described here should already work. Though it would be bootstrap-email -p 'emails/*' -d 'emails/compiled' but I did in the latest release at the ability to use the /* at the end like bootstrap-email -p 'emails/*' -d 'emails/compiled/*' even though it does the same thing.

Question on naming, do you like /output for the default or do you prefer /compiled? I have gone back and forth.

[ComtelJeremy]

Just an update for you, @stuyam ...

We have successfully joined your CLI with a bash script in our build step. 🚀 We now compile all our templates and upload them to our storage container when we push our branches in git... works good so far. Therefore, no bootstrap-email-ified ™ templates in the repo, so we don't have to manage versions, but everything is bootstrap-email-ified ™ and pushed to our server in a build step.

It's very nice!

We will let you know when it hits production and we have a chance to fully test the templates with live emails (we have some other infrastructure work to do first).

I think we would be willing to share our bash script and some basic details on how we got it running for others who use this library, as time allows.