Base solution for your next web application
Starts in:
01 DAYS
01 HRS
01 MIN
01 SEC

Activities of "josefernandez"

Hello,

I was able to deploy, both aspnet-core and angular. I ran into a couple of issue which forced me to modify the appconfig.json in the angular application. I had to change from localhost to the actual real url that I am using.

My question is, how do you deal with multiple appconfig.json files based on the environment. I have for the aspnet-core three environments, dev, staging and production and it works flawlessly. I can't say the same about the angular piece.

I can't do local development without modifying the appconfig.json (localhost:4200, etc). Then I have to change it back to the original values. Annoying.

I know I can use some sort of "hack" so that I have appconfig.dev.json and then during deployment, overwrite the appconfig.json with the corresponding one under any environment.

Is there a way to achieve this painlessly?

Thanks.

I ran into the same issue and i didn't do a "yarn upgrade". What I did was to add the project to my Bitbucket account (from Windows 10) then pull the project in my laptop (MAC) and this happened.

I think it would be ideal from a development perspective to prepare a vagrant file. Just a thought.

Showing 1 to 2 of 2 entries