by

Where communities thrive


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

    makkus on develop

    Typo (compare)

  • Jan 14 2019 21:19

    makkus on develop

    Refactoring: switch 'frecklet' … (compare)

  • Jan 07 2019 14:37

    makkus on develop

    Updated frecklets Minor (compare)

  • Jan 06 2019 19:37

    makkus on develop

    Pytest version Pytest version (compare)

  • Jan 06 2019 19:17

    makkus on develop

    Cleanup cnf template Work on templating. (compare)

  • Jan 05 2019 22:19

    makkus on develop

    documentation (compare)

  • Jan 04 2019 17:04

    makkus on develop

    Fixed manifest (compare)

  • Jan 04 2019 15:25

    makkus on develop

    Updated frecklets (compare)

  • Jan 04 2019 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
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 :-(