What if we have two or more than three services and diferent urls for getting api things then what will we do in our environment .ts files???? and also in .env file
You can add more. Since the environment variable in environment.ts and environment.prod.ts are objects, you can create another key, e.g., ml_url and assign a value to it, e.g., process.env["NG_APP_ML_URL"]. Next, in your .env, add the NG_APP_ML_URL environment variable in a new line, e.g., NG_APP_ML_URL=localhost:8080 or NG_APP_ML_URL=localhost:5200/api/ml/
I can't say when was it exactly introduced, but Netlify has supported redirect configuration through redirects file for many years. For example, this is a post from 2017 (www.netlify.com/blog/2017/10/17/introducing-structured-redirects-and-headers/), of course the structure has changed a lot.
your tutorial really solved my issue that is in my publish directory
What if we have two or more than three services and diferent urls for getting api things then what will we do in our environment .ts files???? and also in .env file
You can add more. Since the environment variable in environment.ts and environment.prod.ts are objects, you can create another key, e.g., ml_url and assign a value to it, e.g., process.env["NG_APP_ML_URL"]. Next, in your .env, add the NG_APP_ML_URL environment variable in a new line, e.g., NG_APP_ML_URL=localhost:8080 or NG_APP_ML_URL=localhost:5200/api/ml/
This "redirects" file its new feature of Netlify, right?
I can't say when was it exactly introduced, but Netlify has supported redirect configuration through redirects file for many years. For example, this is a post from 2017 (www.netlify.com/blog/2017/10/17/introducing-structured-redirects-and-headers/), of course the structure has changed a lot.