obsidian | A custom Minecraft server written in C | Runtime Evironment library

In your config, the server is running only on port 80

Try dotnet contest.dll first. Please note the absence of option -d in the command.

Even then it does not run most likely it is a permission issue. Does the user have executable permissions? You can try giving permissions using chmod ### directory/where/dotnet/publish is done. Try giving 777 permissions and check.

You can also try clearing Nuget cache files at /tmp/NuGetScratch/lock/ using command rm /tmp/NuGetScratch/lock/* if the some other user has used chmod command. Sometimes nuget lock files do create issues if multiple users have access to lock directory.

I managed to solve the issue. The root of the problem is that Plesk expects the package.json file to be in the domain root. Instead it was in a subdir.

I also found later this tutorial: https://www.plesk.com/blog/product-technology/node-js-plesk-onyx/

.obsidian/workspace is a tracked file. A file that is tracked is never ignored.

A tracked file is any file that is in Git's index right now.

Git's index is initially filled in from the commit you check out. So if some file exists in some commit, and you git checkout that commit or git switch to it, that file, from that commit, goes into Git's index. It is now in Git's index and by definition, is tracked. Note that Git fills in both its index and your working tree, at the same time, during this checkout / switch operation.

You may manipulate a file that is in Git's index at any time:

• Running git add on some file in your working tree—this is the version of the file that you can see and edit—kicks any existing copy of that file out of Git's index, then puts the working tree version of the file into Git's index. So now the index and working tree copies match. The file is also tracked, since it exists in Git's index.

• Running git rm on some file that is in both Git's index and your working tree, removes the copy of the file from Git's index, and removes the copy of the file from your working tree. The file is now gone entirely and therefore is not tracked.

• Running git rm --cached on some file that is in both Git's index and your working tree, removes the copy of the file from Git's index, but leaves the copy in your working tree alone. The file is now untracked by definition, as it exists in your working tree, but no longer exists in Git's index.

• Last—this is redundant but worth noting—if you remove the working tree copy of some file that was in both places, then use git add on that file, Git will remove the copy from its index. So this has the same effect as git rm (without --cached) on that file.

When you run git commit, Git—at that time—freezes a snapshot copy of every file that exists in Git's index, exactly as it appears in Git's index. These are the files that go into the new commit. So the index always holds the files that you propose to include in your next commit. That's why Git fills in the index from the current commit when you check out that commit: so that the proposed next commit, matches the current commit that you just checked out.¹

If you want a file to be ignored, but it's currently tracked, you must remove the file from Git's index. Note, however, that if that file exists in some existing commits, those commits will continue to contain that file. New commits you make, having removed the file from Git's index, will omit the file. Comparing the existing commits to the new commits will show the file as being removed.

If you ever check out one of the older commits that has the file, then switch to one of the newer commits that lacks the file, Git will remove the file—because that's the difference between the older and newer commit! So be careful after removing files that should never have been committed. The existing commits do have the file, even if they shouldn't. Checking out the older, existing commits that do have the file will cause pain in the future.

¹There are some special cases here: see Checkout another branch when there are uncommitted changes on the current branch for the gory details.

Add in "config/mail.php"

you absolute position the navbar to the top. Then you use instead of the body a wrapper with a height of 100vh - paddings top + bottom. That way the content wrapper will fill the entire screen height. Then give the content wrapper an overflow rule.

I fixed it by changing my mail driver to SMTP, this allowed my mails to add a DKIM signature

Ok so I solved the problem!

I had to move a few things around: rollup.config.js:

You implementation is legit except it doesn't meet the requirement that requestAnimationFrame or setInterval API must be used.

I'll go with requestAnimationFrame. Refer to the doc and example, requestAnimationFrame(step) takes as argument a step function. The key is to calculate and update, within the step() function, the (x, y) coordinates of the position of that yellow dot for each animation frame.

Refresh our memory about the Parametric Equation of a Circle. x = r * cos(t); y = r * sin(t). In your case r = 200, and t the theta angle goes from 0 to 2π in 4 seconds.

Here's the step(timestamp) function. It is passed the timestamp of current animation frame at each call.