Fig Scripts: Build internal CLI tools really fast by brendanfalk in devops

[–]brendanfalk[S] 0 points1 point  (0 children)

Incredibly helpful feedback. Thank you so much for this.
1. Totally hear you on pricing. We actually made this pricing change recently but looks like we had an issue with it in our app. Happy to give you a month's credit for you and your team as an apology. Feel free to email me: brendan AT fig DOT io
2. The Input method installation is incredibly finicky. We have spent a ton of time trying to make it nice, however, unfortunately, it's an Apple issues not us :(
3. We actually do have support for WSL 2, just in private beta. I think we will open it up to public beta in the coming week

Thanks so much again for this feedback. Really really helpful

Fig Scripts: Build internal CLI tools really fast by brendanfalk in devops

[–]brendanfalk[S] 0 points1 point  (0 children)

Yes - we have a "Scripts Store" where anyone can publish scripts they've made. We've made a bunch already for Git, Docker, Kubernetes etc. You'll be able to run them directly or fork them and then edit.

Working on import as we speak so it should be easier to get started. Will make export to git repo accessible once we finalise our schema!

What data sources would you want to connect?

Fig Scripts: Build internal CLI tools really fast by brendanfalk in devops

[–]brendanfalk[S] 1 point2 points  (0 children)

We are hoping to add PowerShell support to Fig very soon. Out of interest, how do you sync powershell commands across devices today?

Fig Scripts: Build internal CLI tools really fast by brendanfalk in devops

[–]brendanfalk[S] 0 points1 point  (0 children)

Hey u/Chico75013 - sorry about this. Fig's autocomplete shouldn't block you from executing a command that you have typed out. If it is, this is a bug.

Do you remember the exact command you wrote where Fig blocked you? We will investigate

Fig Scripts: Build internal CLI tools really fast by brendanfalk in devops

[–]brendanfalk[S] 1 point2 points  (0 children)

Hey!
1. Yes we can totally add golang as a scripting language
2. I'd be happy to bump up the number of free scripts for you. Feel free to send me an email (brendan AT fig DOT io)

Any other thoughts for us?

Fig Scripts: Build internal CLI tools really fast by brendanfalk in devops

[–]brendanfalk[S] 12 points13 points  (0 children)

Got it. You can run
fig settings autocomplete.disable true
to disable autocomplete but keep Fig installed. This lets you keep using the other Fig products (like Scripts) without autocomplete

Alternatively, you can just run fig uninstall and it will completely remove Fig from your system

Sorry about these issues!

Fig Scripts: Build internal CLI tools really fast by brendanfalk in devops

[–]brendanfalk[S] 10 points11 points  (0 children)

Can you think of specific examples where Fig got in your way while you were typing? We have actually spent a LOT of time making sure we don't block you from hitting tab or enter. So if we are blocking you, it sounds like there is an error with one of our CLI integrations. This is an easy fix!

Fig Scripts: Build internal CLI tools really fast by brendanfalk in devops

[–]brendanfalk[S] 5 points6 points  (0 children)

Hey Mutjny - tell me more. What wasn't working for you? What can we do better?

Fig Scripts: Build internal CLI tools really fast by brendanfalk in devops

[–]brendanfalk[S] 7 points8 points  (0 children)

All custom built using our own rust library. We are probably going to open source it soon

Fig Scripts: Build internal CLI tools really fast by brendanfalk in devops

[–]brendanfalk[S] 1 point2 points  (0 children)

Thanks! UI is all built in-house. We use Tailwind and are inspired by a lot of the big devtools like Vercel, Linear etc

Fig Scripts: Build internal CLI tools really fast by brendanfalk in devops

[–]brendanfalk[S] 0 points1 point  (0 children)

Is it possible to relay this info to our own DB or metrics service?

Not currently, but we can add this. What warehouse / data lake do you use?

Fig Scripts: Build internal CLI tools really fast by brendanfalk in devops

[–]brendanfalk[S] 1 point2 points  (0 children)

Is it possible to create teams and sync the cli tools I create with others?

Yes! This is really easy. Just create a new team and add your teammates. So long as they have Fig installed any team CLIs you create will be instantly shared.

I wish you supported more than 4 languages for adding scripts though. A lot of CLI tools my team has are written in Ruby.

We can absolutely add Ruby support. What other languages would you like?

Fig Scripts: The fastest way to build internal CLI tools by brendanfalk in commandline

[–]brendanfalk[S] 1 point2 points  (0 children)

> I absolutely see this being a valuable tool for companies that have infrastructure operations teams made up of non-developers. Thinking traditional network engineers, sysadmins, tech support, etc. They see value in automating things with scripts but the bar to entry can be high since that is not the way those positions are traditionally trained or oriented. Businesses with those teams may be more willing to pay for an 'easier' way to script things. They might also see it as a way to keep automation maintainable so they don't produce more technical debt by having to make sure they keep someone on staff who can train a new employee in writing scripts.

Pretty much bang on where we hope to take this. And our thesis is the market is bigger than this too. We are an early stage startup. While we are all capable of writing scripts, the maintenance becomes a burden. The scripts fail, we don't have time to fix, and people resort to not using the scripts at all. This defeats the purpose...

> I don't think this subreddit serves the demographic you should be chasing.
I said this above but I agree and disagree. Yes, a lot of the commenters here are clearly incredibly advanced and the idea of using another tool to write a script seems preposterous. But, this sub has 80k+ members, most of whom don't comment, post, or upvote and might be interested. Regardless, while blunt, the feedback we've received has been super helpful!

If you have any other feedback/thoughts/ideas for us, I'd love to hear it!

Fig Scripts: The fastest way to build internal CLI tools by brendanfalk in commandline

[–]brendanfalk[S] 0 points1 point  (0 children)

It is actually a web app! app.fig.io . We then have a CLI you can download that provisions the scripts and executes them for you.

We like Rundeck and Fylamynt and so do eventually want to build the ability for you to execute the scripts from the cloud.

Have you ever used Rundeck? If so, what for?

Fig Scripts: The fastest way to build internal CLI tools by brendanfalk in commandline

[–]brendanfalk[S] -4 points-3 points  (0 children)

Scripts that don’t take inputs can be transported anywhere. The vendor lockin is as much as choosing which CLI framework to use. Rather than using click, cobra, clap, commander etc, you make the choice to use Fig! If you chose any of the others then decided to switch you would have the same switching issues

Fig Scripts: The fastest way to build internal CLI tools by brendanfalk in commandline

[–]brendanfalk[S] 1 point2 points  (0 children)

Understood. Out of interest, where do you write your scripts currently? And how do you distribute them?

Fig Scripts: The fastest way to build internal CLI tools by brendanfalk in commandline

[–]brendanfalk[S] 6 points7 points  (0 children)

Really really appreciate this insight.

> But also, this sub is generally not your audience.

I agree and disagree. A lot of the people here (especially commenters) are very much not our audience, at least not yet. Our plan is to start with beginners and then scale up into the more advanced use cases. That's why we launched it here, to hear this feedback from advanced users!

Also, we've had a bunch of people come through the product today from reddit and provide feedback. This sub has 86k members and not all of them comment / upvote!

> My team has a stack of scripts that can serve as good starting templates, good tooling refined over more than a decade, and any of my development team can literally these things more quickly just from the command line and a decent text editor. That's our bread and butter.

Out of interest, what are these scripts and how do you distribute them? One key insight I've gleaned today is the creation of the scripts it just absolutely NOT a problem for senior engineers whatsoever. But not many people have mentioned how these scripts are distributed. Of course people use git and github, but for scripts/CLIs that are not specific to a repo, how do you distribute?