Hey everyone, :rocket: :rocket: :rocket: I’m thr...

# feed

[Jgafner]

Hey everyone,

🚀 🚀 🚀
I’m thrilled to announce a new public available free plugin of mine I’m super proud of!
RUN LIKE ME
🚀 🚀 🚀

This plugin allows you to dynamically generate Run Configurations using templates, offering great flexibility and protecting your configurations from accidental modifications.

I’d love to hear your opinion and feedback about it!

Run Like Me marketplace
Run Like Me documentation

[CLOVIS]

What can this do exactly? Is it just about storing run configurations in another directory? What is possible within the templates? Can a single template generate multiple run configurations?

[Jgafner]

Hi Ivan
This plugin aims to resolve different issues, but I guess the two main ones are:
1. For a large organization with a lot of developers and applications with run configurations, you, as a developer, don’t want the idea to show you all but only those relevant
2. When you share the configuration within the VSC, anyone can change the shared configuration and can break this configuration for other developers (adding an env that exists only on his machine), so when you store the template instead of the configuration you enforce an explicit change policy
Regarding your question, you can generate from a source template ( a folder with multiple template files), and the plugin will create RC files for each template file.
So basically, a single template file is generated to a single run configuration

[Jgafner]

Forgot to mention that one can work with both templates and run configurations stores in vcs. So you can keep the configurations you want to and also have templates.

[CLOVIS]

when you store the template instead of the configuration you enforce an explicit change policy

I don't see it; in both cases, you require a new commit in the repository, right?

So basically, a single template file is generated to a single run configuration

I see. Something I wanted for a long time is a way to generate different run configuration for different environments.

[Jgafner]

If you have a configuration store in vcs pre plugin and you change it (flag, working directory, env…)
This change is immediately reflected in the VCS
And you can commit it and push.

When working with the template the generated run configurations are ignored. So if change something it will not change the template.
If you want to change the template the plugin give you the ability to generate the template from the changed run configuration.

About different environments - you can create multiple source templates ( folder that contains template file) for instance under the .runlikeme folder:
Dev/
Stage/
Production/

Or another example:
Us1/
Eu1/

Each one of those is a source template (contains one or multiple rlm files)

And when you need you generate the rc.
If you click on the run like me you can type stage click ok and you will have all the rc for that env.
You can do that for each one of those source or for a specific template in those sources.

The important point is that the generated location should be ignored.