If you think I can provide some helpful contribution, do not hesitate. I think you know some of my skills.
But it was part of a large redesign, I wanted to get rid of a few hotspots of complexity, and make the code more elegant.
That feature fit right into this work.
Thanks for your offer, I will definitely get back to you once there is something worthwhile to show.
this time I have a use-case to use freckelize ; we use a small python library that allow to write launcher for our ansible / sphinx projects. This library install needed virtualenv and provide custom launchers (with click) for our tasks (basically automatically add ANSIBLE_CONFIG environment, bind custom command line arguments to ansible extra vars, deploy documentation after sphinx build, ...). First I want to replace my bootstrap.sh by a freckelize prerequisite ; then I'll see if I rework virtualenv install part to use freckelize or if I keep this in my library
It'll be possible to use the same frecklecutables in both frecklecute as well as freckelize. So, you could for example write custom frecklecutables to do the sphinx build, deploy the docs, do the testing. A dev could run those separately. And you can re-use them in a custom freckelize adapter for your project type.
Kinda hard to explain without code examples, but I'll ping you as soon as I have something. If you want, you could write up your use-case in a bit more detail. Would be helpful for me to understand and think about how/whether it's a good fit.
Sure I think it's doable ; it was just to outline this time I have some use-case to try, test and provide feedback. The first time, I only tested frecklecute as I have nothing to do with freckelize.
And sure, I'll just work on my freckelize once you consider the application ready for testing ; and I'll happily provide my feedbacks.
And sure, I'll just work on my freckelize once you consider the application ready for testing ; and I'll happily provide my feedbacks.
https://code.fb.com/data-infrastructure/xars-a-more-efficient-open-source-system-for-self-contained-executables/ I think it may be of interest to you
Looks cool, the only problem is it needs quite a few system-dependencies.
So, once you setup all of those it's cool, but you need to install them first.
Which would be easy once freckles is installed, but not suitable for bootstrapping.
Would be interesting to support as a sort of 'package manager' though.
Currently working on making the install of packages transparent by automatically installing the package manager and its dependencies whenever the user uses the special 'install' Ansible module I'm writing.
Old freckles could do that already, but the code is a bit crap.
There is no documentation yet, so probably not really useful just now.
curly install now via
curl https://freckles.sh | bash -s -- frecklecute
And this is where the included (Ansible-type) frecklets live: https://gitlab.com/freckles-io/frecklets-nsbl
A frecklet is a bit like a mini-frecklecutable.
And a frecklecutable is basically a top-level frecklet (that usually calls other frecklets).
Example:
calls
Install location is now $HOME/.local/share/inaugurate/...
Only bigger thing missing is a password-plugin system, so sensitive variables are protected.
Also, I'm using the Parity license for now. Might change that later, but not sure yet.
You had a few commits in the last version, those files are either gone or completely rewritten, just in case you are wondering whether re-licensed your code without your permission :-)
Will start on documentation soon, but feel free to ping me if you have any questions.
Scope of freckles is much wider now, not just a boostrap-wrapper around Ansible. More like a declarative script interpreter or something.
About Parity License, what is your interpretation of
3. Contribute all source code for software you develop, deploy,
monitor, or run with this software. for closed source developments (only my customer has access to source-code) where I use freckles (or frecklecute, don't if there is still a distinction) for developer tooling installation ?
If it touches the non-open code in some way it isn't.
You'd have to publish the frecklecutable you use, but I assume that wouldn't be a problem, right?
If there are small parts that are non-free, one could always install the bulk of it using freckles, and have a small custom bash script or so that does the rest.
Bit cumbersome, but I figure I need some reason for people to consider buying a license.