creame/trellis-simple-sync

Ansible playbooks for Trellis database and uploads sync. Just copy and run without any extra configuration.

trellis-simple-sync's Issues

"Stylesheet is missing." Error

I'm seeing blank pages on my production site with the message:

Stylesheet is missing.

and 500 Internal Server Error on the browser console.

when I run:

$ ./bin/sync.sh production "mysite.com" all push

The script is finishing without errors and the pages on my development site work normally.

Pull not working

Howdy!

Pull isn't working for my sites. It's like it's pulling from local, because the gzip contents are there*.

Any tips?

Best!
R

'dict object' has no attribute 'example.com'

Thank you for creating this script, I've been searching for something like this for a while now.

I followed the instructions for installation but receive the following error message when I try to run "./bin/sync.sh staging example.com db push":

---

The task includes an option with an undefined variable. The error was: 'dict
object' has no attribute 'example.com'

The error appears to have been in'../trellis/database.yml': line 80, column 9, but may
be elsewhere in the file depending on the exact syntax problem.

The offending line appears to be:
- name: PUSH > Push dump file from development to "{{ env }}"
^ here
We could be wrong, but this one looks like it might be an issue with
missing quotes. Always quote template expression brackets when they
start a value. For instance:

with_items:
  - {{ foo }}

Should be written as:

with_items:
  - "{{ foo }}"

fatal: [dev.example.com]: FAILED! => {}

---

I am running:
Ansible 2.7.10;
Trellis 1.0.3

Make compatible with Lima VM

Trellis CLI has announced support for Lima, which used containerd instead of vagrant to provide a fast and lightweight development environment for trellis projects. roots/trellis-cli@d3894d6

I use trellis-simple-sync on every project, and noticed it's not compaible with this new workflow.

I'm interested in having cross-compatibility with lima and vagrant.

GUIDs are modified by default

Modifying GUIDs can be a disruptive change for site already deployed to a production environment, therefore not modifying them should be the default behaviour.

Add option to modify GUIDs

As #6 disables modifying the GUID column by default, and there are still some scenarios where it is desirable to modify GUIDs, such as on the first deployment to a production environment.

A flag could be added to modify GUIDs when performing a search-replace on URLs.

Feature: ability to use --limit flag to specify host

Firstly, muchas gracias for all your efforts in this and for open sourcing it 🙏

I've just tried it out and found we can't use --limit=[host] in the command to specify which server to connect to, therefore it connects to all servers listed in the hosts file.

Background

We have a setup like this one in Roots Discourse:

hosts/production file example:

server1 ansible_ssh_host=IP1
server2 ansible_ssh_host=IP2

[production]
server1
server2

[web]
server1
server2

host_vars folder example:

trellis/
-- host_vars/
---- server1/
------ wordpress_sites.yml
---- server2/
------ wordpress_sites.yml

To deploy, we then use

./bin/deploy.sh production example.com --limit=server1

Feature request

To be able to use

./bin/sync.sh production example.com db pull --limit=server1

I think I can put together a PR for it, however ansible is not a strong suit of mine. For now I'll open the issue at least and we'll see how far we get 😅