Meltwater has a very complex tech stack, but many of its tools are ubiquitus and can be used / configured generically to provide those curious a base from which to build knowledge. This library and the scenarios housed here are intended to provide this base knowledge while also serving as a playground or reference for technology refreshment. Many of these courses may be referenced in https://underthehood.meltwater.com our engineering blog, provide introductory information to new-hires, or be used as a platform for internal knowledge transfer.

We are looking to provide training senarios and groupings to help people through not only a current understanding but future-proofing their learning with tracking of the courses they have already taken alongside newer ones as time progresses. To access our courses, all you should need is a web browser and a good internet connection:

• https://www.killercoda.com/meltwater

Anyone in Meltwater Engineering is welcome to commit new material to this repository, but the following must be adhered to in order to ensure the course is properly published to the main site. Also, it has been stated multiple times, all trainings posted should be kept to the generic toolset, not Meltwater-specific configurations (unless showcasing an open-sourced project).

There is a simplistic structure.json file that is present at the root of this repo and defines the top-level which can contain any number of components (Ex: 'elastic', 'grafana', 'drone') beneath. This json file works with the following options, all we ask is that it be kept alphabetical:

• path: The sub-directory of the course which will contain scenarios
• title: Title of the course to appear at the root / index
• description: Description of the course to appear at the root / index

{
  "items": [
    {
      "path": "drone-ci",
      "title": "Drone CI",
      "description": "Introduction to continuous improvement drone.io"
    },
    {
      "path": "elastalert",
      "title": "ElastAlert",
      "description": "How to write ElastAlert rules to alert on data in Elasticsearch"
    }
  ]
}

Senarios are the brains of your content and can contain lots of nice features:

• Example Layouts
• Quizes
• Documentation
• Migration
• Much more...

To edit a senario, please be considerate of the repo structure?

.
├── structure.json
├── component/
    ├── secenario/
    └── secenario/
        ├── assets/
        ├── index.json
        └── scenario files...

To create scenarios, follow the guides or an existing scenario and form a pull-request. This will start a testing proceedure visible on github actions.

Since you need to be able to try it out online, you can use a personal account to do the testing in and publish here when completed, but the katacoda scenarios:validate command will be your friend checking the syntax in json and the file structure you have created.

Once you are satisfied and are observing valid code, give it a push! This will automatically post the resources into Katacoda (typically within a minute) and you are free to reload scenarios and PLEASE test your changes out?

• https://killercoda.com/meltwater

This code-base and the Killercoda profile on killercoda.com are and will be maintained for the R&D organization so that there is a consolidated place for code.

• @meltwater-a-team