Why would you want to automatically deploy something; wouldn't that be the point of git hooks to build new releases based on master, and by branching out you still get CI. Or am i missing something?
How does a person use the cirlceci environment variables in their application code? Do you have to export via bash or can it be placed on process.env? Your explainer has been super helpful but i lost my path once I tried to introduce the api keys necessary for my application. Example would be in a file setting up an integration with a mail server I need the api key but want to deploy using my sandbox keys on my dev branch and production keys in prod. I understand how to split these up using circle contexts just cant seem to access them in my code. All help appreciated!!
Are you wanting to read the env variables while running your code in circle ci or wherever you deploy it? I think the env variables should be available on process.env automatically when you run it in circle ci
Hey Ben! Your resources on lerna and yarn workspaces have been really helpful to me, thanks! Detecting and deploying the package that changed at the end seems quite convoluted, wouldn't it be easier to do with `lerna changed` somehow. I could imagine running that at the beginning and then conditionally testing and deploying based on the result. Would be awesome if you could do a video on that!
Got it working without need for tags: github.com/chrisd08/circleci-monorepo/ Also in this fork I have a monorepo setup working on heroku so both frontend/server apps are hosted in the same place. (took forever to figure that out xd)
That's why I remain skeptical about monorepos. It's still a hell of a trouble to configure CI. But looks like you almost figured it out!
Why would you want to automatically deploy something; wouldn't that be the point of git hooks to build new releases based on master, and by branching out you still get CI. Or am i missing something?
yeah I sometimes question whether monorepos are really worth
what do you mean by branching out?
We can determine which project changed and deploy app that are only changed circleci.com/orbs/registry/orb/iynere/compare-url
How does a person use the cirlceci environment variables in their application code? Do you have to export via bash or can it be placed on process.env? Your explainer has been super helpful but i lost my path once I tried to introduce the api keys necessary for my application. Example would be in a file setting up an integration with a mail server I need the api key but want to deploy using my sandbox keys on my dev branch and production keys in prod. I understand how to split these up using circle contexts just cant seem to access them in my code. All help appreciated!!
Are you wanting to read the env variables while running your code in circle ci or wherever you deploy it?
I think the env variables should be available on process.env automatically when you run it in circle ci
@@bawad I got it sorted. I was really frustrated then but figured it out after a day or so. Running lerna based on this setup now.👍👍👍 thnx
Hey Ben! Your resources on lerna and yarn workspaces have been really helpful to me, thanks!
Detecting and deploying the package that changed at the end seems quite convoluted, wouldn't it be easier to do with `lerna changed` somehow. I could imagine running that at the beginning and then conditionally testing and deploying based on the result. Would be awesome if you could do a video on that!
lerna changed would be easier, but for some reason it not always accurate for me. Idk if I'm doing something wrong with it or something
what happens if packages are more than one version apart?
Which packages?
@@bawad never mind, I just read the lerna docs and it makes sense now
Got it working without need for tags: github.com/chrisd08/circleci-monorepo/
Also in this fork I have a monorepo setup working on heroku so both frontend/server apps are hosted in the same place. (took forever to figure that out xd)