kandi background
Explore Kits

urlaubsverwaltung | Schluss mit Papierchaos und langweiliger Software | Addon library

 by   synyx Java Version: urlaubsverwaltung-4.37.0 License: Apache-2.0

 by   synyx Java Version: urlaubsverwaltung-4.37.0 License: Apache-2.0

Download this library from

kandi X-RAY | urlaubsverwaltung Summary

urlaubsverwaltung is a Java library typically used in Plugin, Addon applications. urlaubsverwaltung has no bugs, it has no vulnerabilities, it has build file available, it has a Permissive License and it has low support. You can download it from GitHub.
Die Urlaubsverwaltung ist eine Web-Anwendung, um Abwesenheiten elektronisch verwalten zu können. Anhand von Urlaubsanträgen kann ein Mitarbeiter eine Anfrage stellen, die von den jeweils berechtigten Personen genehmigt, abgelehnt oder storniert werden kann. Jeder Mitarbeiter kann seine Überstunden pflegen, um immer den Überblick zu behalten und falls doch mal eine Person ausfallen sollte, so kann die Krankmeldung direkt gepflegt werden. Wenn du mehr Informationen und Bilder über dieses Projekt sehen möchtest dann schaue auf unserer Landingpage vorbei.
Support
Support
Quality
Quality
Security
Security
License
License
Reuse
Reuse

kandi-support Support

  • urlaubsverwaltung has a low active ecosystem.
  • It has 193 star(s) with 71 fork(s). There are 29 watchers for this library.
  • There were 10 major release(s) in the last 12 months.
  • There are 111 open issues and 934 have been closed. On average issues are closed in 45 days. There are 9 open pull requests and 0 closed requests.
  • It has a neutral sentiment in the developer community.
  • The latest version of urlaubsverwaltung is urlaubsverwaltung-4.37.0
urlaubsverwaltung Support
Best in #Addon
Average in #Addon
urlaubsverwaltung Support
Best in #Addon
Average in #Addon

quality kandi Quality

  • urlaubsverwaltung has 0 bugs and 0 code smells.
urlaubsverwaltung Quality
Best in #Addon
Average in #Addon
urlaubsverwaltung Quality
Best in #Addon
Average in #Addon

securitySecurity

  • urlaubsverwaltung has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
  • urlaubsverwaltung code analysis shows 0 unresolved vulnerabilities.
  • There are 0 security hotspots that need review.
urlaubsverwaltung Security
Best in #Addon
Average in #Addon
urlaubsverwaltung Security
Best in #Addon
Average in #Addon

license License

  • urlaubsverwaltung is licensed under the Apache-2.0 License. This license is Permissive.
  • Permissive licenses have the least restrictions, and you can use them in most projects.
urlaubsverwaltung License
Best in #Addon
Average in #Addon
urlaubsverwaltung License
Best in #Addon
Average in #Addon

buildReuse

  • urlaubsverwaltung releases are available to install and integrate.
  • Build file is available. You can build the component from source.
  • Installation instructions, examples and code snippets are available.
  • It has 74189 lines of code, 5096 functions and 954 files.
  • It has medium code complexity. Code complexity directly impacts maintainability of the code.
urlaubsverwaltung Reuse
Best in #Addon
Average in #Addon
urlaubsverwaltung Reuse
Best in #Addon
Average in #Addon
Top functions reviewed by kandi - BETA

