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

fix: self hosting architecture best practices #2775

Draft
wants to merge 7 commits into
base: main
Choose a base branch
from

Conversation

jnikhila
Copy link
Collaborator

@jnikhila jnikhila commented Jan 9, 2025

Description

Provide a concise summary of the changes made in this pull request

  • Updated Deployment Architecture
  • Added a new deployment architecture diagram
  • Added a new doc on process management

Pull request type

Check the appropriate box:

  • Review Fixes
  • Documentation Overhaul
  • Feature/Story
    • Link one or more Engineering Tickets
      *
  • A-Force
  • Error in documentation
  • Maintenance

Documentation tickets

Link to one or more documentation tickets:

Checklist

From the below options, select the ones that are applicable:

  • Checked for Grammarly suggestions.
  • Adhered to the writing checklist.
  • Adhered to the media checklist.
  • Verified and updated cross-references or added redirect rules.
  • Tested the redirect rules on deploy preview.
  • Validated the modifications made to the content on the deploy preview.
  • Validated the CSS modifications on different screen sizes.

Copy link

vercel bot commented Jan 9, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
appsmith-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jan 10, 2025 4:35am

@jnikhila jnikhila requested a review from sharat87 January 9, 2025 11:31
@jnikhila jnikhila changed the title Fix self hosting architecture best practices fix: self hosting architecture best practices Jan 9, 2025
### Appsmith Server
The **Appsmith Server** is a cloud service managed by Appsmith, and acts as the control layer for managing licenses and template configurations.

### Customer Data (Datasources)
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

@sharat87 - The customer data is customer-facing as this resides in their network, and IMO is not a part of Appsmith's deployment architecture. Could you please elaborated on why should this be included?

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.

1 participant