Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🪟 🔧 Add a start:cloud command to the webapp #19026

Merged
merged 2 commits into from
Nov 7, 2022
Merged

Conversation

timroes
Copy link
Collaborator

@timroes timroes commented Nov 7, 2022

What

This adds a start:cloud command to the webapp. This makes it easier for employees to run the webapp in cloud mode, by simply running npm run start:cloud.

The existing npm start command will continue to work as it does today.

How

The corresponding files will be checked into the (private) airbyte-cloud repository: https://github.com/airbytehq/airbyte-cloud/pull/3391

When running the command the environment.js file will check if the airbyte-cloud repository is checked out in parallel (thus the file exists), and if so use dotenv to load it. This replaces the need for having any .env.development file we need to copy around.

Given that we can use different ports in those environment files (as the above linked PR already does), we can run Cloud and OSS also more easily in parallel in the future.

@timroes timroes added team/compose area/frontend Related to the Airbyte webapp ui/tooling labels Nov 7, 2022
@timroes timroes requested a review from a team as a code owner November 7, 2022 12:28
@github-actions github-actions bot added the area/platform issues related to the platform label Nov 7, 2022
@timroes timroes changed the title Add a start:cloud command to the webapp 🪟 🔧 Add a start:cloud command to the webapp Nov 7, 2022
@@ -9,6 +9,8 @@
"prepare": "cd .. && husky install airbyte-webapp/.husky",
"prestart": "npm run generate-client",
"start": "craco start",
"prestart:cloud": "npm run generate-client",
"start:cloud": "AB_ENV=frontend-dev node -r ./scripts/environment.js ./node_modules/.bin/craco start",
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ℹ️ Using AB_ENV here (we use AB across infra more commonly as an abbreviation of Airbyte), to not collide with the standardized ENV variable for production vs development.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Somehow I had not yet realized what AB signified 😅

Copy link
Contributor

@josephkmh josephkmh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice improvement! 🎉

@@ -9,6 +9,8 @@
"prepare": "cd .. && husky install airbyte-webapp/.husky",
"prestart": "npm run generate-client",
"start": "craco start",
"prestart:cloud": "npm run generate-client",
"start:cloud": "AB_ENV=frontend-dev node -r ./scripts/environment.js ./node_modules/.bin/craco start",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Somehow I had not yet realized what AB signified 😅

airbyte-webapp/scripts/environment.js Outdated Show resolved Hide resolved
@timroes timroes merged commit 8969824 into master Nov 7, 2022
@timroes timroes deleted the tim/cloud-start branch November 7, 2022 13:52
letiescanciano added a commit that referenced this pull request Nov 7, 2022
* master:
  🪟 🎨 Adapt Osano banner to new UI (#19029)
  🪟 🔧 Add a start:cloud command to the webapp (#19026)
  🪟🧪 [Experiment] Move OAuth to top of signup page (#18899)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/frontend Related to the Airbyte webapp area/platform issues related to the platform team/compose
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants