leapp VS lowdefy

Summary:

Do you find yourself overwhelmed with work, requests, or complaints and in need of assistance to alleviate the pressure, enhance communication, facilitate organization, prioritize tasks, and foster greater trust and transparency?

Alternatively, I can work as a full stack developer.

AWS Community builder, AWS User group Leader, public speaker (https://www.youtube.com/watch?v=qdu58NAQfU0&t=271s)

Or perhaps you need both? =)

I have 4+ years of experience as a product manager and 8 in product development (before pm: agile coach, UX designer, and developer).

I've been the co-founder of the open-core company behind the OSS project Leapp (https://github.com/Noovolari/leapp)

Please feel free to reach out.

You can switch to saml2aws using the browser method instead of the Okta method and it will continue to work after the upgrade. There is also a really neat GUI tool to manage your session tokens that also works. https://www.leapp.cloud

Take a try to Leapp: https://github.com/Noovolari/leapp

Hello everyone, I'm the maintainer of an open-source DeveloperTool (https://github.com/Noovolari/leapp)

With a heuristic of 7000 users daily, I started feeling the need to have more information on how Users are using the project to improve it.

Is it the right thing to do to create a better Developer Experience and gain feedback for the end users?

On a side:

- For all your employees I can advice you Leapp as open-source project (https://github.com/Noovolari/leapp). It solve mayor of the problem listed here:

I am looking to manage Leapp (https://www.leapp.cloud/) from the StreamDeck. Leapp allows you to manage and switch between different Cloud Accounts (AWS, Azure, etc). Leapp has a command line interface which I could automate with a StreamDeck plugin. Unfortunately it looks like the only official SDK is the sandboxed JavaScript one. This means I cannot automate command line tools with it.

If you’re wondering if there is a tool that allows you to stop thinking about AWS credentials and where to store them in the right way, give a look at Leapp! It takes the responsibility of storing long-term credentials in the system vault, generating/refreshing short-term credentials, and placing them in the right place for the clients to use them.

Still, there is an elementary problem that we need to address, and it’s more on the operational side of things. Once we secured and implemented a tremendous multi-account strategy, how do people access AWS accounts? It turns out there is a fantastic open-source tool that lets you handle that with no effort, and its name is Leapp.

When you have to configure access to multiple AWS accounts using the Assume Role access pattern, it becomes difficult to get rid of all the Named Profiles configuration data and relationships. When you’ve to deal with a complex access scenario, tools like Leapp (https://www.leapp.cloud) come to the rescue! Leapp avoids you to specify relationships between Named Profiles in the config file, as the access methods are stored in the tool-specific configuration file.

Leapp Github repository

I'm really enjoying reading through the docs and the tutorial. We've created Lowdefy, a config web-stack which makes it really simple to build quite advanced web apps. We're writing everything in YAML, but it has it's limitations, specifically when doing config type checking and IDE extensions that go beyond just YAML.

I've been looking for a way to have typed objects in the config to do config suggestions and type checking.. PKL looks like it can do this for us. And with the JSON output we might even be able to get there with minimal effort.

Is there anyone here with some PKL experience that would be willing to answer some technical questions re the use of PKL for more advanced, nested config?

See Lowdefy:

https://lowdefy.com/

https://github.com/lowdefy/lowdefy

Awsome! With Lowdefy we tried to build a low-code framework that works like code. We’ve developed a schema in which to define applications and we’ve built all kinds of apps for enterprise customers. Massive, advanced CRM systems, call centre solutions, ticketing systems, a light MRP, all kinds of survey apps and so many dashboards. Even our docs and our website are Lowdefy apps!

Give Lowdefy a try and reach out it you have any questions or want to see what is possible :) (We need to invest a lot more into content and examples, bootstapping is a grind!)

https://github.com/lowdefy/lowdefy

Also add Lowdefy onto the list https://github.com/lowdefy/lowdefy

co-founder here :)

100% this. And yes, good documentation takes a lot of investment but it pays off like compound interest. But with that done, it becomes even more important not to pull the carpet for no good reason, you are building a tower and documentation is at the foundation.

We’ve built Lowdefy [1] as an open source project and documented it with all effort, 200 pages of docs. I often forget why or how something works and then jump to the docs. This investment keeps on paying of as we use Lowdefy to build customer apps, new devs in the team typically take less than two week to get up to speed and start making contributions, the sharp ones, just a two or three days.

This year, we’re extended our documentation onto customer apps aswell, with flow diagrams, state machine definitions, detailed field level explication schema definitions, and end user test procedures. The key here for this documentation is detail. It should be easier to reach for the docs and the the answer, than to dive in the code and interpret it.

1 - https://github.com/lowdefy/lowdefy

https://github.com/lowdefy/lowdefy Co-Founder here.

Check out https://lowdefy.com/ they even have a sample survey app as one of their examples.

You can build an app that would do this

Lowdefy is a low code tool that uses AG Grid as a block component, allowing you to create apps which render data in AG Grid without a lot of coding knowledge. There is a Lowdefy example using AG Grid here.

Shameless plug, also check out Lowdefy - https://github.com/lowdefy/lowdefy

I’m also going to jump in here and say try Lowdefy https://github.com/lowdefy/lowdefy - co-founder here.

We take a different angle and believe that low code should still work like code. We focus on a developer first approach.