Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Jan 14 21:30

    makkus on develop

    Typo (compare)

  • Jan 14 21:19

    makkus on develop

    Refactoring: switch 'frecklet' … (compare)

  • Jan 07 14:37

    makkus on develop

    Updated frecklets Minor (compare)

  • Jan 06 19:37

    makkus on develop

    Pytest version Pytest version (compare)

  • Jan 06 19:17

    makkus on develop

    Cleanup cnf template Work on templating. (compare)

  • Jan 05 22:19

    makkus on develop

    documentation (compare)

  • Jan 04 17:04

    makkus on develop

    Fixed manifest (compare)

  • Jan 04 15:25

    makkus on develop

    Updated frecklets (compare)

  • Jan 04 14:39

    makkus on develop

    Added documentation. Auto-doc html template. Auto-doc markdown template. and 4 more (compare)

  • Dec 21 2018 12:48

    makkus on develop

    Formatting (compare)

  • Dec 21 2018 12:43

    makkus on develop

    Unlock config command. (compare)

  • Dec 20 2018 22:23

    makkus on develop

    bumpversion config (compare)

  • Dec 20 2018 18:39

    makkus on develop

    bumpversion (compare)

  • Dec 20 2018 18:04

    makkus on develop

    dependencies. Set version to 1.0.0-beta1 (compare)

  • Dec 20 2018 17:11

    makkus on develop

    Updated dependencies. (compare)

  • Dec 20 2018 16:24

    makkus on develop

    Renamed: connector -> adapter (compare)

  • Dec 20 2018 11:43

    makkus on develop

    Formatting (compare)

  • Dec 20 2018 11:40

    makkus on develop

    Also inherit 'msg' if necessary. Minor (compare)

  • Dec 19 2018 23:24

    makkus on develop

    Tests. Requirements for dev. Consolidated doc related method… and 6 more (compare)

  • Dec 19 2018 16:29

    makkus on develop

    Removed old code. (compare)

Markus Binsteiner
@makkus
Haven't published my changes yet though.
Laurent
@lalmeras
Yes, it was something I propose as a new feature ; I hope it is not too painful to implement this
If you think I can provide some helpful contribution, do not hesitate. I think you know some of my skills.
Markus Binsteiner
@makkus
Oh, it was plenty painful to implement :-)
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.
Laurent
@lalmeras
fine, do not hesitate if you find any subject where I can help
Laurent
@lalmeras
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
Markus Binsteiner
@makkus
I'm not 100% sure I understand the requirements exactly, but that sounds definitely doable and easy, especially after the rewrite.
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.
Laurent
@lalmeras
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.
Markus Binsteiner
@makkus
Cool, thanks again!
Markus Binsteiner
@makkus
Thanks, yes, I've read about it just yesterday.
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.
Markus Binsteiner
@makkus
Hi @lalmeras , just a quick heads up: I published the new, rewritten freckles and all the dependency libraries on GitLab:
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/...
Markus Binsteiner
@makkus
Still a bit of work to do, but I'm more or less happy with the design now, and most features.
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.
Laurent
@lalmeras
Fine, I'll try to give it a glance this weekend.
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 ?
Markus Binsteiner
@makkus
I'd say, as long as the developer tooling is open source it's ok.
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.
Markus Binsteiner
@makkus
Also, the old freckles is still available and that's GPL. I'll keep a repo around, and provode a inaugurate script for it.
Laurent
@lalmeras
Thanks for your answer about License ; still not sure about what I can and can't do. I still plan to give it a try, but I fail to find some spare time these last weeks :-(