pull-push
Skill10 starsChanged 38 days agoMITView on GitHub
Use when syncing code, database, or files between local and Acquia Cloud environments, or pulling a Cloud database/files locally.
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- acquia/acquia-skills-privateedited, first seen May 1, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- acquia/acquia-skills-private★ 199% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository25 other files it gives its agents.
- application-managementSkill
- codestudioSkill
- environment-managementSkill
- getting-startedSkill
- ide-managementSkill
- meo-cdn-securitySkill
- meo-codebasesSkill
- meo-deploymentsSkill
- meo-environmentsSkill
- meo-identity-accessSkill
- meo-overviewSkill
- meo-site-instancesSkill
- meo-sitesSkill
- remote-accessSkill
- scriptingSkill
- ssh-key-managementSkill
- trial-managementSkill
- troubleshootingSkill
- dependency-updatesSkill
- security-updatesSkill
- application-managementSkill
- getting-startedSkill
- pipeline-operationsSkill
- drupal-update-deploySkill
- setup-external-ci-cdSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 101
If you skipped scripts during a pull, run them separately:
- Distinctive: line 222
Verify your SSH key is set up and your account has write access to the environment:
- Very specific: line 231
Check that composer install and any build steps complete without errors before pushing:
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Pull & Push with Acquia CLI
Platform: This skill applies to ACE (Acquia Cloud Enterprise) subscriptions only. For MEO (Multi-site Enterprise Operations), see MEO Site Instances for database and file operations.
Trials: trial SSH is Drush-only, so any pull path that needs rsync/scp/sftp (for example
acli pull:files) fails on a trial. Usegit clonefor code, and pull the database with--no-importthen import into the local stack (e.g.ddev import-db); pass--no-fileswhere a command would otherwise try to sync files. See Trial Management.
Use when:
- Syncing your local environment with a Cloud Platform environment
- Pulling code, database, or files from Cloud to local
- Pushing code, database, files, or build artifacts to Cloud
Pull: Copy from Cloud to Local
Pull everything (code + database + files)
acli pull:allAliases: acli refresh, acli pull
Prompts you to select an environment, then copies code, database, and files to your local environment.
Options:
acli pull:all \
--dir=/path/to/project \
--no-code \ # skip code
--no-databases \ # skip database
--no-files \ # skip files
--no-scripts # skip post-pull scriptsPull code only
acli pull:codePulls the latest code from the selected Cloud environment into your local directory.
acli pull:code --dir=/path/to/projectPull database only
acli pull:databaseAlias: acli pull:db
Imports a database backup from a Cloud environment into your local database.
Options:
acli pull:database \
--on-demand \ # force a fresh on-demand backup (not cached)
--no-import \ # download the backup file but don't import it
--multiple-dbs # download multiple databases (multisite)Pull files only
acli pull:filesCopies Drupal public files (sites/default/files) from the Cloud environment to your local.
Run post-pull scripts manually
If you skipped scripts during a pull, run them separately:
acli pull:run-scripts
acli pull:run-scripts --dir=/path/to/projectPush: Copy from Local to Cloud
Push database
acli push:databaseAlias: acli push:db
Uploads your local database to a Cloud Platform environment. Requires both a local and remote database to be configured.
Push files
acli push:filesCopies your local Drupal public files to the selected Cloud environment.
Push code (IDE only)
acli push:codePush code from your Cloud IDE to a Cloud Platform environment. This command is only available inside a Cloud IDE or Lando environment.
Build and push a code artifact
Build your project and push the compiled artifact to a Cloud environment or custom git remote:
acli push:artifactCommon options:
# Push to a specific branch on Cloud
acli push:artifact --destination-git-branch=deploy/main
# Push to a specific tag
acli push:artifact --destination-git-tag=release-1.2.3
# Push to an external git URL (e.g. GitHub)
acli push:artifact --destination-git-urls=git@github.com:myorg/myrepo.git
# Dry run — build but don't push
acli push:artifact --no-push
# Build in a specific directory
acli push:artifact --dir=/path/to/project
# Skip sanitization step
acli push:artifact --no-sanitizeTypical Workflows
Refresh local dev environment
acli pull:allPull only the database (fastest for testing)
acli pull:database --on-demandDeploy a build artifact to Cloud
acli push:artifact --destination-git-branch=tags/deploy-branchSync files to production (use with care)
acli push:filesBest Practices
- Always pull before you push — Avoid overwriting recent Cloud changes.
- Use
--on-demandfor fresh data — The default pull uses a cached backup;--on-demandforces a new one. - Test artifact builds with
--no-push— Verify the artifact is correct before pushing. - Use
--no-scriptsin CI — Post-pull scripts are designed for local dev, not CI pipelines. - Backup before pushing a database — A push:database overwrites the remote database.
Troubleshooting
"Local database not found"
pull:all and pull:database require a running local database. Make sure your local Drupal stack (Lando, DDEV, etc.) is running.
"Access denied" on push
Verify your SSH key is set up and your account has write access to the environment:
acli ssh-key:list
acli auth:meArtifact push fails
Check that composer install and any build steps complete without errors before pushing:
acli push:artifact --no-push # dry run to inspectRelated Topics
- Application Management — Find environment IDs
- SSH Key Management — Authentication
- Remote Access — SSH and Drush on Cloud environments
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

