http://coldfusion.com logo
Join Slack
Powered by
Are you on window, Mac, or Linux
# wheels-dev
p
Are you on window, Mac, or Linux
r
Windows. I was able to just do this in a blank directory in command box and see it running. I didn't install any new jdk or anything. wheels generate app. it also didn't create /vendor/wheels/vendor/wheels so that's good
p
Can you do a scoop update wheels to see if you get the 4.0.2 version installed
r
Copy code
scoop update wheels
wheels: 4.0.1 (latest version)
Latest versions for all apps are installed! For more information try 'scoop status'
@Peter Amiri If I'm in a blank directory in commandbox what is the proper way to create a new wheels 4 app? install wheels or wheels generate app?
p
I'm away from the but will get this resolved for you in a bit
r
Thanks no rush just wanted to try out the latest and greatest
I got my new wheels 4 app running but receive this error
Copy code
Lucee 7.0.3.43 Error (expression)
Message 	key [ENGINEADAPTER] doesn't exist
 	The Error Occurred in
C:\wheels4app\personal\vendor\wheels\Global.cfc: line 2325

    2323:    public numeric function $getRequestTimeout() {
    2324:       if ($hasEngineAdapter()) {
    2325:          return application.wheels.engineAdapter.getRequestTimeout();
    2326:       }
    2327:       // Fallback when adapter not yet initialized (e.g. error during startup)
p
Let see if we can get scoop to install the latest version now. Please try 
scoop update wheels
then 
wheels --version
to see if you get 4.0.2. If not then try 
scoop reinstall wheels
and see if you get v4.0.2. Hopefully one of those will work fro you, then you can try 
wheels new blog
to create a sample app. Try these and let me know how it goes.
r
Copy code
PS C:\Users\cy> scoop update wheels
wheels: 4.0.2 (latest version)
Latest versions for all apps are installed! For more information try 'scoop status'
PS C:\Users\cy> wheels --version
Wheels Version: 4.0.2 (stable)

 __        ___               _
 \ \      / / |__   ___  ___| |___
  \ \ /\ / /| '_ \ / _ \/ _ \ / __|
   \ V  V / | | | |  __/  __/ \__ \
    \_/\_/  |_| |_|\___\___|_|___/

<https://wheels.dev>
PS C:\Users\cy> wheels new blog
[ERROR] Error: lucee.runtime.exp.NativeException: there is no Resource provider available with the name [c], available resource providers are [ftp, zip, tar, tgz, http, https, ram, s3]
PS C:\Users\cy>
@Peter Amiri Do you have any ideas about that engineadapter error above? That is 4.0.2 running on Lucee 7.0.3.43 on commandbox. I really would like to get rid of that error if you have any ideas.
p
Looking into it. May potentially be a path related parsing issue.
can you run
Copy code
wheels --verbose new blog 2>&1
and paste the output here
r
Copy code
wheels --verbose new blog 2>&1
Executing module shortcut: wheels (equivalent to 'lucli modules run wheels new blog')
[ERROR] Error: lucee.runtime.exp.NativeException: there is no Resource provider available with the name [c], available resource providers are [ftp, zip, tar, tgz, http, https, ram, s3]
wheels --verbose new blog Executing module shortcut: wheels (equivalent to 'lucli modules run wheels new blog') [ERROR] Error: lucee.runtime.exp.NativeException: there is no Resource provider available with the name [c], available resource providers are [ftp, zip, tar, tgz, http, https, ram, s3]
p
@risto Before I package and ship the new version can you run this in a power shell window, it will replace your Module.cfc file with the one in the next CLI PR so we can test if the fix works.
Copy code
# Backup the current Module.cfc
Copy-Item "$env:USERPROFILE\.wheels\modules\wheels\Module.cfc" `
          "$env:USERPROFILE\.wheels\modules\wheels\Module.cfc.bak-4.0.2"

# Download the patched version from the PR branch
Invoke-WebRequest `
  -Uri "<https://raw.githubusercontent.com/wheels-dev/wheels/peter/fix-windows-drive-letter-uri-misparse/cli/lucli/Module.cfc>" `
  -OutFile "$env:USERPROFILE\.wheels\modules\wheels\Module.cfc"

# Verify the patch is in place (should print "yes")
if (Select-String -Path "$env:USERPROFILE\.wheels\modules\wheels\Module.cfc" -Pattern "safeDirExists" -Quiet) { "yes" } else { "no — download failed" }

# Re-run the broken command
wheels new blog
r
@Peter Amiri Worked like a charm!
Everything is working but I couldn't pull up the blog because I have something running on 8080. Changed it to port 8082 in lucee.json and started up perfectly.
p
Thanks for the feedback. I will get this baked into the the next major release. I have been wanting to add a port checker to the server start command so it automatically picks the next available port. I too don't like how this limits getting multiple engines running.
r
@Peter Amiri Yes it seems to run great. Do you have any idea how I can solve this running on Lucee 7 commandbox?
Copy code
Lucee 7.0.3.43 Error (expression)
Message 	key [ENGINEADAPTER] doesn't exist
 	The Error Occurred in
C:\wheels4app\personal\vendor\wheels\Global.cfc: line 2325

    2323:    public numeric function $getRequestTimeout() {
    2324:       if ($hasEngineAdapter()) {
    2325:          return application.wheels.engineAdapter.getRequestTimeout();
    2326:       }
    2327:       // Fallback when adapter not yet initialized (e.g. error during startup)
p
I'll look at that, it shouldn't be too hard to get it to run.
r
@Peter Amiri Have you had wheels 4.2 running on Lucee 7 on commandbox without that "key [ENGINEADAPTER] doesn't exist" error?
@Peter Amiri I think this is solved now by using "wheels new myapp" instead of "install wheels-core" which does not work on commandbox. I got a running 4.0.3 homepage on Lucee 7
p
@risto I shifted my attention away from CommandBox and towards LuCLI with 4.0 cause it unlocked a lot of features we wanted to do with the CLI. the Wheels cli is now a white labeled LuCLI. We are still in the transition but that is where the attention has been. I'm glad you got 4.0.3 running using the new CLI. Let me know if you run into any issues. Then next point release has a lot of fixes coming so the whole eco-system gets better and better.
r
@Peter Amiri Don't get me wrong I love the LuCLI. I was concerned with commandbox because I run commandbox servers for live sites. Is LuCLI something you are running on a production server or is it mainly intended for Dev work?
p
I switched our production servers to LuCLI as well. It is definitely possible and we haven't had any issues.
r
Good to know. Thanks Peter
Open in Slack
PreviousNext
Powered by