This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # announcements (1)
- # babashka (118)
- # beginners (108)
- # calva (20)
- # chlorine (3)
- # clara (10)
- # clj-kondo (47)
- # cljsrn (10)
- # clojure (144)
- # clojure-australia (5)
- # clojure-czech (2)
- # clojure-dev (11)
- # clojure-europe (94)
- # clojure-france (4)
- # clojure-nl (5)
- # clojure-spec (3)
- # clojure-sweden (2)
- # clojure-uk (11)
- # clojuredesign-podcast (5)
- # clojurescript (56)
- # cloverage (1)
- # code-reviews (6)
- # conjure (1)
- # cursive (13)
- # datascript (1)
- # datomic (16)
- # defnpodcast (1)
- # emacs (1)
- # etaoin (1)
- # events (7)
- # fulcro (21)
- # graalvm (3)
- # helix (17)
- # jackdaw (3)
- # jobs-discuss (2)
- # lambdaisland (2)
- # london-clojurians (2)
- # meander (2)
- # mid-cities-meetup (2)
- # midje (1)
- # off-topic (1)
- # pathom (3)
- # pedestal (12)
- # reagent (7)
- # reitit (15)
- # reveal (12)
- # shadow-cljs (6)
- # sql (14)
- # test-check (3)
- # vim (13)
I made bb fork that includes ring middleware and reitit routing functions. MS-Windows executable is provided. https://github.com/kloimhardt/bb-web#edit-with-parinfer-codemirror
Interesting! I would like to package it for scoop. Do you plan to have regular releases on Github?
My intention is not to add anything in the near future to my forked Babashka repository. The bb-web repository will be updated though. What would you need for making a scoop package?
Basically if you upload binary, output from appveyor) as zipped file as Github release, similar to what babashka is doing, it's already quite good.
I just published a release: https://github.com/kloimhardt/babashka/releases/tag/v0.2.2
I would suggest you to maintain the versions in sync. Under v0.2.2 there should be babashka-0.2.2-windows-amd64.zip Also I'll come with the something in scoop and we can tune it to a level it's convenient.
@U77MR6ETD I think it would maybe be good if you renamed the executable and zip archive to something that doesn't conflict with the "official" babashka
I‘ll take care of the naming and come back. thank you for the feedback. Any hints where to look to set the names as I need to figure out how to do that (tomorrow)
it would be nice to dodge also binary conflicts. Technically binary sits in it's own directory, but having
bb-web.exe would be nicer as well.
I can dodge this by setup shim in scoop, but still valid since, also users can just download, uncompress and copy to some PATH to use it side-by side with original babashka
This is how it may look like (draft PR) https://github.com/littleli/scoop-clojure/pull/117
@U77MR6ETD The zip has the name SNAPSHOT in it. Unpacking the zip, the binary is still called bb.exe, not bb-web.exe
it has the name SNAPSHOT, yes. But the contained exe, I insist, has the name bb-web.exe. Are you sure on this second point?
$ unzip babashka-0.2.3-SNAPSHOT-windows-amd64.zip Archive: babashka-0.2.3-SNAPSHOT-windows-amd64.zip inflating: bb.exe
Seems to work:
$ unzip babashka-web-0.2.3-SNAPSHOT-windows-amd64.zip Archive: babashka-web-0.2.3-SNAPSHOT-windows-amd64.zip inflating: bb-web.exe
Does it make sense to release this as bb-web <some other stable version> and not SNAPSHOT?
cool. Now point 1: is the name SNAPSHOT a big problem (I do not know a good way to get rid of it)
@U77MR6ETD These numbers are set in these files:
if you change them manually, these files will reflect that. Also
bb-web --version will print the correct version.
you could choose to only override these files in CI, just temporarily overwrite them there
I deleted the tag 0.2.2 locally and created a new one. Deleted the tag via GitHub gui as well. Still I could not push the tag 0.2.2 . So decided to go for 0.2.3 . But I am sure this can be fixed somehow and a 0.2.2 can be made, I just did not try hard enough. So lets leave that for now, I'll look again into it.
I don't see the tag anymore in your repo, so I'm puzzled why you're not able to push
I tried around a lot and just gave up somewhere in the middle, did not go all the way, that's why. Just said f* it, I go for 0.2.3
Can fix that, give me some time. But the SNAPSHOT name is still an issue. How to remove this SNAPSHOT out of the .zip file name?
understood, I just change the content of the file BABASHKA_VERSION (thought there is a more standard way somehow involving BABASHKA_RELEASED_VERSION)
ah, I see, thank you for the info. I get back to work on a next release attempt 🙂 thank you for the patience.
the efforts are mostly because bb-web is for folks like me who are not well versed in dev-ops things.
Now AppVayor obviously delays my builds because I made so many today or so... need to wait for that build.
@U77MR6ETD It starts a new build for every commit, so you might have to cancel those. There's a setting for automatically stopping running builds on a new commit
Will set that. But today I wanted a build for every single commit because I juggled around with tags and release versions and names. So the penalty is well deserved 🙂
you can see the history here: https://ci.appveyor.com/project/kloimhardt/babashka/history
@UBLU3FQRZ can you work with the lastest Babashka-web release or is anything missing?
@U77MR6ETD side question, what should be homepage of this project? should I use just github home?
PR with manifest: https://github.com/littleli/scoop-clojure/pull/117
I would change
A Clojure babushka for the grey areas of Bash into something which makes it clear that this is a fork
bb-web is a repository with examples for beginners. Let me think about all this naming, will come back.
@U77MR6ETD Idea: maintain a bb-web branch in your fork, with adapted README/examples etc.
and the master branch will be the original which can be used for merging upstream bb
@U04V15CAJ That is the right approach from a technical point of view. But the example repository (now called bb-web) should be a small thing with just one master branch, so there is no doubt what it is.
then maybe call your fork repo bb-web or babashka-web and your other one bb-web-examples
on the case. @UBLU3FQRZ will come back with a title and link to renamed git repository being the homepage.
@UBLU3FQRZ Homepage: https://github.com/kloimhardt/babashka-web/tree/bb-web Title: A babashka fork for small web-apps
@U77MR6ETD Github also allows you to set a default branch, so then you can leave out the /tree stuff
Note that your README says: Note: the relevant branch of this fork is guestbook2 which is a bit confusing
cleaned all up and set default branch. So the homepage is just https://github.com/kloimhardt/babashka-web
Should I replace the standard Babashka Readme.md in the bb-web branch or is this confusing?
ok, will do theses cosmetics later on. @UBLU3FQRZ Is there anything I need to do for scoop? Remember the homepage is just the GitHub page without the /tree stuff.
I think it's in good shape now. I did some adjustments to my draft, make it a proper PR. Check here: https://github.com/littleli/scoop-clojure/pull/117/files
I'm about to merge it. I need someone to actually test it, because I'm nowhere near my Windows box system. @U04V15CAJ 🙏 can I ask you to test it?
@UBLU3FQRZis it necessary to do
scoop bucket add java for successful
scoop install bb-web ?
just successfully installed bb-web with scoop. But I do not understand why I need to
scoop bucket add java and install openjdk for it. Is this necessary or just accidental?
It's optional. It's convenience for those who want to use scoop for both clojure (clj) and java installation
but still, just doing
scoop install git
scoop bucket add extras and
scoop install bb-web did not do the trick. Something was missing, and after I did all the other (not obviously related) scoop commands described in the Readme.md, it worked.
you mean, you installed other tools from the bucket and after that it started working?
if it's the case I think candidate for this are:
Yes, that is what I mean. I tried
scoop install joker before doing
scoop bucket add java and all following commands. Error message was "Couldn't find manifest for joker". Then I did bucket add 1)java+2)scoop-clojure and install 3)jdk+4)clojure, then joker and bb-web worked. One of those thing 1)-4) seem necessary, and I do not understand why.
yes, extras bucket and scoop-clojure needs to be added before issuing installation commands.
I see. The reason I wanted to know is of course to write instruction for installing bb-web with scoop. But maybe an update of the scoop readme would be useful.
I'll consider this as more and more tools are present and they maybe some useful without having even clojure installed. Which wasn't the initial purpose.
scoop install git would not work without git being installed in the first place?
I will also use git for my package manager: https://github.com/borkdude/glam it makes sense. brew does it too
I worked at the national tax service where they still used Office 97 because some scripts relied on that. It's best to stay away from those places.
now what I usually do is to "watch releases only" on Github and once a new release is out, I run a script with version and generate a manifest for it.