I have installed swift 1.4.8 and I want to know how to Add a new user to swift 1.4.8 .In swift 1.4.7 version ,user was added using swauth authentication but ,swauth command is not available in newer version(swift 1.4.8).
If you are using Ubuntu, you can install swauth by
apt-get install swauth
Also, make sure you enable swauth in proxy-server.conf.
For example,
[pipeline:main]
pipeline = healthcheck cache swauth proxy-server
[filter:swauth]
use = egg:swauth#swauth
set log_name = root
default_swift_cluster = https://127.0.0.1:8080/v1
Related
I am running Raspbian and have so far installed Swift 5.1.5 and cloned Vapor Branch 18.0.0 beta 27. I can't seem to get version 5.2 of Swift installed on my system somehow.
Nonetheless, the next step is to build Vapor, but it gives me the following error:
sudo swift build -c release
Updating https://github.com/jpsim/Yams.git
Updating https://github.com/apple/swift-nio.git
Updating https://github.com/vapor/console-kit.git
Updating https://github.com/apple/swift-log.git
Updating https://github.com/tanner0101/mustache.git
https://github.com/apple/swift-nio.git # master: error: terminated(128): git -C /home/pi/Downloads/toolbox/.build/repositories/swift-nio-b68c973e rev-parse --verify 'master^{commit}' output:
fatal: Needed a single revision
Not sure where to go from there, can't find any relevant info online.
Vapor 4 and the new toolbox all require Swift 5.2 - you'll need to get the installed before anything else.
Next that's an old version of the toolbox, you can find the latest release at https://github.com/vapor/toolbox/releases
Finally, the chances are you don't need the toolbox. It's used for creating new projects. If you just want to build or run existing ones, just use the swift commands
Only when using cocoapods(after run pod install), generamba setup failes with the following message when settin path to a .xcodeproj.
The path to a .xcodeproj file of the project is 'GrambaSample.xcodeproj'. Do you want to use it? (yes/no) yes
/Library/Ruby/Gems/2.3.0/gems/xcodeproj-1.4.2/lib/xcodeproj/project/object.rb:321:in `configure_with_plist': [!] Xcodeproj doesn't know about the following attributes {"inputFileListPaths"=>[], "outputFileListPaths"=>[]} for the 'PBXShellScriptBuildPhase' isa. (RuntimeError)
This error won't appear is not using cocoapods.
How can I be able to setup Generamba while using cocoapods.
To avoid this issue you should update CocoaPods to the latest beta version by executing
gem install cocoapods --pre
Latest beta version of CocoaPods now using inputFileListPaths and outputFileListPaths.
More info here See .xcfilelist Support
I have migrated to the upcoming version (v1) of material-UI, and I installed v1 alongside the current version according to the recommendation:
yarn add material-ui#latest
yarn add material-ui-next#npm:material-ui#next
When I try to use redux-form and use the package redux-form-material-ui to connect the components, it searches for the material-UI components in "material-ui" folder, which gives an error:
Error: Can't resolve 'material-ui/Radio' in 'C:\path\to\redux-form-material-ui\lib'
But I import Radio from material-ui-next/Radio
So it looks for it in the wrong version.
How can I make this work? Should I uninstall the current version and install "next" as "material-ui" instead?
Here is what is installed:
"material-ui": "^0.20.0",
"material-ui-next": "npm:material-ui#next",
"redux-form-material-ui": "^5.0.0-beta.2",
"redux-form": "^7.3.0",
My way of getting around the problem was to uninstall both material UI packages and then install the v1 as "material-ui" , and the old one as "material-ui-old":
"material-ui": "npm:material-ui#next",
"material-ui-old": "npm:material-ui"
I had to change all the imports in the project.
But now it finds the 'material-ui/Radio'.
I am currently following the small and brief introduction to Swift Vapor by following their "Hello World" tutorial on their website. However I keep getting an error from swift-package when I try to build the project where it shows the following.
$ vapor build
No .build folder, fetch may take a while...
Fetching Dependencies [Failed]
Error: swift-package: error: unknown command: --enable-prefetching
I cannot seem to find out how to resolve this online. Anybody have any idea?
you have not mentioned your environment, so i'm giving solution for macOS.
I had the same issue, my swift version is 3.0.2 and vapor toolbox version is 1.0.9,
I tried the following thing to make it work
get into your project directory
create xcode project with command
swift package generate-xcodeproj
open xcode project
Select your scheme as App like this
and then build and run app
hope this helps!!
Make sure that you're using the correct command line tools for the Swift Version that you're using.
You can check from Xcode > Preferences > Locations > Command Line Tools
For me, using swift 3.0.2, vapor build command doesn't work neither.
However using swift 3.1.0, vapor build command works well.
My Vapor toolbox version is v1.1.0
I had the same problem, and I had Swift 3.1 installed. I deleted old version completely and installed new one and now it's building fine.
Try
rm -rf /usr/local/bin/vapor
brew tap vapor/homebrew-tap

than
brew install vapor
or
brew link vapor
if you have installed a new version previously.
When i try install and i have this error:
# composer require backpack/base
Using version ^0.7.3 for backpack/base
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Installation request for backpack/base ^0.7.3 -> satisfiable by backpack/base[0.7.3].
- backpack/base 0.7.3 requires laravel/framework 5.3.* -> satisfiable by laravel/framework[5.3.x-dev, v5.3.0, v5.3.0-RC1, v5.3.1, v5.3.10, v5.3.11, v5.3.12, v5.3.13, v5.3.14, v5.3.15, v5.3.16, v5.3.17, v5.3.18, v5.3.19, v5.3.2, v5.3.3, v5.3.4, v5.3.5, v5.3.6, v5.3.7, v5.3.8, v5.3.9] but these conflict with your requirements or minimum-stability.
Installation failed, reverting ./composer.json to its original content.
How fix that?
You're probably running a Laravel 5.2 app. If so, you have two options:
1) Upgrade from Laravel 5.2 to Laravel 5.3, then try again, it will most definitely work. The Laravel upgrade takes about about 1 hour for a medium-sized project, but you'll have all the benefits of using the latest and greatest (both Laravel and Backpack).
2) Install Backpack for Laravel 5.2, but please be aware you're running an old Backpack version and you won't be receiving any updates or new features.
My recommendation, of course, is option #1. In the end, you'll still need to update Laravel, then update Backpack, so it's best to just do it now.