Turborepo starter

This is an official starter Turborepo.

Using this example

Run the following command:

npx create-turbo@latest

What's inside?

This Turborepo includes the following packages/apps:

Apps and Packages

• dispatch: a dispatching platform for web based unit/mission dispatching
• docs: a Next.js app
• @repo/ui: a stub React component library shared by both web and docs applications
• @repo/eslint-config: eslint configurations (includes eslint-config-next and eslint-config-prettier)
• @repo/typescript-config: tsconfig.jsons used throughout the monorepo

Each package/app is 100% TypeScript.

Utilities

This Turborepo has some additional tools already setup for you:

• TypeScript for static type checking
• ESLint for code linting
• Prettier for code formatting

Build

To build all apps and packages, run the following command:

cd my-turborepo
pnpm build

Develop

To develop all apps and packages, run the following command:

cd my-turborepo
pnpm dev

Remote Caching

Tip

Vercel Remote Cache is free for all plans. Get started today at vercel.com.

Turborepo can use a technique known as Remote Caching to share cache artifacts across machines, enabling you to share build caches with your team and CI/CD pipelines.

By default, Turborepo will cache locally. To enable Remote Caching you will need an account with Vercel. If you don't have an account you can create one, then enter the following commands:

cd my-turborepo
npx turbo login

This will authenticate the Turborepo CLI with your Vercel account.

Next, you can link your Turborepo to your Remote Cache by running the following command from the root of your Turborepo:

npx turbo link

Useful Links

Learn more about the power of Turborepo:

• Tasks
• Caching
• Remote Caching
• Filtering
• Configuration Options
• CLI Usage

Execution policy

MachinePolicy Undefined UserPolicy Undefined Process Undefined CurrentUser RemoteSigned LocalMachine RemoteSigned

Moodle:

1. Im docker volume gehe in lib -> Classes -> OAuth2 -> Endpoint.php
2. überspringe die https enforcement rule am Ende der Datei (true in if abfrage)
3. Moodle Admin -> General -> HTTP Security -> Curl einschränkungen löschen
4. http://localhost:8081/admin/category.php?category=authsettings -> Guest login button -> Hide
5. http://localhost:8081/admin/settings.php?section=sitepolicies -> emailchangeconfirmation -> False
6. Beim anlegen des Auth-Services Require Email verification deaktivieren
7. Beim erstellen der Role für API user: permission moodle/site:viewuseridentity geben
8. API user zu moodle kursen hinzufügen, um andere Nutzer hinzuzufügen