Sage 10 on Pantheon as of Jan 30, 2021. These are the steps I used to get things running on Pantheon. There are brighter minds here, if you can look this over and see if I am missing anything, if anything could use clarification, or for random, “YOU USE PANTHEON DAS GARBAGE!” trolling I would appreciate it.
- Add
node_modules/
to the Pantheon.gitignore
- Clone Sage 10 in themes folder
git clone https://github.com/roots/sage.git
cd sage/
-
gco log1x/next
(If you want Tailwind 2 from Brandon’s fantastic work) rm -rf /.git
yarn && composer install && yarn build
- Update
config/view.php
to,'compiled' => wp_upload_dir()['basedir'].'/storage/framework/views',),
git add -f vendor/
git add -f public/
mv storage/ ../../uploads/storage
ln -sfn ../../uploads/storage
composer install --no-dev
- Updated local url in
webpack.mix.js
(for Lando or Localdev) - Git commit all these changes
- SFTP Mode: Upload
storage/
folder to/code/wp-content/uploads
- Git push!
Now I use Lando, and pointed the above local url to the Lando URL for Browsersync. YMMV. This worked locally, on Lando, always – without any changes.
I wonder now, because I haven’t had time to go further yet, when I make changes from here on out, do I need to upload the storage/
folder again due to changes? Or can I leave that the way it is now that it’s working. This is the black magic of the process I am not 100% familiar with. Composer and it’s relation to making changes/deploying. I’ll find out soon enough I suppose… and update this thread.