Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Oct 23 2020 23:58
    tmesser removed as member
  • Oct 19 2020 18:36
    groggemans commented #103
  • Oct 19 2020 18:32

    groggemans on master

    Replace dependency on 'rev' wit… Merge pull request #104 from r4… (compare)

  • Oct 19 2020 18:32
    groggemans closed #104
  • Oct 19 2020 18:32
    groggemans closed #103
  • Oct 19 2020 18:27
    groggemans milestoned #104
  • Oct 19 2020 18:27
    groggemans labeled #104
  • Oct 19 2020 18:26
    groggemans assigned #104
  • Oct 19 2020 18:26
    groggemans review_requested #104
  • Oct 18 2020 12:36
    r4lv opened #104
  • Oct 18 2020 12:05
    groggemans milestoned #103
  • Oct 18 2020 12:04
    groggemans demilestoned #103
  • Oct 18 2020 12:04
    groggemans milestoned #103
  • Oct 18 2020 12:03
    groggemans assigned #103
  • Oct 18 2020 12:03
    groggemans labeled #103
  • Oct 18 2020 12:02
    groggemans commented #103
  • Oct 18 2020 11:38
    r4lv opened #103
  • Sep 20 2020 05:38
    shadowrylander commented #102
  • Sep 20 2020 05:37
    zeekay commented #102
  • Sep 20 2020 05:35
    shadowrylander opened #102
Zach Kelling
@zeekay
ok cool thanks man
oversight on my part, sorry about that
Gertjan Roggemans
@groggemans
NP! :)
Zach Kelling
@zeekay
should be fixed!
Gertjan Roggemans
@groggemans
Works again, thanks!
Zach Kelling
@zeekay
:D
Zach Kelling
@zeekay
@groggemans any thoughts about where we go from here with ellipsis? It would be nice to sketch out 2.0 wants/wishes
maybe we should ping community for improvements / desired changes?
any thoughts about how best to get more people using ellipsis?
Gertjan Roggemans
@groggemans
Getting more people to use ellipsis is probably not so hard to do, we should just spread the word :) I gave an introduction to ellipsis to a few colleagues last week and there was a lot of interest. If we could do a few talks at meetups and development conferences and get other people to do the same that would be a good start
Zach Kelling
@zeekay
great idea
Gertjan Roggemans
@groggemans
about 2.0, I have been thinking a lot the last two years.. I like bash, but it's definitely a limiting factor. On the other hand, it makes it way easier to customize and hack the tool. GO seemed like a nice option to play with ( easy to make static binaries) but I'm afraid we would lose flexibility and hackability.
Zach Kelling
@zeekay
yeah
i like Go a lot (we've been using it in production for over 4 years now)
I am not the biggest fan of bash
but for ellipsis it's great -- i can curl ellipsis.sh | sh on any machine
and get up and running seconds
i've probably run curl ellipsis.sh | sh several thousand times at this point
i've had pretty much zero issues across thousands of installs for all the time i've been relying on it
heck i used it last night
to get my dotfiles on a random vm i was messing with
haha
Gertjan Roggemans
@groggemans
:D Either way, I'd like to do a redesign and new implementation from the ground up to fix some deeper "issues"
Zach Kelling
@zeekay
the biggest thing i'm missing would be
discoverability of packages
search
better bootstrapping for new packages
tools for adding/removing files from packages easily
i've also been thinking about how to make the curl ellipsis.sh | sh move more secure, possibly by using PGP
a package index + site would be nice
Gertjan Roggemans
@groggemans
package dependencies would be a nice addition too
Zach Kelling
@zeekay
yeah
definitely
Gertjan Roggemans
@groggemans
But a lot of these things are hard to do with pure bash :(
Not impossible, but hard :)
Zach Kelling
@zeekay
yeah
it's definitely annoying -- which lead to our current bash "standard library"
Gertjan Roggemans
@groggemans
The idea behind ellipsis is awesome, and there aren't much alternatives out there. So we should definitely do v2! I think we've learned a lot with v1, and we will probably learn a lot more in the time we need to build a v2. I'll create an issue to gather some ideas for v2 (, and then we just need to make a good design and find some time to build it :D )
Jeff McCarrell
@jmccarrell
Hello Zach and friends. I'm trying to use ellipsis to manage my dot files. Like many, I have a long and somewhat twisted set of files that I want to rationalize. Above I see some questions about how to get more folks using ellipsis. I, for one, would love to see a worked example in the docs to bootstrap from existing dot files using ellipsis. Does something like this already exist? thx...
Specifically, it is not clear to me what the model is here. I have several git repos that I would like to manage with ellipsis
Jeff McCarrell
@jmccarrell
When I install from a github url, a new copy of the repo is cloned under the ellipsis install direction in packages
that was not what I expected; I expected ellipsis to install from a git repo that I am managing directly.
Perhaps an overview of the theory of operation would help out? Any suggestions welcome.
It seems like the only way ellipsis can discover files to install is if they are in the root of the repo; files in subdirectories are ignored. Is that right?
Jeff McCarrell
@jmccarrell
If the model is that ellipsis makes its own copy of the git repo, then what is the usual workflow to update and install a change?
I don't seem to be getting it.
Jeff McCarrell
@jmccarrell
FWIW, I would be willing to write docs to help the next noob up this learning curve...
Gertjan Roggemans
@groggemans
Hi @jmccarrell, welcome, and thanks for using ellipsis! There are currently no detailed examples about bootstrapping from an existing setup (AFAIK). The hard part for such documentation is that everybody has a different setup to start from, and might use ellipsis in there own way. Although that doesn't mean we can't document some approaches of doing this. Your contributions would be greatly appreciated!
Gertjan Roggemans
@groggemans
Ellipsis always installs packages in it's packages directory (this can be changed to another location). I install packages with SSH on the machines where I manage my packages, and then update the packages in their installation location (.ellipsis/packages by default), but this workflow is not always ideal and has flaws for certain changes. I've been thinking to add a few commands to ellipsis to make this workflow easier. Each config has its own repo/package (you can look under my personal github page (/groggemans) for examples). You can put all your configs in a single package, but that's not always ideal. And you're correct that only Files in the root are linked by default (can be overwritten). This is a very simple default behavior to prevent the need for an ellipsis.shfile for the most basic packages.
Jeff McCarrell
@jmccarrell
Thanks very much @groggemans for the response. I understand where the project is coming from; it is understandable that ellipsis is not opinionated in that way as dotfiles are a pretty wide open kind of topic. That being said, after looking into this a bit more, I think I am going to try my luck with vcsh. Take care...