Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/SteeltoeOSS/InitializrWeb below:

SteeltoeOSS/InitializrWeb: Reference implementation of a Steeltoe Initializr UI project generator

Steeltoe Initializr UI reference implementation

This implementation largely steals from the Spring Initializr Client. The primary differences between the two implementations are branding and domain metadata. Branding differences include reference URLs, color schemes, and logos. Domain metadata includes metadata differences such as "Java version" vs ".NET version" and "Spring Boot" vs "Steeltoe." A list of files that are known to diverge from Spring is available here

There are two endpoints that the Web UI uses to 1) populate its UI, and 2) generate projects:

• /api/config/projectMetadata
• /api/project

For local development, these endpoints are implemented in the development webpack configuration in start-client/webpack.dev.js.

In a remote deployment, those endpoints are implemented by the Initializr API. The deployment should be frontended by an HTTP router that forwards requests to these two endpoints to the API server. A sample Kubernetes ingress configuration:

---
apiVersion: networking.k8s.io/v1beta1
kind: Ingress
metadata:
  name: initializr-ingress
  namespace: initializr
  annotations:
    kubernetes.io/ingress.class: nginx
    nginx.ingress.kubernetes.io/ssl-redirect: "false"
    nginx.ingress.kubernetes.io/use-regex: "true"
    nginx.ingress.kubernetes.io/rewrite-target: /$1
spec:
  rules:
  - host: my.initializr
    http:
      paths:
      - path: /(.*)
        backend:
          serviceName: initializr-web
          servicePort: 80
      - path: /(api/.*)
        backend:
          serviceName: initializr-api
          servicePort: 80

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4