Feeedback cleaver new update

We use systemctl and supervisor.

Also, we made some updates to env to use default variables so that basic laravel apps will run (just work) after deployment -> we will include this in our next release. Thanks for good insights and helping us reduce friction!

well .en is not work at all …
:sleepy:

in fact, i get anything, please check on ploi or forge laravel.

i get why, because in step 2, composer install failed while deploy database… with default config.
because it failed, Activate New Deployment not run …
so link is not done with current directory

and fetch maybe fetch in current.

so it’s blocked.

i try other way.
manually add .env in realPath but not work. each deploy destroy .env.

It looks like you are still confused a bit with how fetch works. Fetch gets your env variables if it is already on the server. But the first time, you may not have any env variables to begin with.

So, the very first time, you need to add your env variables and then click Sync. You can click that blue switcher on top-right to switch between field editor and text editor.

Once you have synced your variables, they are available in future for fetching and editing. To summarize:

  1. Add your env variables first
  2. Sync the variables to your server
  3. Deploy
  4. Fetch your env variables and do more editing (like adding, removing, updating etc.)
  5. Sync
  6. Deploy

it s not possible to set each env variable with this type of features. all .env already exist. and should be copy paste.

it s for me a waste of time and to enter row by row all env. and I will never do that.

That’s true. That’s why we have that blue switcher that you can switch to toggle between row by row and text edit.

1 Like

Hi @spham - sorry for the confusion, the video below shows how you can easily copy and paste the env file and then apply it to your server. Hope this helps! :grinning:

1 Like

thank you, i don"t see this feature.
but something is strange,

    • I copy paste
    • deploy
    • deploys failed
    • check env and see nothing …

that mean, it not persist my .env

can you add same feature instead of hook
it’s very complicated hook feature, if we need to make some fast work

instead of only this

You’ll still need to fetch the env file to view the current env. Are you trying to deploy October CMS still? I can take a look at it tomorrow to see if there is anything else needed for October.

Hum, is discouraging to use it. many feature need to guess.

for no, not work, regular laravel project or october cms
for october cms you can check on github and try.

This is already possible with Cleaver. You can create your own hook and add any script you want:

Something to keep in mind: Cleaver’s Webapps feature is much more powerful than what Forge and Ploi provides. Webapps feature is more comparable to Laravel Envoyer then Laravel Forge.

1 Like

i see this, because i have make some change .
for envoyer i dont like it and not use it , because is too complicated

Hi @spham - I took a look at deploying October CMS and was able to get it to run. I posted a blog here Deploying October CMS . I hope this helps you with launching yours!

Also, we’ve released some new updates, some based on your feedback! I’m hoping this helps reduce some more friction around the env setup. https://releases.cleaver.cloud/

1 Like

hi
thank you for october

i try a new install in jovo framework ( alexa ) and all is success but i have a 502 bad gateway

https://sapx.cleancode.ovh/

What is Jovo framework?

it’s an node js framework for voice app

I need start this script below

cd src && node index.js --webhook

this not work too
node {{ releasePath }}/src/index.js --webhook

any help for this hook and if possible disable default monitoring, it seems duplicate with

ok now it seems ok. and resolved, have you fix something ?