This repository configures a Spring Initializr instance with a custom UI
running at https://start.spring.io. The UI is a server-side
Vaadin Flow application hosted inside start-site.
The following modules are available:
-
start-site: server infrastructure, metadata configuration, and the Vaadin UI -
start-site-verification: tests to verify the validity of the metadata
There is a dedicated page that describes how you can interact with the service.
You need Java 17 and a bash-like shell.
Invoke the build at the root of the project
$ ./mvnw clean install
The project also includes a number of longer-running verification tests. They
can be built and run using the verification profile:
$ ./mvnw -Pverification clean install
The project’s other tests are not included in the verification profile. All of
the project’s tests can be run using the full profile:
$ ./mvnw -Pfull clean install
For a production build that includes Vaadin’s optimized frontend bundle, enable
the production profile:
$ ./mvnw -Pproduction clean install
You can start the app as any other Spring Boot app. In development mode Vaadin provisions Node + Vite on first run, so this also doubles as a frontend dev server:
$ cd start-site $ ../mvnw spring-boot:run
You should be able to import the project into your IDE with no problems. Once there you
can run the StartApplication from its main method and debug it. If you also need to
work on the library, adding the initializr project in your workspace would make sure
to reload the app whenever you make any change.
This is the recommended way to operate while you are developing the application, especially the UI.
This instance has a thin layer with our opinions about getting started with Spring Boot. You can reuse them but please keep in mind that this is not supported with the same level as the Spring Initializr library. The Web UI, in particular, is for our own purpose and is not particularly engineered to be easily extended.
If you are on a Mac and using homebrew, install the Cloud Foundry CLI:
$ brew install cloudfoundry-cli
Alternatively, download a suitable binary for your platform from Pivotal Web Services.
You should ensure that the application name and URL (name and host values) are
suitable for your environment before running cf push.
First, make sure that you have built the application, then make sure first that the jar has been created:
$ cd start-site $ ../mvnw package
The project creates a regular library jar and a repackaged archive that can be used to
start the application with the exec classifier. Once the build as completed, you can
push the application:
$ cf push your-start -p target/start-site-exec.jar
The start.spring.io website is Open Source software released under the Apache 2.0 license.