Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

cartridge-gg / controller Public

Notifications You must be signed in to change notification settings
Fork 26
Star 66

Code
Issues 36
Pull requests 19
Actions
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Actions
Security
Insights

Proxy dev server to PostHog to avoid CORS issue in development#1023

Closed

JunichiSugiura wants to merge 4 commits intomaincartridge-gg/controller:mainfrom fix(profile)/posthog-corscartridge-gg/controller:fix(profile)/posthog-corsCopy head branch name to clipboard

+42-17

Conversation Commits4 (4)Checks Files changed

Commits

Commits on Nov 12, 2024

Rewrite localhost /ingest path to posthog host to avoid CORS
JunichiSugiura
committed
process.env -> import.meta.env in profile
JunichiSugiura
committed
Directly pass api key and options to posthog provider
JunichiSugiura
committed
Setup dev server proxy to posthog endpoints
JunichiSugiura
committed

Footer

© 2025 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.