Skip to main content
11
results
Andrew Fletcher
The error you're encountering indicates an issue with the ffi gem during the CocoaPods update. The error message suggests trying to run the gem pristine command to fix it. Using terminal - run the following command: gem pristine ffi --version 1.16.3This command will attempt to restore the ffi gem to its pristine state, resolving any issues with its extensions. After running this command, try running pod update again pod updateIf you encounter any permission issues, you might need to use...
Andrew Fletcher
Looking to install Solr on your server?  Not sure if it worth the...
Andrew Fletcher
Installing Varnish to increase the speed of the page load. Install varnish using...
Andrew Fletcher
Getting Started with Cocoapods Installation Built with Ruby, Cocopods is...
Andrew Fletcher
I’m recently doing an IoT project. I wanted to investigate the network...
Andrew Fletcher
Well for me it is very slow.  Recently, I upgraded from CentOS 6 to Centos 7.  CentOS 6 was lightening fast.  Since the upgrade CentOS 7 has been so slow in comparison.  But when I say slow, it has been appallingly slow.  It just was unable to reach anywhere the performance of 6.  Which seems odd, given high transmission speed and powerful hardware.   It still takes forever in executing or processing services or applications. This is a fluid...
Andrew Fletcher
To add ejabberd and run MYSQL to the server I needed to update the server...
Andrew Fletcher
To connect to your CPanel hosted server via SSH OSX, please follow...
Andrew Fletcher
Installing Laravel on an Apache server was going to be a no fuss process said no...
Andrew Fletcher
I had an instance where I needed to move content from a plist to the server...
Andrew Fletcher
Today while in Terminal, I ran a regular script pod update.  However, this time I received the following error [!] CDN: trunk URL couldn't be downloaded: https://raw.githubusercontent.com/CocoaPods/Specs/master/Specs/d/a/2/Alamofire/5.1.0/Alamofire.podspec.json Response: Timeout was reachedI read on GitHub that it could be a cache issue, so I ran: sudo rm -rf ~/.cocoapods/repoNo change. Instead of attempting a pod update, I changed the command to pod install.  Worked a treat....