-
-
Notifications
You must be signed in to change notification settings - Fork 262
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Standalone binary works - but how to bundle octane #605
Comments
@kevincobain2000 could you share the Dockerfile used in this process? did you embed your application and frankenphp? if you created a binary probably your worker script path is not these |
Hello How did you connect database when using Laravel application as Standalone binary? I can't get connected to database. The database is on same machine localhost. |
I'm writing a guide explaining how to bundle Laravel and Octane apps: #753 Does it help? For the database, set the corresponding environment variables or change your |
The database connection is now established. However, it appears that images uploaded within the application, like those stored in the public folder, aren't retained in the application. I did build self contained binary. |
@skmirajbn I added a section about this: #753 |
Hello @dunglas @skmirajbn, where to put the .env file for the bundled app? Many thanks |
Describe you feature request
Standalone binary works well and works out of the box. Nice!
However, in order to run the binary on Octane, I am doing like below:
If I just run as
php-server
, then it runs onFrankenServer
, and notFrankenAPI
. There is a huge performance difference between these two and want to be able to run the binary onFrankenAPI
.I think I am missing something? A worker file
--worker=
to be passed to run to get the boosted performance. By providing worker path, it throws ERROR same as #318Anyways, my question (or feature request) is to have docs on creating standalone binary with samples of workers files.
The text was updated successfully, but these errors were encountered: