the ~/ and /home are basically the same thing as (EDITED: false)
Somehow it’s getting the (EDITED: crossing out so as not to mislead anyone, see Sebastian’s correction in next message)
prepare-image.sh script (which i see on your github hosting repo), but not the
setup script that’s documented … oh, well …
Regardless, it’s pretty simple to get up and running with docker-compose and a .env file, so not a big deal.
Btw, S3 compatibility for asset storage works nicely on Vultr Object Storage
I’m able to easily add custom plugins using PLUGINS__0, PLUGINS__1, etc… in the docker-compose file, pointing to a custom /etc/squidex/plugins directory I can just dump *.dll files into :-). The plugins directory is mounted as a volume, and the assembly is referenced as
plugins/Squidex.Extensions.MyExtension.dll for example, and I was able to configure that with a trivial CI build/publish script … Pretty cool
Is there an example floating out there somewhere on creating an API controller that is able to insert / update / delete records inside an extension, and upload assets without using the client manager (which is awkward)? I’m assuming it’s just a matter of injecting the relevant repositories, but maybe you could point me to some sample code for that?