Open hermesalvesbr opened 11 months ago
I'm try to test your SEO extension, it's a great idea. Thanks for your job!
I'm trying to use inside a docker container:
directus/directus:latest
43 timing command:i Completed in 3272ms 44 verbose stack Error: Unsupported URL Type "workspace:": workspace:* 44 verbose stack at unsupportedURLType (/usr/local/lib/node_modules/npm/node_modules/npm-package-arg/lib/npa.js:327:15) 44 verbose stack at fromURL (/usr/local/lib/node_modules/npm/node_modules/npm-package-arg/lib/npa.js:387:13) 44 verbose stack at Function.resolve (/usr/local/lib/node_modules/npm/node_modules/npm-package-arg/lib/npa.js:83:12) 44 verbose stack at #nodeFromEdge (/usr/local/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:1048:22) 44 verbose stack at #buildDepStep (/usr/local/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:917:35) 44 verbose stack at #resolveLinks (/usr/local/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:1436:32) 44 verbose stack at #buildDepStep (/usr/local/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:783:32) 44 verbose stack at #buildDepStep (/usr/local/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:1035:30) 45 verbose cwd /directus 46 verbose Linux 5.15.0-86-generic 47 verbose node v18.18.0 48 verbose npm v9.8.1 49 error code EUNSUPPORTEDPROTOCOL 50 error Unsupported URL Type "workspace:": workspace:* 51 verbose exit 1 52 timing npm Completed in 3406ms
Another way to install your extension?
Hello. Please refer to this directus docker guide: https://docs.directus.io/self-hosted/docker-guide.html#persistence There's a specific section about persistence. In short, you have to create volume for extensions and link it to your project extensions folder, then you can create or paste an extension. There's one more valuable options id docker-compose file which I use daily - EXTENSIONS_AUTO_RELOAD: true, which will watch for changes and reload extensions (if it's a newly copied extension then you'll have to restart your directus docker container).
Here's an example of my docker-compose.dev.yaml file: backend: container_name: yourname-directus image: directus/directus:latest ports:
# only for dev
CORS_ENABLED: true
CORS_ORIGIN: "http://localhost:3000"
REDIS: 'redis://cache:6379'
WEBSOCKETS_ENABLED: true
ADMIN_EMAIL: '${DIRECTUS_ADMIN}'
ADMIN_PASSWORD: '${DIRECTUS_PASSWORD}'
#EMAIL SETUP
EMAIL_VERIFY_SETUP: '${EMAIL_VERIFY_SETUP}'
EMAIL_FROM: '${EMAIL_FROM}'
EMAIL_TRANSPORT: '${EMAIL_TRANSPORT}'
EMAIL_SMTP_HOST: '${EMAIL_SMTP_HOST}'
EMAIL_SMTP_PORT: '${EMAIL_SMTP_PORT}'
EMAIL_SMTP_USER: '${EMAIL_SMTP_USER}'
EMAIL_SMTP_PASSWORD: '${EMAIL_SMTP_PASSWORD}'
EMAIL_SMTP_SECURE: '${EMAIL_SMTP_SECURE}
npm i directus-extension-seo
at directus directory.
- npm i directus-extension-seo
why isn't this mentioned in the Readme.md file, if it wasn't for this issue then it would have been difficult to install this extension.
I'm try to test your SEO extension, it's a great idea. Thanks for your job!
I'm trying to use inside a docker container:
directus/directus:latest
Another way to install your extension?