Skip to content

Feat: CLI settings init&deploy#564

Closed
Meldiron wants to merge 1 commit intomasterfrom
feat-cli-settings
Closed

Feat: CLI settings init&deploy#564
Meldiron wants to merge 1 commit intomasterfrom
feat-cli-settings

Conversation

@Meldiron
Copy link
Contributor

@Meldiron Meldiron commented Oct 1, 2022

What does this PR do?

As implemented by init&deploy collection, this PR adds the same logic for project settings. It' common practice to have a predefined structure of a project (enabled services, auth methods, users limit), just like it's common for databases. Since appwrite.json is supposed to be a source of truth for initial setup of Appwrite project, it should project settings.

This PR gets us one small step closer to "Deploy to Appwrite" 1-click setup.

Settings include:

  • Max users limit
  • Status (enabled/disabled) of auth methods (not OAuth)
  • Status (enabled/disabled) of project services

Test Plan

  • Manual QA
CleanShot.2022-10-01.at.20.24.34.mp4

Related PRs and Issues

x

Have you read the Contributing Guidelines on issues?

Yes

Copy link
Member

@lohanidamodar lohanidamodar left a comment

Choose a reason for hiding this comment

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

Looks good, small query

}
}

const deploySettings = async ({ yes } = {}) => {
Copy link
Member

Choose a reason for hiding this comment

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

Should we seprate these settings into individual deploys? Might be confusing as these are independent settings?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

We currently apply:

  • OAuth enable/disable
  • Services enable/disable
  • Max users limit

I can see how it would be useful to only specify one of them to deploy. I can implement a similar passion to what we do in deploy functions where you either select ones to deploy manually, or do --all to auto-pick all of them. Sounds good?

Copy link
Member

Choose a reason for hiding this comment

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

yes that sounds good, otherwise people might be confused as to what settings will be deployed, initialized

@lohanidamodar
Copy link
Member

Skipping it for now, closing, we can reopen if we want to go ahead with this later.

@lohanidamodar lohanidamodar deleted the feat-cli-settings branch April 6, 2023 02:09
@lohanidamodar lohanidamodar restored the feat-cli-settings branch April 6, 2023 02:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants