We use Heroku pipelines. Our standard practice is to use the CB Dashboard deployment as production, and set up a separate pipeline for staging (auto-deployed from your master branch).
I suggest you follow the pull request git workflow and test all merged pull requests on staging before deploying them using the CB Dashboard.
SSL is provided by Heroku automatically, both for CB domains and custom domains - just follow the instructions to correctly set the CNAME records when adding a custom doain.
If you let me know the app id I can configure the staging pipeline for you.
Here is project Dasboard link : https://app.crowdbotics.com/dashboard/app/18446
This is chrome plugin not Android/iOS application. We have to upload this on Google chrome store.
We already tested plugin with backend every thing is working fine.Now we have to upload on store only.
What i understand, we can use the default environment as production and upload build to chrome store. For further development you will create staging environment. Please create staging environment, if you need any further information let me know.
Thanks @dmitrii.k i am able to access staging app link, but not able to login with default password credentials. May i know procedure to create user for stage (https://ex-curator-18446-staging.herokuapp.com/), how can i access the admin panel of staging server?
@ankit, staging management isn’t supported by the CB Dashboard yet, so please post any requests for creating a superuser/resetting its password, as well as setting env vars here (DM the values to the responder).
I’ve created a default super user on staging for you and DM’d you the password.
That was a temporary failure due to the new Docker Hub limits, which started happening occasionally on Heroku. We’re looking into finding a possible workaround for this.
Your subsequent builds worked and you have a successful release on staging right now.
Thanks can i have staging server admin panel URL, Username and password
can i have user name and password for this. Note: Production server application URL and login working fine which i receive from previous developer, if stage is replicated from production branch same user should work here also.