Once you have a working Wagon site, you probably want to see it working online, with the backoffice and everything. That's the role of the LocomotiveCMS engine.
1. Edit your deployment settings
cd ~/workspace mate my_first_website/config/deploy.yml
Here is what your deploy.yml file should look like:
development: host: dev.example.com email: email@example.com password: easyone staging: host: staging.example.com email: firstname.lastname@example.org password: easyone production: host: www.example.com email: email@example.com password: easyone
The email/password credentials are owned by one of your LocomotiveCMS administrator accounts.
You can either push the whole site or specify a type of resource.
Pushing the whole site:
cd ~/workspace/my_first_website bundle exec wagon push staging
If you want to push your content entries (
data/*.yml), add the
--data option (or
bundle exec wagon push staging --data
Pushing only a specific type of resource:
In some cases, you do not want to push the whole site. For instance, if you have just modified a single page, you do not need to push the assets too.
The available resource types are: theme_assets, snippets, content_types and pages.
bundle exec wagon push staging --resources=pages
You might prefer the shorter syntax:
bundle exec wagon push staging -r pages
What if the resource already exists within your target engine?
By default, the push command will not let you erase your target resources. That is why you will see the “skipped” label beside your resource name if you try to run the push command.
Unless you force it:
bundle exec wagon push staging --resources=pages --force