Closed LucaPipolo closed 1 year ago
Not sure if this is related but I also now noticed that as well the delete process stuck forever ⬇️
I'm not sure what wp-local-docker-v2
is supposed to do on /etc/hosts
(during troubleshooting procedure I read something about this) but I suspect is not working since I do not see any change to the file and I have to manually add the host there.
@LucaPipolo wp-local-docker-v2
is trying to add/delete in /etc/hosts
the necessary entry to recognize the custom URLs locally.
As far as your 1.
point, I had this happen using fnm
as well and it's due to the installation location path. Specifically the space in ../Application Support/..
not being escaped by a command for mkcert
.
My workaround was to move the whole folder /Users/{your_user_name}/Library/Application Support/fnm
to the root /Users/{your_user_name}/.fnm
.
Notes:
fnm
to .fnm
.fnm default {number}
.. ~/.zshrc
, might be a different file if you do not use Zsh (e.g. it might be . ~/.bashrc
instead).Hope that helps for you or anyone using fnm
and it was installed via brew.
Troubleshooting
Describe the bug
After a totally clean installation on a new machine (MacBook Pro 14'' M1 Pro) when I try to setup a new website using 10updocker create (does not matter what I choose in the following steps such as PHP version, WordPress installation, additional domains, etc.) I encounter the following errors:
Rewrite rules structure is updated to /%postname%/...
and never complete.I already tried the trouble shooting techniques and did not help.
Steps to Reproduce
10updocker create
Screenshots, screen recording, code snippet
Environment information
MacBook Pro Model: MacBook Pro 18,3 Chip: Apple M1 Pro Core Numbers: 8 RAM: 16 GB macOS Monterey 12.3 (21E230)
Docker 4.11.1 (84025) Engine: 20.10.17 Compose: 1.29.2 Kubernetes: v1.24.2
Node v.16.16.0 NPM 8.11.0 Installed using FNM
Code of Conduct