WT-Tech-Tree-Maker VS JHipster

As you might guess from the vehicles included, Rank VIII ground battles would start involving a lot of powerful fire-and-forget ATGMs. However, access to soft- and hard-kill APS would become commonplace at the same time. If you have any other questions or suggestions in regards to these vehicles, feel free to comment. And as always, thanks to the WT Tree Maker Tool for making these graphics possible.

Included in the image gallery is also a number of unfinished designs which were too cool not to mention. Also, here are the links to the wonderful WT Tree Maker tool used to make the interactive version and the Yugoslav Tech Tree Discord Server, where we discuss the country’s vehicles and coordinate suggestions for them in the forums.

This is by no means a definitive chart, just an old project for fun of mine that I polished once I heard Rank VIII was coming. Similar creations have been made before, but usually only for the USA. As for BRs, they are estimates and definitely up for debate. If you have any criticism for the placements and want to explain how X plane would be completely overpowered because of a capability I wasn't aware of, feel free. Same for if you have an aircraft that you think is missing. Thanks to the wonderful WT Tree Maker for making it possible to present this so nicely. PS: Fifth-gen fighters are greyed out because if you want to give every nation a competitive plane at that level, you would end up with a bunch of F-35s fighting each other and some nations wouldn't have a fifth gen to begin with. See you in a few years when technology has advanced and more countries start actually producing their own variants.

Also, if you didn’t know already, there’s a great software for making these kinds of tech trees, made by u/zanju13

This came after months of on-and-off research, and I want to thank people who posted info and suggestions online (as I was by no means the first to try and make such a tree) as well as the WT Tree Maker tool. If you have a keen interest in Yugoslav vehicles, we have made a new server to discuss them and coordinate suggestions for them in the WT forums: https://discord.gg/25yjTRabSP. Below this comment is some extra info if you are interested. See you when the air tree is ready!

The tool I used to make tech tree

Take a look at my tech tree generator, might help you with that too ;) https://github.com/przemyslaw-zan/WT-Tech-Tree-Maker

Homepage

JHipster: A development platform for generating, developing, and deploying full-stack web applications based on Spring Boot and front-end frameworks like Angular, React, or Vue.

An easy way to get a pre-configured Keycloak instance is to use JHipster's jhipster-sample-app-oauth2 application. It gets updated with every JHipster release. You can clone it with the following command:

provider "auth0" { domain = "https://" debug = false } # Create a new Auth0 application for the JHipster app resource "auth0_client" "java_ms_client" { name = "JavaMicroservices" description = "Java Microservices Client Created Through Terraform" app_type = "regular_web" callbacks = ["http://localhost:8080/login/oauth2/code/oidc"] allowed_logout_urls = ["http://localhost:8080"] oidc_conformant = true jwt_configuration { alg = "RS256" } } # Configuring client_secret_post as an authentication method. resource "auth0_client_credentials" "java_ms_client_creds" { client_id = auth0_client.java_ms_client.id authentication_method = "client_secret_post" } # Create roles for the JHipster app resource "auth0_role" "admin" { name = "ROLE_ADMIN" description = "Administrator" } resource "auth0_role" "user" { name = "ROLE_USER" description = "User" } # Create an action to customize the authentication flow to add the roles and the username to the access token claims expected by JHipster applications. resource "auth0_action" "jhipster_action" { name = "jhipster_roles_claim" runtime = "node18" deploy = true code = <<-EOT /** * Handler that will be called during the execution of a PostLogin flow. * * @param {Event} event - Details about the user and the context in which they are logging in. * @param {PostLoginAPI} api - Interface whose methods can be used to change the behavior of the login. */ exports.onExecutePostLogin = async (event, api) => { const namespace = 'https://www.jhipster.tech'; if (event.authorization) { api.idToken.setCustomClaim(namespace + '/roles', event.authorization.roles); api.accessToken.setCustomClaim(namespace + '/roles', event.authorization.roles); } }; EOT supported_triggers { id = "post-login" version = "v3" } } # Attach the action to the login flow resource "auth0_trigger_actions" "login_flow" { trigger = "post-login" actions { id = auth0_action.jhipster_action.id display_name = auth0_action.jhipster_action.name } } # Create a test user. You can create more users here if needed resource "auth0_user" "test_user" { connection_name = "Username-Password-Authentication" name = "Jane Doe" email = "[email protected]" email_verified = true password = "passpass$12$12" # Don't set passwords like this in production! Use env variables instead. lifecycle { ignore_changes = [roles] } } resource "auth0_user_roles" "test_user_roles" { user_id = auth0_user.test_user.id roles = [auth0_role.admin.id, auth0_role.user.id] } output "auth0_webapp_client_id" { description = "Auth0 JavaMicroservices Client ID" value = auth0_client.java_ms_client.client_id } output "auth0_webapp_client_secret" { description = "Auth0 JavaMicroservices Client Secret" value = auth0_client_credentials.java_ms_client_creds.client_secret sensitive = true }

If you want a Spring backend with an Angular Frontend check out https://www.jhipster.tech. This is very nice for CRUD stuff.

Use https://www.jhipster.tech/

To test GitHub Actions, we need a new project which in this case I generated using JHipster with the configuration seen here:

exports.onExecutePostLogin = async (event, api) => { const namespace = 'https://www.jhipster.tech'; if (event.authorization) { api.idToken.setCustomClaim('preferred_username', event.user.email); api.idToken.setCustomClaim(`${namespace}/roles`, event.authorization.roles); api.accessToken.setCustomClaim(`${namespace}/roles`, event.authorization.roles); } }

What you maybe asking for is something like vaadin or jhipster which marries the front with the backend. (I don't like them tbh but it worth mentioning)