app | Spiral Framework Skeleton HTTP Application : Queue | Application Framework library

You have included fetching function in the component as it is, so it fires every time component being rendered. You better to include fetching data in useEffect hook just like this:

Run ‘python manage.py collectstatic’ and try again.

The way you handle static wrong, remove the static dirs in your INSTALLED_APPS out of STATIC_DIRS and set a STATIC_ROOT then collectstatic again.

Add the following as django documentation to your urls.py

Why do I name projects with a website in the path?

If your package has the exact same import path as someone else's package, then someone will have a hard time trying to use both packages in the same project because the import paths are not unique. So long as everyone uses a string equal to a URL that they effectively "own", such as your GitHub account (or actually own, such as your own domain), then these name collisions will not occur (excepting the fact that ownership of URLs may change over time).

It also makes it easier to go get your project, since the host location is part of the import string. Every source file that uses the package also tells you where to get it from. That is a nice property to have.

Where do I initialize git?

Your project should have some root folder that contains everything in the project, and nothing outside of the project. Initialize git in this directory. It's also common to initialize your Go module here, if it's a Go project.

You may be restricted on where to put the git root by where you're trying to host the code. For example, if hosting on GitHub, all of the code you push has to go inside a repository. This means that you can put your git root in a higher directory that contains all your repositories, but there's no way (that I know of) to actually push this to the remote. Remember that your local file system is not the same as the remote host's. You may have a local folder called github.com/myname/, but that doesn't mean that the remote end supports writing files to such a location.

The next-fire-base-auth config documentation links to the cookies package. Under the cookies example, I found:

If you are using vuetify from vue-cli-plugin-vuetify (vue add vuetify), treeshaking and auto component import is enabled by default, by using vuetify-loader.

If you look into the source code of vue-cli-plugin-vuetify, it only uses vuetify-loader if it is present in your package.json. So removing vuetify-loader from package.json should disable this behavior.

I'm sure it's not the most efficient, but it worked.

Since, I am not 100% sure the context in which you are trying to apply the MVC pattern, a good generic explanation of MVC can be found in GoF's 1995 book, Design Patterns: Elements of Reusable Object Oriented Software.

In the book, they state the following.

The Model is the application object, the View is its screen presentation, and the Controller defines the way the user interface reacts to user input.

A more robust explanation can be found from Martin Fowler where he also makes the case for a variation of Model View Controller that uses a Presentation Model.

If you are referring to Spring MVC then there is some magic that blurs the lines a bit. But in general, you have a controller that represents some screen or an encapsulated piece of functionality that the user (web requests) interact with. The controller serves up responses that are derived from the domain, usually via a Spring Service (i.e. @Service). The domain (Model) doesn't know anything about the View and the View may or may not know anything about the domain.

Given that, the View should be derived from the Model. But that's not always the case since sometimes how we present things to a screen is not the best logical way to model things in our domain - not to mention, the domain should be presentation agnostic. This leads into Fowler's argument for a Presentation Model, which is a model that belongs to the Presentation.

I call this a Presentation Model because it's a model that is really designed for and thus part of the presentation layer.

Microsoft took that idea and ran with it in a variant of MVC called MVVM (Model View ViewModel).

You can read more about that in Microsoft's documentation on ASP.Net Core.

So, back to your original question of "Should you pass the model directly to the view?" If you are using MVC then the controller is what provides the interaction. But if you're really asking, "Can you bind your view directly to the model?" If your model has all the stuff you need organized how your view needs it, then sure. And if it's simple enough, maybe that's the way to go. Otherwise, you could go with something like a Presentation Model or MVVM.

Remove your agreement vars in MinimalClone.sol, and either have the user input them as args in your init() method or hardcode them into the request like this:

Under Support+troubleshooting -> Resource health of your virtual machine portal panel, you can set up a health alert. You can then select under which conditions the alert should be triggered. In your case, Current resource status: Unavailable should work just fine. You can also implement a custom notification (E-Mail) under Actions or implement a logic that triggers an Azure Function or Logic App that performs an action when the VM is unavailable.

To detect if your application in Apache server is working correctly you can use a monitoring solution that checks the Apache error logs.