cloud

We badly started implementing some props mutation.
There are usually two cases:

1. The props are injected via root component propsData
2. The props are used inside a vue app

Solution 1

Migrate the propsData (usually initial-states) to the root .vue file away from the .js entry point

Solution 2

Use a sync modifier and change the data flow according to vue documentations

Describe the solution you'd like
It would be nice to have a way to control whether a VM starts on boot or not. Maybe a new autostart option to salt.states.virt.running and/or salt.states.virt.defined? Or maybe a new function?

Describe alternatives you've considered
I'll probably use salt.modules.virt.set_autostart for now.

The upstream pull got closed. It is referenced in:

• driver/registry_base.go#L246

This issue was created by the ORY Closed Reference Notifier GitHub action.

Describe the bug

Some devfiles have several commands that need to be executed in a precise order to succeed.
Some are named with prefixed numbers that help the user, but some others are not.

For instance:

• angular
• python-django

Che version

• latest
• nightly
• other: please spec

I like how Simplepush presents a couple of different ways to generate push messages on their website:

https://simplepush.io/#libraries

How about having a similar feature directly in the server GUI? That would include the bits documented here https://gotify.net/docs/pushmsg