-
Notifications
You must be signed in to change notification settings - Fork 91
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
Cloud installation #135
Comments
We have success on Cloud by putting |
Hi, I added the commands there and this is the deployment result:
100 13527 100 13527 0 0 62665 0 --:--:-- --:--:-- --:--:-- 62916
######################################################################## 100.0%
######################################################################## 100.0%
Do I need to add something else in the magento.app.yaml file? |
Can you post the (relevant) contents of your hooks:
build: |
set -e
unset NPM_CONFIG_PREFIX
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.1/install.sh | bash
export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"
nvm install 16
npm config set puppeteer_skip_chromium_download true -g
npm install magepack -g
php ./vendor/bin/ece-tools build:generate
magepack bundle
php ./vendor/bin/ece-tools build:transfer
deploy: |
php ./vendor/bin/ece-tools deploy
post_deploy: |
php ./vendor/bin/ece-tools post-deploy See the section that mentions that "you can customize the build phase" on the Adobe Commerce Developer Guide regarding |
Hi,
The deployment result was: ` Executing build hook...
######################################################################## 100.0%
|
Great, it looks like we're making progress. The 'hooks' section looks good (formatting here makes it hard to read, but I think it matches the known-working snippet I'd posted where relevant).
It looks like you need to set up static content deployment on the build step. This is step two in the zero downtime deployment guide. See also the output of |
Hey @fredden bit of a blast from the past for you :) Am I misunderstand this bit
In this process you are running Those requests being made will be against the live version of the codebase and not the version you are in the process of deploying? My understanding is that you would always be generating magepack on the version that is live, and therefor potentially be 1 step behind? |
@convenient hello again. :) I think you're confusing |
Hi,
I'm trying to install this on a cloud project following the steps provided here:
I updated the magento.app.yaml file in the post_deploy section including this:
echo "\n================================== Install and configure Magepack - Start ==============================="
unset NPM_CONFIG_PREFIX
curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.35.1/install.sh | bash
export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh"
nvm install --lts=dubnium
npm install -g magepack
echo "\n================================== create bundle ==============================="
magepack bundle
echo "\n================================== Install and configure Magepack - END ================================="
However during the deployment I got these error messages:
100 13527 100 13527 0 0 252k 0 --:--:-- --:--:-- --:--:-- 254k
=> Downloading nvm from git to '/app/.nvm'
W: mkdir: cannot create directory ‘/app/.nvm’: Read-only file system
W: ls: cannot access '/app/.nvm': No such file or directory
W: fatal: could not create work tree dir '/app/.nvm': Read-only file system
W: Failed to clone nvm repo. Please report this!
W: /bin/dash: 7: nvm: not found
W: npm ERR! Linux 4.19.205-0psh2
W: npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install" "-g" "magepack"
W: npm ERR! node v6.17.1
W: npm ERR! npm v3.10.10
W: npm ERR! path /app/.npm
W: npm ERR! code EROFS
W: npm ERR! errno -30
W: npm ERR! syscall mkdir
W:
W: npm ERR! rofs EROFS: read-only file system, mkdir '/app/.npm'
W: npm ERR! rofs This is most likely not a problem with npm itself
W: npm ERR! rofs and is related to the file system being read-only.
W: npm ERR! rofs
W: npm ERR! rofs Often virtualized file systems, or other file systems
W: npm ERR! rofs that don't support symlinks, give this error.
W: npm ERR! Linux 4.19.205-0psh2
W: npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install" "-g" "magepack"
W: npm ERR! node v6.17.1
W: npm ERR! npm v3.10.10
W: npm ERR! path npm-debug.log.4141927588
W: npm ERR! code EROFS
W: npm ERR! errno -30
W: npm ERR! syscall open
W:
W: npm ERR! rofs EROFS: read-only file system, open 'npm-debug.log.4141927588'
W: npm ERR! rofs This is most likely not a problem with npm itself
W: npm ERR! rofs and is related to the file system being read-only.
W: npm ERR! rofs
W: npm ERR! rofs Often virtualized file systems, or other file systems
W: npm ERR! rofs that don't support symlinks, give this error.
W:
W: npm ERR! Please include the following file with any support request:
W: npm ERR! /app/npm-debug.log
=> “n================================== create bundle ===============================”
W: /bin/dash: 10: magepack: not found
“n================================== Install and configure Magepack – END =================================”
is any other configuration required?
Thanks
The text was updated successfully, but these errors were encountered: