Skip to content

Commit

Permalink
fix - skeet init
Browse files Browse the repository at this point in the history
  • Loading branch information
POPPIN-FUMI committed Apr 11, 2024
1 parent fd57981 commit e8b0b4b
Show file tree
Hide file tree
Showing 3 changed files with 7 additions and 7 deletions.
2 changes: 1 addition & 1 deletion packages/cli/src/cli/ai/skeetPrompt.ts
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ import { Example } from '@skeet-framework/ai'
export const skeetAiPrompt = async (): Promise<Example> => {
return {
context: `You are a senior engineer specialized in assisting developers. You have deep expertise in the Skeet framework, which is a platform for building web applications. Additionally, you are proficient in TypeScript and have a comprehensive understanding of the Google Cloud Platform. You are also familiar with the Firebase Emulator Suite.
To successfully set up Skeet Cloud, users must progress through a series of seven steps, each associated with a specific status indicated in the ./skeet-cloud.config.json file. This file also contains the app.name, app.projectId, app.projectId which is crucial for naming the Google Cloud and Firebase projects. Below is a guide detailing each step and the actions required to reach the next status:
To successfully set up Skeet Cloud, users must progress through a series of seven steps, each associated with a specific status indicated in the ./skeet-cloud.config.json file. This file also contains the app.name, app.projectId which is crucial for naming the Google Cloud and Firebase projects. Below is a guide detailing each step and the actions required to reach the next status:
1. NOT_CREATED - Immediately after creating your project, initiate the setup by creating a Google Cloud Project and a Firebase Project. Both should have the name specified in the app.name field of your ./skeet-cloud.config.json file. Detailed instructions for this step can be found at: https://skeet.dev/en/doc/skeet-firestore/setup/
2. PROJECT_CREATED - Once the projects are created, proceed to set up your first Firebase Functions by executing the command:\n\n $ skeet deploy
3. FUNCTIONS_CREATED - After setting up Firebase Functions, the next step is to configure Github Actions for continuous integration and delivery. This is also done using the same command: $ skeet init --repo
Expand Down
9 changes: 5 additions & 4 deletions packages/cli/src/cli/sub/sync/syncTaskQueue.ts
Original file line number Diff line number Diff line change
@@ -1,12 +1,13 @@
import { sleep } from '@/utils/time'
import { importConfig, setGcloudProject } from '@/lib'
import { setGcloudProject } from '@/lib'
import { addTaskQueue } from '../add/addTaskQueue'
import { readOrCreateConfig } from '@/config/readOrCreateConfig'

export const syncTaskQueue = async () => {
const skeetConfig = await importConfig()
const skeetConfig = await readOrCreateConfig()
await setGcloudProject(skeetConfig.app.projectId)
if (skeetConfig.taskQueues) {
for await (const taskQueue of skeetConfig.taskQueues) {
if (skeetConfig.taskQueue) {
for await (const taskQueue of skeetConfig.taskQueue) {
const isUpdate = true
await addTaskQueue(
skeetConfig.app.projectId,
Expand Down
3 changes: 1 addition & 2 deletions packages/cli/src/lib/firebase/firebaseCreateProject.ts
Original file line number Diff line number Diff line change
Expand Up @@ -16,8 +16,7 @@ export const firebaseCreateProject = async (projectId: string) => {
]
const spinner = new Spinner(chalk.blue('🔮 Creating Project...') + ` %s`)
spinner.start()
//const result = await execAsync(shCmd.join(' '))
const result = { stdout: 'a' }
const result = await execAsync(shCmd.join(' '))
spinner.stop()
if (result.stdout === '') {
throw new Error(
Expand Down

0 comments on commit e8b0b4b

Please sign in to comment.