kandi has reviewed urlaubsverwaltung and discovered the below as its top functions. This is intended to give you an instant insight into urlaubsverwaltung implemented functionality, and help decide if they suit your requirements.

  • Obtains a list of months based on the month range .
    • Extract a LdapUser from a context .
      • Export a list of ApplicationForLeaveStatistics .
        • Connect to the exchange server .
          • Sets the detail view for the user .
            • Creates the application .
              • Start the downloader .
                • Validate application for leave .
                  • Returns true if there are enough vacation days left .
                    • Converts an absence into a VEvent object .

                      Get all kandi verified functions for this library.

                      Get all kandi verified functions for this library.

                      urlaubsverwaltung Key Features

                      Demo-System

                      FAQ

                      Berechtigungen

                      Betrieb Konfiguration

                      Demodaten Modus

                      Entwicklung

                      urlaubsverwaltung Examples and Code Snippets

                      See all related Code Snippets

                      Download

                      copy iconCopydownload iconDownload
                      java -jar urlaubsverwaltung.war
                      

                      Konfiguration

                      copy iconCopydownload iconDownload
                      # account
                      uv.account.default-vacation-days=20 # deprecated - kann über 'Einstellungen' gesetzt werden wenn auf '-1' gesetzt
                      uv.account.update.cron=0 0 5 1 1 *
                      
                      # application
                      uv.application.reminder-notification.cron=0 0 7 * * *
                      uv.application.upcoming-holiday-replacement-notification.cron=0 0 7 * * *
                      uv.application.upcoming-notification.cron=0 0 7 * * *
                      
                      # ical calendar
                      uv.calendar.organizer
                      uv.calendar.refresh-interval=P1D
                      
                      # development
                      uv.development.demodata.create=false
                      uv.development.demodata.additional-active-user=0
                      uv.development.demodata.additional-inactive-user=0
                      
                      # mail
                      uv.mail.administrator
                      uv.mail.application-url
                      uv.mail.sender
                      uv.mail.senderDisplayName=Urlaubsverwaltung
                      
                      # security
                      uv.security.auth=default
                      
                      uv.security.directory-service.identifier
                      uv.security.directory-service.last-name
                      uv.security.directory-service.first-name
                      uv.security.directory-service.mail-address
                      uv.security.directory-service.sync.cron=0 0 1 * * ?
                      uv.security.directory-service.filter.member-of
                      uv.security.directory-service.filter.object-class=person
                      
                      ## active directory
                      uv.security.directory-service.active-directory.url=ldap://ad.example.org/
                      uv.security.directory-service.active-directory.domain=example.org
                      uv.security.directory-service.active-directory.searchFilter=
                      uv.security.directory-service.active-directory.sync.enabled=false
                      uv.security.directory-service.active-directory.sync.password=password
                      uv.security.directory-service.active-directory.sync.user-dn=cn=Administrator,cn=users,dc=example,dc=org
                      uv.security.directory-service.active-directory.sync.user-search-base=dc=example,dc=org
                      
                      ## ldap
                      uv.security.directory-service.ldap.url=ldap://ldap.example.org/
                      uv.security.directory-service.ldap.base=dc=example,dc=org
                      uv.security.directory-service.ldap.manager-dn
                      uv.security.directory-service.ldap.manager-password
                      uv.security.directory-service.ldap.user-search-filter=(uid={0})
                      uv.security.directory-service.ldap.user-search-base=ou=accounts
                      uv.security.directory-service.ldap.sync.enabled=false
                      uv.security.directory-service.ldap.sync.password=password
                      uv.security.directory-service.ldap.sync.user-dn=uid=username,ou=other,ou=accounts,dc=example,dc=org
                      uv.security.directory-service.ldap.sync.user-search-base=ou=people,ou=accounts
                      
                      # oidc (openid connect)
                      uv.security.oidc.client-id
                      uv.security.oidc.client-secret
                      uv.security.oidc.issuer-uri
                      uv.security.oidc.logout-uri
                      uv.security.oidc.scopes=openid,profile,email
                      
                      # jsp template engine
                      uv.template-engine.jsp.use-precompiled=false
                      
                      # sick-note
                      uv.sick-note.end-of-pay-notification.cron=0 0 6 * * *
                      
                      # workingtime - deprecated - kann über 'Einstellungen' gesetzt werden 
                      # wenn auf uv.workingtime.default-working-days[0]=-1 gesetzt
                      # (monday till friday)
                      uv.workingtime.default-working-days[0]=1
                      uv.workingtime.default-working-days[1]=2
                      uv.workingtime.default-working-days[2]=3
                      uv.workingtime.default-working-days[3]=4
                      uv.workingtime.default-working-days[4]=5
                      

                      Starten der Anwendung im Demodaten-Modus

                      copy iconCopydownload iconDownload
                      docker-compose up
                      

                      Repository clonen

                      copy iconCopydownload iconDownload
                      git clone git@github.com:synyx/urlaubsverwaltung.git
                      

                      git hooks (optional)

                      copy iconCopydownload iconDownload
                      ./scripts/install-git-hooks.sh
                      

                      Anwendung starten

                      copy iconCopydownload iconDownload
                      docker-compose up
                      

                      Frontend Entwicklung

                      copy iconCopydownload iconDownload
                      <%@taglib prefix="asset" uri = "/WEB-INF/asset.tld"%>
                      
                      <script defer src="<asset:url value='npm.jquery.js' />"></script>
                      

                      Release

                      copy iconCopydownload iconDownload
                      export RELEASE_VERSION=0.10.0
                      export NEW_VERSION=0.11.0-SNAPSHOT
                      ./release.sh
                      git fetch
                      

                      See all related Code Snippets

                      Community Discussions

                      Trending Discussions on Addon
                      • Microk8s dashboard using nginx-ingress via http not working (Error: `no matches for kind "Ingress" in version "extensions/v1beta1"`)
                      • Type Error: this.getOptions is not a function For style-loader
                      • Global SCSS style is no longer loaded in Storybook with Angular 12
                      • Storybook error when using Webpack5 with Next.JS app + Typescript
                      • Colab: (0) UNIMPLEMENTED: DNN library is not found
                      • Minikube dashboard ingress
                      • NPM CI error bindings not accessible from watchpack-chokidar2:fsevents
                      • What should the result be when assigning a variable to a reference to itself, in-between modified and then returned by a function call?
                      • How to penetrate or cut holes through a 2D foreground
                      • Linking local Openssl to Nodejs C++ addon
                      Trending Discussions on Addon

                      QUESTION

                      Microk8s dashboard using nginx-ingress via http not working (Error: `no matches for kind "Ingress" in version "extensions/v1beta1"`)

                      Asked 2022-Apr-01 at 07:26

                      I have microk8s v1.22.2 running on Ubuntu 20.04.3 LTS.

                      Output from /etc/hosts:

                      127.0.0.1 localhost
                      127.0.1.1 main
                      

                      Excerpt from microk8s status:

                      addons:
                        enabled:
                          dashboard            # The Kubernetes dashboard
                          ha-cluster           # Configure high availability on the current node
                          ingress              # Ingress controller for external access
                          metrics-server       # K8s Metrics Server for API access to service metrics
                      

                      I checked for the running dashboard (kubectl get all --all-namespaces):

                      NAMESPACE     NAME                                             READY   STATUS    RESTARTS   AGE
                      kube-system   pod/calico-node-2jltr                            1/1     Running   0          23m
                      kube-system   pod/calico-kube-controllers-f744bf684-d77hv      1/1     Running   0          23m
                      kube-system   pod/metrics-server-85df567dd8-jd6gj              1/1     Running   0          22m
                      kube-system   pod/kubernetes-dashboard-59699458b-pb5jb         1/1     Running   0          21m
                      kube-system   pod/dashboard-metrics-scraper-58d4977855-94nsp   1/1     Running   0          21m
                      ingress       pod/nginx-ingress-microk8s-controller-qf5pm      1/1     Running   0          21m
                      
                      NAMESPACE     NAME                                TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)    AGE
                      default       service/kubernetes                  ClusterIP   10.152.183.1     <none>        443/TCP    23m
                      kube-system   service/metrics-server              ClusterIP   10.152.183.81    <none>        443/TCP    22m
                      kube-system   service/kubernetes-dashboard        ClusterIP   10.152.183.103   <none>        443/TCP    22m
                      kube-system   service/dashboard-metrics-scraper   ClusterIP   10.152.183.197   <none>        8000/TCP   22m
                      
                      NAMESPACE     NAME                                               DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR            AGE
                      kube-system   daemonset.apps/calico-node                         1         1         1       1            1           kubernetes.io/os=linux   23m
                      ingress       daemonset.apps/nginx-ingress-microk8s-controller   1         1         1       1            1           <none>                   22m
                      
                      NAMESPACE     NAME                                        READY   UP-TO-DATE   AVAILABLE   AGE
                      kube-system   deployment.apps/calico-kube-controllers     1/1     1            1           23m
                      kube-system   deployment.apps/metrics-server              1/1     1            1           22m
                      kube-system   deployment.apps/kubernetes-dashboard        1/1     1            1           22m
                      kube-system   deployment.apps/dashboard-metrics-scraper   1/1     1            1           22m
                      
                      NAMESPACE     NAME                                                   DESIRED   CURRENT   READY   AGE
                      kube-system   replicaset.apps/calico-kube-controllers-69d7f794d9     0         0         0       23m
                      kube-system   replicaset.apps/calico-kube-controllers-f744bf684      1         1         1       23m
                      kube-system   replicaset.apps/metrics-server-85df567dd8              1         1         1       22m
                      kube-system   replicaset.apps/kubernetes-dashboard-59699458b         1         1         1       21m
                      kube-system   replicaset.apps/dashboard-metrics-scraper-58d4977855   1         1         1       21m
                      

                      I want to expose the microk8s dashboard within my local network to access it through http://main/dashboard/

                      To do so, I did the following nano ingress.yaml:

                      apiVersion: extensions/v1beta1
                      kind: Ingress
                      metadata:
                        annotations:
                          kubernetes.io/ingress.class: public
                          nginx.ingress.kubernetes.io/backend-protocol: "HTTPS"
                        name: dashboard
                        namespace: kube-system
                      spec:
                        rules:
                        - host: main
                          http:
                            paths:
                            - backend:
                                serviceName: kubernetes-dashboard
                                servicePort: 443
                              path: /
                      

                      Enabling the ingress-config through kubectl apply -f ingress.yaml gave the following error:

                      error: unable to recognize "ingress.yaml": no matches for kind "Ingress" in version "extensions/v1beta1"
                      

                      Help would be much appreciated, thanks!

                      Update: @harsh-manvar pointed out a mismatch in the config version. I have rewritten ingress.yaml to a very stripped down version:

                      apiVersion: networking.k8s.io/v1
                      kind: Ingress
                      metadata:
                        name: dashboard
                        namespace: kube-system
                      spec:
                        rules:
                        - http:
                            paths:
                            - path: /dashboard
                              pathType: Prefix
                              backend:
                                service:
                                  name: kubernetes-dashboard
                                  port:
                                    number: 443
                      

                      Applying this works. Also, the ingress rule gets created.

                      NAMESPACE     NAME        CLASS    HOSTS   ADDRESS     PORTS   AGE
                      kube-system   dashboard   public   *       127.0.0.1   80      11m
                      

                      However, when I access the dashboard through http://<ip-of-kubernetes-master>/dashboard, I get a 400 error.

                      Log from the ingress controller:

                      192.168.0.123 - - [10/Oct/2021:21:38:47 +0000] "GET /dashboard HTTP/1.1" 400 54 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/94.0.4606.71 Safari/537.36" 466 0.002 [kube-system-kubernetes-dashboard-443] [] 10.1.76.3:8443 48 0.000 400 ca0946230759edfbaaf9d94f3d5c959a
                      

                      Does the dashboard also need to be exposed using the microk8s proxy? I thought the ingress controller would take care of this, or did I misunderstand this?

                      ANSWER

                      Answered 2021-Oct-10 at 18:29
                      error: unable to recognize "ingress.yaml": no matches for kind "Ingress" in version "extensions/v1beta1"
                      

                      it' due to the mismatch in the ingress API version.

                      You are running the v1.22.2 while API version in YAML is old.

                      Good example : https://kubernetes.io/docs/tasks/access-application-cluster/ingress-minikube/

                      you are using the older ingress API version in your YAML which is extensions/v1beta1.

                      You need to change this based on ingress version and K8s version you are running.

                      This is for version 1.19 in K8s and will work in 1.22 also

                      Example :

                      apiVersion: networking.k8s.io/v1
                      kind: Ingress
                      metadata:
                        name: minimal-ingress
                        annotations:
                          nginx.ingress.kubernetes.io/rewrite-target: /
                      spec:
                        rules:
                        - http:
                            paths:
                            - path: /testpath
                              pathType: Prefix
                              backend:
                                service:
                                  name: test
                                  port:
                                    number: 80
                      

                      Source https://stackoverflow.com/questions/69517855

                      Community Discussions, Code Snippets contain sources that include Stack Exchange Network

                      Vulnerabilities

                      No vulnerabilities reported

                      Install urlaubsverwaltung

                      Die Anwendung steht als. Nach der Konfiguration lässt sich die Urlaubsverwaltung starten. Falls es Probleme beim Starten der Anwendung gibt, ist es hilfreich das Logging der Anwendung zu konfigurieren, damit erhält man mehr Informationen über den Fehlerzustand. Alle Informationen zum Betrieb mit unserem Docker Image sind im Ordner .example zu finden.
                      Web Application Archive (.war)
                      Docker Image
                      Konfiguration Datenbank
                      Konfiguration Security Provider
                      Lege ein Verzeichnis für die Urlaubsverwaltung an (z.B. /opt/urlaubsverwaltung). Kopiere die .war-Datei dorthin.
                      Erstelle in dem Verzeichnis eine Konfigurationsdatei namens application.properties, welche die Konfiguration für die Urlaubsverwaltung enthält und die Standardwerte überschreibt. Die vollständigen Konfigurationsoptionen sind unter Konfiguration dokumentiert.

                      Support

                      For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

                      DOWNLOAD this Library from

                      Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from
                      over 430 million Knowledge Items
                      Find more libraries
                      Reuse Solution Kits and Libraries Curated by Popular Use Cases
                      Explore Kits

                      Save this library and start creating your kit

                      Explore Related Topics

                      Share this Page

                      share link
                      Consider Popular Addon Libraries
                      Try Top Libraries by synyx
                      Compare Addon Libraries with Highest Support
                      Compare Addon Libraries with Highest Quality
                      Compare Addon Libraries with Highest Security
                      Compare Addon Libraries with Permissive License
                      Compare Addon Libraries with Highest Reuse
                      Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from
                      over 430 million Knowledge Items
                      Find more libraries
                      Reuse Solution Kits and Libraries Curated by Popular Use Cases
                      Explore Kits

                      Save this library and start creating your kit

                      • © 2022 Open Weaver Inc.