Code Monkey home page Code Monkey logo

laravel-sync's People

Contributors

aerni avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar

laravel-sync's Issues

Issue pulling down from production

Having an unusual issue I can't quite narrow down.

I have a very simple config:

  'remotes' => [

    'production' => [
      'user' => 'ploi',
      'host' => '192.192.192.192',
      'port' => 22,
      'root' => '/home/ploi/site.life',
      'read_only' => true,
    ],

  ],

(actual details replaced above, but correctly auths)

  'recipes' => [

    'assets' => ['/public/assets/'],

  ],
  'options' => [
  // '--archive',
  // '--itemize-changes',
  '--verbose',
  '--human-readable',
  '--progress'
],

When running php artisan sync pull production assets I get:

 Please confirm that you want to pull the assets from production (yes/no) [yes]:
> yes

skipping directory .

sent 8 bytes  received 13 bytes  14.00 bytes/sec
total size is 0  speedup is 0.00
The sync was successful

I've tried changing folders (same result), testing with a folder that doesn't exist (error saying folder doesn't exist). As far as I can tell everything works completely fine except the folder is skipped?

Not too sure what could be the culprit here?

Make the "read_only" option based on both the origin and destination

Hi,

I was wondering if it would be easy to adapt the package so we could have the ability to set the "read_only" option on a remote based on the origin?

I want for example to prevent somebody to push from local to production, but I need them to be able to push from staging to production.

Thanks.

Implement --force option

I created a custom utility in Statamic for our customers to be able to push content themselves, by clicking a button.

This action triggers Artisan::call('sync push production content') but it doesn't seem to work as I'm guessing the command awaits confirmation.

Would it be possible to add a --force parameter, in order to bypass the confirmation?

Add Laravel 9 support?

Getting this error on a Laravel 9 installation:

aerni/sync v1.2.0 requires illuminate/support ^7.0 || ^8.0 -> found illuminate/support[v7.0.0, ..., 7.x-dev, v8.0.0, ..., 8.x-dev] but these were not loaded, likely because it conflicts with another require.

Handling deleted assets?

Hi

I'm a new user! Very happy with laravel-sync

Just wondering, if there's a way to keep track of deleted images?

My client deletes a bunch of images and uploads a bunch more on the staging server.

During development I add a few images locally.

Using php artisan sync pull local assets pulls all the new images from the staging server, which is great.

However, the images the cilent deleted are still on my local version of the site. When I run php artisan sync push production assets. All my new images and the old images the client deleted are pushed up to the staging server.

Is there anyway around this?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.