Ablageort im Repository (GitLab): Projekt3091-Landräume Admin
Diskussionsforum (Discourse): Projekt3091-Landräume Admin
Readme: Projekt3091-Landräume Admin
Beschreibung des Projektes:
PublicCode.YML: anzeigen
OSS Compliance: anzeigen
LandRäume provides the opportunity to present, book, and pay for space offers of all kinds nationwide. The project part "LandRäume Admin" refers to the view of the space provider, where it is possible to create, edit, and publish spaces, view and edit existing bookings, and manage the organization. The space provider must first be accepted by a district before they can post anything on LandRäume.
To run the project locally, follow these steps:
Services: Ensure the following services are running: slr-authorization-service (keycloak), slr-user-service, slr-media-service and solution1-admin-sdk (refer to the corresponding projects for setup instructions).
Private SDKs: Generate TypeScript SDKs for some services mentioned above using openapi-generator.
SLR Shared Library: Ensure that shared library is hosted and can be installed (refer to the corresponding projects for setup instructions).
These SDKs can be hosted privately as well. If hosting privately, configure access for these packages. See for more in .npmrc.default.
The project structure is organized as follows:
All implemented pages, context, hooks utils and more can be found inside the src folder.
assets: Includes icon library and images used within the application.
components: Includes shared views used within different pages.
contexts: Includes the different contexts that are shared between components.
hooks: Includes all hooks used within the components. Endpoints are grouped within folders and for each endpoint independent hooks are created.
i18: Includes localization configurations and localized values.
layouts: Includes the layout implementation of the application.
mocks: Includes the mocks for running the tests.
pages: Includes all pages, their routings.
providers: Includes implementations of providers used for sharing various contexts.
schemas: Includes the schema validations for user inputs.
services: Includes services hooks and api configurations. Services are grouped within folders and for each service api controller independent hooks are created.
settings: Includes the seetings/configurations that are used across the application.
styles: Includes implementations related to theming/styling.
utils: Includes shared utils and helper functions implementations.
In the project directory, you can run:
Installs all packages and dependencies listed in `package.json`.
Runs the app in the development mode.\
Open http://localhost:3000 to view it in the browser.
The page will reload if you make edits.\
You will also see any lint errors in the console.
This is a list of the used libraries, their description as provided by the libraries authors and their license(s).