generated from codinsonn/universal-app-router
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
chore: Move core files to '@green-stack/core' package workspace
- Loading branch information
Showing
63 changed files
with
247 additions
and
70 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,4 +1,46 @@ | ||
EXPO_PUBLIC_BASE_URL= | ||
EXPO_PUBLIC_BACKEND_URL= | ||
EXPO_PUBLIC_API_URL= | ||
EXPO_PUBLIC_GRAPH_URL= | ||
## --- Notes ----------------------------------------------------------------------------------- */ | ||
|
||
## -i- The `.env.example` file can be copied into `.env.local` using `npx turbo env:local` | ||
## -i- For more info, development, staging & production environments, check the expo docs: | ||
## -i- https://docs.expo.dev/guides/environment-variables/ | ||
|
||
## -i- Note that Expo will inline environment variables in your bundle during builds & deployments | ||
## -i- This means dynamically retrieving environment variables from e.g. `process.env[someKey]` will not work | ||
## -i- It also means that you should never include sensitive / private keys | ||
|
||
## -i- We suggest that for each environment variable you add here, you also add an entry in `appConfig.ts` | ||
## -i- There, you can add logic like ```envValue: process.env.EXPO_PUBLIC_ENV_KEY || process.env.NEXT_PUBLIC_ENV_KEY``` | ||
## -i- Where you would only define the EXPO_PUBLIC_ prefixed versions here in `.env.local` locally and using Expo UI for deployed envs | ||
|
||
## --- General --------------------------------------------------------------------------------- */ | ||
## -i- Env vars that should always be present & the same locally, independent of the simulated environment | ||
## --------------------------------------------------------------------------------------------- */ | ||
|
||
EXPO_PUBLIC_BASE_URL= # Keep empty in `.env.local` for maximum local testability, `appConfig.ts` will figure out back-end URL from expo-config | ||
EXPO_PUBLIC_BACKEND_URL= # Keep empty in `.env.local` for maximum local testability, `appConfig.ts` will figure out back-end URL from expo-config | ||
EXPO_PUBLIC_API_URL= # Keep empty in `.env.local` for maximum local testability, `appConfig.ts` will figure out back-end URL from expo-config | ||
EXPO_PUBLIC_GRAPH_URL= # Keep empty in `.env.local` for maximum local testability, `appConfig.ts` will figure out back-end URL from expo-config | ||
|
||
## --- LOCAL ----------------------------------------------------------------------------------- */ | ||
## -i- Defaults you might want to switch out for local development by commenting / uncommenting | ||
## --------------------------------------------------------------------------------------------- */ | ||
|
||
# EXAMPLE= # ... | ||
|
||
## --- DEV ------------------------------------------------------------------------------------- */ | ||
# -i- Uncomment while on development branch to simulate the dev environment | ||
## --------------------------------------------------------------------------------------------- */ | ||
|
||
# EXAMPLE= # ... | ||
|
||
## --- STAGE ----------------------------------------------------------------------------------- */ | ||
# -i- Uncomment while on staging branch to simulate the stage environment | ||
## --------------------------------------------------------------------------------------------- */ | ||
|
||
# EXAMPLE= # ... | ||
|
||
## --- PROD ------------------------------------------------------------------------------------ */ | ||
# -i- Uncomment while on main branch to simulate the production environment | ||
## --------------------------------------------------------------------------------------------- */ | ||
|
||
# EXAMPLE= # ... |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,4 +1,47 @@ | ||
## --- Notes ----------------------------------------------------------------------------------- */ | ||
|
||
## -i- The `.env.example` file can be copied into `.env.local` using `npx turbo env:local` | ||
## -i- For development, staging & production environments, check the next.js docs: | ||
## -i- https://nextjs.org/docs/app/building-your-application/configuring/environment-variables | ||
|
||
## -i- Note that you should treat environment variables as if they could be inlined in your bundle during builds & deployments | ||
## -i- This means dynamically retrieving environment variables from e.g. `process.env[someKey]` might not work | ||
## -i- It also means that you should never prefix with `NEXT_PUBLIC_` for sensitive / private keys | ||
|
||
## -i- We suggest that for each environment variable you add here, you also add an entry in `appConfig.ts` | ||
## -i- There, you can add logic like ```envValue: process.env.NEXT_PUBLIC_ENV_KEY || process.env.EXPO_PUBLIC_ENV_KEY``` | ||
## -i- Where you would only define the NEXT_PUBLIC_ prefixed versions here in `.env.local` locally and using Next.js UI for deployed envs | ||
## -i- For environment variables you only be available server-side, you can omit `NEXT_PUBLIC_` | ||
|
||
## --- General --------------------------------------------------------------------------------- */ | ||
## -i- Env vars that should always be present & the same locally, independent of the simulated environment | ||
## --------------------------------------------------------------------------------------------- */ | ||
|
||
NEXT_PUBLIC_BASE_URL=http://localhost:3000 | ||
NEXT_PUBLIC_BACKEND_URL=http://localhost:3000 | ||
NEXT_PUBLIC_API_URL=http://localhost:3000/api | ||
NEXT_PUBLIC_GRAPH_URL=http://localhost:3000/api/graphql | ||
|
||
## --- LOCAL ----------------------------------------------------------------------------------- */ | ||
## -i- Defaults you might want to switch out for local development by commenting / uncommenting | ||
## --------------------------------------------------------------------------------------------- */ | ||
|
||
# DB_URL= # TODO: Add DB layer connection for full local dev... | ||
|
||
## --- DEV ------------------------------------------------------------------------------------- */ | ||
# -i- Uncomment while on development branch to simulate the dev environment | ||
## --------------------------------------------------------------------------------------------- */ | ||
|
||
# DB_URL= # TODO: Add DB layer connection for the dev environment... | ||
|
||
## --- STAGE ----------------------------------------------------------------------------------- */ | ||
# -i- Uncomment while on staging branch to simulate the stage environment | ||
## --------------------------------------------------------------------------------------------- */ | ||
|
||
# DB_URL= # TODO: Add DB layer connection for the stage environment... | ||
|
||
## --- PROD ------------------------------------------------------------------------------------ */ | ||
# -i- Uncomment while on main branch to simulate the production environment | ||
## --------------------------------------------------------------------------------------------- */ | ||
|
||
# DB_URL= # TODO: Add DB layer connection for the production environment... |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes
4 changes: 2 additions & 2 deletions
4
features/app-core/components/styled.tsx → features/@app-core/components/styled.tsx
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes.
File renamed without changes.
File renamed without changes.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
2 changes: 1 addition & 1 deletion
2
features/app-core/routes/index.tsx → features/@app-core/routes/index.tsx
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
4 changes: 2 additions & 2 deletions
4
features/app-core/screens/SlugScreen.tsx → features/@app-core/screens/SlugScreen.tsx
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
4 changes: 2 additions & 2 deletions
4
...pp-core/screens/UniversalAppProviders.tsx → ...pp-core/screens/UniversalAppProviders.tsx
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes.
File renamed without changes.
File renamed without changes.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.