Standarduser: [email protected] , password
npm install leaflet npm install --save-dev @types/leaflet
Leaflet: WGS84-Format (EPSG:4326) = gebräuchlich
GeoJSON-Datensatz = metrische Koordinaten im EPSG:25832-Koordinatensystem = UTM Zone 32N
- Create or upload files
- Add files using the command line or push an existing Git repository with the following command:
cd existing_repo
git remote add origin https://git.uni-due.de/sep/sommersemester_2023/gruppe-a-d/gruppe-d.git
git branch -M main
git push -uf origin main
git config --global user.name “vorname nachname”
git config --global user.email [email protected]
im Hauptordner, wo die Docker-Dateien liegen, ausführen per Kommandozeile
-
Allgemein:
- Anzeigen der laufenden Images:
docker image ls - Anzeigen der laufenden Container:
docker container ls -a - Anzeigen der aktuellen Volumes:
docker volume ls - Entfernen eines Images (per ID), z.B.
docker image rm <ID>(analgo für volumes) - Entfernen eines Containers (muss gestoppt sein):
docker rm <ID> - Bauen & Starten:
docker build -t my_image .
docker run my_image - mit automatischem Stoppen des Containers beim Beenden:
docker run --rm -p 4200:4200 -it my_image - Entfernen gestoppter Container:
docker system prune
- Anzeigen der laufenden Images:
-
bei uns:
- frontend:
docker run --rm -p 4200:4200 -it my_image
docker run --rm -p 4200:4200 -it image_frontend - backend:
docker build -t image_backend . -f Dockerfile_backend
docker run --rm -it image_backend
- frontend:
- Herstellen:
- Bilden per:
docker image save image_frontend -o docker_image_frontend.tar
docker image save image_backend -o docker_image_backend.tar
- Bilden per:
- Nutzen:
- Laden der tar mögl. per, d.h. hier:
docker load -i docker_image_frontend.tar
bzw.
docker load -i docker_image_backend.tar - danach normal starten mögl., d.h.
docker run --rm -p 4200:4200 -it image_frontend
bzw.
docker run --rm -it image_backend
- Laden der tar mögl. per, d.h. hier:
- Docker Images laden (z.B.
docker load -i docker_image_frontend.tar) oder erstellen (docker build -t image_backend . -f Dockerfile_backend)
! nicht starten = keindocker run-Kommando nötig . - wenn docker-compose.yml vorhanden ist:
docker compose up
in unserem Fall sollte das frontend wie üblich unter localhost:4200/ erreichbar sein; mit dem backend kommunizieren können und Daten werden im volume _data gespeichert
durch Stoppen (Ctrl+C), Löschen des backend-Containers und Neustarten vondocker compose upsollten dennoch keine Daten verloren gehen
Notizen:
- npm-Flags:
- -g = global
- --save = installs the package and updates the dependencies in package.json
- Warnings bei npm install durch -g [email protected] behoben (npm WARN deprecated @npmcli/[email protected]: This functionality has been moved to @npmcli/fs)
- Fehlermeldung aufgrund Internet-Verbindungs-Fehler:
- Inlining of fonts failed. An error has occurred while retrieving https://fonts.googleapis.com/css2?family=Roboto:wght@300;400;500&display=swap over the internet. getaddrinfo EAI_AGAIN fonts.googleapis.com
- db Error: Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
- Persistenz muss bestehen, wenn: docker container löschen, aber image nicht
.spec.ts (einfach in IntelliJ starten) -> korrigieren der Imports und ggf. Beispieluser für interne Seiten
starten in Kommandozeile (& ohne Browser): npm run test -- --no-watch --browsers=ChromeHeadlessCI --karma-config=./karma.conf.js
ohne MatInputModule entsteht der seltsame Fehler: Error: mat-form-field must contain a MatFormFieldControl.
- Invite team members and collaborators
- Create a new merge request
- Automatically close issues from merge requests
- Enable merge request approvals
- Automatically merge when pipeline succeeds
Use the built-in continuous integration in GitLab.
- Get started with GitLab CI/CD
- Analyze your code for known vulnerabilities with Static Application Security Testing(SAST)
- Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy
- Use pull-based deployments for improved Kubernetes management
- Set up protected environments
When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thank you to makeareadme.com for this template.
Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
Choose a self-explaining name for your project.
Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
If you have ideas for releases in the future, it is a good idea to list them in the README.
State if you are open to contributions and what your requirements are for accepting them.
For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
Show your appreciation to those who have contributed to the project.
For open source projects, say how it is licensed.
If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.