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

"Deploy to Caprover" Button #863

Closed
NeoTheThird opened this issue Oct 18, 2020 · 2 comments
Closed

"Deploy to Caprover" Button #863

NeoTheThird opened this issue Oct 18, 2020 · 2 comments

Comments

@NeoTheThird
Copy link

I've seen this button on some projects:

image

I think it'd be nice to actively promote something like this for caprover. Some low-hanging fruit to get more exposure in readmes of one-click projects. Obviously the button couldn't point to a direct sales thingie like it does for heroku, but it could open a page explaining that project xyz is configured as a caprover one-click app, that caprover is the greatest invention since sliced bread, and how to set it up, show the demo video, etc.

@githubsaturn
Copy link
Collaborator

The applications developers usually use "Deploy to Heroku" type buttons to simply create an app on the user's Heroku account. All these buttons are backed by a centralized service.

While I agree that it's a nice thing to have. there is not much value to be added here. Also, there is nothing to be done on CapRover side to enable this. This is purely just a piece of documentation. Currently applications developers host their own documentation like this: https://www.chatwoot.com/docs/deployment/deploy-chatwoot-with-caprover

@NeoTheThird
Copy link
Author

Also, there is nothing to be done on CapRover side to enable this.

True, not caprover itself, rather the website. I was just thinking it could generate pages for all one-click apps in the default repo, display some generic info about caprover, the description from the app config, and the app logo. Just to get the word out about caprover. But your call, you're right of course that it wouldn't do anything.

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

No branches or pull requests

2 participants