Free Migration Support
We’ve found a collaborative approach to migration is the most efficient. You’ll get live on Coherence over the course of a few meetings and a few hours of homework on your end. For newer or simpler projects it can be much faster.
We start by opening a joint slack channel for asynchronous communication followed by the meetings below.
App Creation and Cloud Authorization Meeting
Duration: 1 hour
Agenda:
- Choose app & team name
- Team name used in URLs for all your apps
- Setup GitHub app
- Link cloud account
Prequisites:
- Repo on GitHub in your org that you have admin rights to
- AWS/GCP account that you are owner/admin of, that you will use for non-production workloads on Coherence
At the end of this meeting, you will have:
- Coherence connected to your repo and your cloud
- We will not have created any resources aside from the IAM role in your cloud account
- You might have created a new branch in your repo (up to you if you want to setup the yml on an existing or a new branch)
Coherence.yml Setup Meeting
Duration: 2 hours
Agenda:
- We will be adding a coherence.yml file to your branch we chose in the first meeting, including resources like database/redis/cloud storage
- We will be setting up cloud secrets integration and adding all required variables in the Coherence UI
- Our goal will be to get our first successful build/deployment
- Some features for previews will still be missing (database setup)
- Some features for tests/CI will still be missing
Prerequisites:
- If Dockerfile desired/required, need to have a draft of that
- List of all required env vars for your app to start
- List of all required resources, database versions, and how your app gets configuration info (variable names)
- Any special domain or routing requirements
- Cloud function for routing
- Subdomains for tenants
- CORS/allowed hosts in your app settings
- Understand how to configure your app to run on a PORT variable from environment instead of something hard-coded
App setup
Duration: 2 hours
Agenda:
- We will be configuring database seeding/migrations, tests, and other coherence features like workspaces, depending on your requirements and use case
Prerequisites:
- linting/test configuration
- Database requirements for previews
- Do you want to use snapshot? What type (data or data +schema)?
- Do you need any seed or other logic, possibly in addition to snapshot?
- Migrations?
Integrations setup
Duration: 1 hour
Agenda:
- Setup Slack and configure GitHub integrations more deeply
- Choose workflow for review apps, if you want to control that in the Coherence UI or if you want to use our GitHub integration
- Cover toolboxes and review any other questions
Prerequisites:
- Have chosen GitHub workflow
- Have set up at least 1 feature on the app and hit the deployment URL
Discussion of data/DNS migration
Duration: 1 hour
If you're migrating data from another existing production environment, we'll support you in finding a plan that makes migrating your data and domains as simple as possible. Generally, this can be done with minimal downtime and with no risk to your existing environments or data. We'll be happy to answer any questions you've got and to share examples and learnings based on our previous experience.
Team training (optional 1 hour meeting)
- We can train your team on how to use Coherence