Add ws command line interface.

[zw963]

This commit including following changes:

1. Add src/ws.cr, it used to build ws command, it not required by default.
2. Add a new github action, when we are release a new version use git tag, it will built a packed version alpine static binary which can be download directly on release page, we probably should support download macOS version, but i need investigate how to do it, because i never use Mac.
3. some Improvement.

Code probably still optimizing, but it works!

[jwoertink]

Just a few small suggestions, but this looks great! Thank you.

[zw963]

Hi, @jwoertink , i try improve banner usage for ws again, please help on check english. : )

And bump a new version to fix some error when pacakge and avoid flush ours discussion.

One more question:

I found when i add following code into shard.yml, the ws binary was not build when wordsmith
add as a lib dependency, and installed as shards install.

diff --git a/shard.yml b/shard.yml
index 014b24d..b7dd167 100644
--- a/shard.yml
+++ b/shard.yml
@@ -5,6 +5,10 @@ authors:
   - Paul Smith <paulcsmith0218@gmail.com>
   - Flinn Mueller <theflinnster@gmail.com>
 
+targets:
+  ws:
+    main: src/ws.cr
+
 crystal: ">= 1.4.0"

This is so wired, because i want to remove this diff because i thought ws will be build if i add a targets item into shard.yml.
But it seem like build ws never happen, but, i check https://github.com/luckyframework/avram/blob/main/shard.yml#L8-L10
it seem like works, i just want to confirm, if we want install any prebuild binary, we must add a postinstall item in shard.yml?

Thank you.

[jwoertink]

I've added a few new comments for the new updates.

[zw963]

I test the mac version ws precompile binary, it works.

For those tag, because i create tag v0.3.1 and v0.3.2 on my fork, should i remove those tag before merge?

[zw963]

I consider if the name of ws a litter shorter? though, i search on my Arch linux package manager with /usr/bin/ws with no result.

I don't know if there is a command told ws in mac anyway.

[jwoertink]

I searched apt and didn't see any ws programs, so we may be fine. As for the tags, I'm not sure how that works. If the merge carries them over, then yeah, they need to go away. I can't imagine that's the case though because I'd think that could lead to a security issue of people just making random tags in commits 😬

[zw963]

I searched apt and didn't see any ws programs, so we may be fine. As for the tags, I'm not sure how that works. If the merge carries them over, then yeah, they need to go away. I can't imagine that's the case though because I'd think that could lead to a security issue of people just making random tags in commits grimacing

I guess the tag should never be merged in a PR.

And for the tag, it means when maintainer create a new valid version tag like this: v0.0.3 which start with v, the builder workflow will create a binary, anyway, i consider we don't need build binary each when push code into base, right?

[jwoertink]

It looks good to me 👍 I guess we can just merge this in and give it a shot. Thanks for putting this together!