10000 Consider moving away from Ansible · Issue #82 · wincent/wincent · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Consider moving away from Ansible #82

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

< 8000 div class="d-flex flex-items-center"> Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
wincent opened this issue Mar 17, 2020 · 4 comments
Closed

Consider moving away from Ansible #82

wincent opened this issue Mar 17, 2020 · 4 comments
Labels
wishlist

Comments

@wincent
Copy link
Owner
wincent commented Mar 17, 2020

I like it much better than any system configuration tool I've used in the past (that is, Puppet and then Chef), but I am scared of the complexity of the dependency tree. I get nervous every time I have to update, and that sucks. My entire programming career can be summed up as a war against the forces of entropy, and I don't exactly want my frickin' dotfiles repo to be the site of a losing battle in that fight.

Given that I am using it to do simple setup of one (local!) machine, I think it may be overkill, kind of like using a 10,000-pound hammer to drive in a nail. This issue is just a wishlist item for now, but it is something to think about.
wincent added a commit that referenced this issue Mar 20, 2020
@wincent
feat: create seed version of "install-next" script
29c93da 
Just playing around at this point to see if I could make something that
was very close to zero-dependencies (other than the language runtime and
its standard library), unlike Ansible, which sits atop pile of Python
infrastructure.

Related: #82
wincent added a commit that referenced this issue Mar 20, 2020
@wincent
feat: create seed version of "install-next" script
8809a16 
Just playing around at this point to see if I could make something that
was very close to zero-dependencies (other than the language runtime and
its standard library), unlike Ansible, which sits atop pile of Python
infrastructure.

Related: #82
@wincent
Copy link
Owner Author
wincent commented Apr 24, 2020

Going to close this. Not done yet, but we're well past the "considering" phase at this point.

@wincent wincent closed this as completed Apr 24, 2020
@nomasprime
Copy link

Hey @wincent 👋

Discovered your work a while back through your YouTube channel, really good stuff. Came here and you were the first other person I've found using Ansible for their dotfiles.

I started out with Puppet about seven years ago, then Ansible, Salt, and back to Ansible because it works better for configuring localhost.

Now I see you've gone one step further and written your own provisioner, Fig—wow.

I understand your motivation but wondering how you feel about it now: is addressing these issues worth the extra development and maintenance time; other than stated in the Readme, have you discovered any other advantages; any disadvantages?

@wincent
Copy link
Owner Author
wincent commented May 12, 2020

@nomasprime:

I understand your motivation but wondering how you feel about it now: is addressing these issues worth the extra development and maintenance time; other than stated in the Readme, have you discovered any other advantages; any disadvantages?

At the end of the day this is partly about wanting to avoid incurring a massive dependency footprint in the form of Ansible, but mostly about having a bit of fun. If I wanted something minimal, I could do quite a bit with a simple Bash script. But instead, I dedicated some hours on evenings and weekends making something that gave me a bit of pleasure.

@nomasprime
Copy link

Thanks @wincent. Fun's a great reason, too many people forget.

wincent added a commit that referenced this issue Apr 9, 2025
@wincent
fix: unbreak yazi config after update
f576938 
With old config, launching the updated version of yazi dumped you in a
blank screen.

Needed to update submodule and apply other tweaks to unbork.

* aspects/dotfiles/files/.config/yazi/vendor/plugins beb586a...a1738e8 (29):
  > docs: no longer need nightly build for vcs-files.yazi
  > fix: bump version to 25.4.4
  > refactor: simplify default value assignment
  > feat: make `git.yazi` work in the search view (compatible with `vcs-files.yazi`)
  > fix: bump required Yazi version to 25.2.26
  > refactor!: switch to `th` (#87)
  > feat(git): use terminal colors and consistent icon style in default options (#86)
  > fix: don't draw `┬` and `┴` if the user changed their border symbol, closes #85
  > refactor: add a comment to explain why we skip some paths
  > docs(git): added some comments to improve understanding (#84)
  > feat(git): adjust the priority of codes (#83)
  > refactor(git): use more appropriate variable names (#82)
  > refactor: use meaningful variable names instead of single letters (#81)
  > refactor: rename ignored to excluded
  > refactor(git):  remove unnecessary logic (#80)
  > docs: add `vcs-files` plugin to the list
  > fix: use into_search instead of to_search
  > Update README.md
  > feat: new plugin `vcs-files.yazi`
  > refactor: use a table for status codes (#79)
  > refactor: update for Yazi v25.2.26
  > refactor: simplify the code
  > docs: use the correct term for panes in toggle-pane.yazi
  > docs: fix the installation command for toggle-pane plugin
  > docs: correct the description of toggle-pane.yazi
  > docs: expand the description of the toggle-pane plugin
  > chore: rename toggle-view to toggle-pane for better semantics
  > docs!: deprecate max-preview and hide-preview in favor of toggle-view
  > feat: new plugin `toggle-view.yazi`, closes #71
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
wishlist
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@wincent @nomasprime
0