Seravo / wordpress

The WordPress project layout used by many of Seravo's customers, suitable also for local development with Vagrant and git deployment
https://seravo.com
GNU General Public License v3.0
102 stars 54 forks source link

Automatically run Gulp is SCSS/SASS files have changes #163

Closed ottok closed 3 years ago

ottok commented 3 years ago

"Screenshot":

laptop$ git push production
Counting objects: 8, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (8/8), done.
Writing objects: 100% (8/8), 667 bytes | 667.00 KiB/s, done.
Total 8 (delta 7), reused 0 (delta 0)
remote: Seravo: running post-receive git hook
remote: Seravo: SASS files changed, running Gulp...
remote: [21:07:07] Using gulpfile /data/wordpress/gulpfile.js
remote: [21:07:07] Starting 'default'...
remote: [21:07:07] Starting 'build'...
remote: [21:07:07] Starting 'sass'...
remote: [21:07:08] Finished 'sass' after 257 ms
remote: [21:07:08] Starting 'js'...
remote: [21:07:09] Finished 'js' after 1.16 s
remote: [21:07:09] Finished 'build' after 1.42 s
remote: [21:07:09] Finished 'default' after 1.42 s
remote: Found Tideways API key: abc123
remote: {"apiKey": "abc123", "name": "894405ac", "type": "release", "environment": "", "service": "web", "compareAfterMinutes":90}
remote: ==> Tideways event registered successfully!
remote: Seravo: Flushing all caches...
remote: ----> Purging WordPress object cache...
remote: Success: The cache was flushed.
remote: ----> Flush WordPress rewrites...
remote: Success: Rewrite rules flushed.
remote: ----> Flush the entire Redis cache (includes Nginx PageSpeed cache etc)...
remote: OK
remote: ----> Success
remote: ----> Purging Nginx page cache...
remote: Cache purged successfully for production.
remote: Error: Couldn't purge cache. Could be empty already.
remote: Cache purged successfully for production.
remote: Error: Couldn't purge cache. Could be empty already.
To production:/data/wordpress
   124ebbc4..894405ac  master -> master