- [ x] Checked the logs and have provided the logs if I found something suspicious there
I’m submitting a…
- [ ] Regression (a behavior that stopped working in a new release)
- [x ] Bug report
- [ ] Performance issue
- [ ] Documentation issue or request
We currently run Squidex in an AWS Elastic Beanstalk environment with a multicontainer Docker setup; with a minimum of 2 instances running concurrently. Our Squidex application is served through a nginx reverse proxy on each instance, with an AWS application load balancer (ALB) in front of it & responsible for distributing the requests to each server.
For data storage we use a MongoDB database connected through an AWS VPC Peering connection. For file storage (images and other kinds of static assets) we have an AWS Elastic File System (EFS) setup that’s accessible from each Squidex instance. Currently there’s no Redis or any other kind of distributed caching setup for the Squidex instances.
When creating new schema fields we need to restart Squidex, else the schema won’t be created on one of the servers which will cause errors when you try to fetch content that does not “exist” on one of the servers.
We should not need to restart Squidex to sync the schemas to the different servers
Minimal reproduction of the problem
- [x ] Self hosted with docker
- [ ] Self hosted with IIS
- [ ] Self hosted with other version
- [ ] Cloud version
Squidex version 4.0.0-beta1, as fetched from Docker Hub.
- [ x] Chrome (desktop)
- [x ] Chrome (Android)
- [x ] Chrome (iOS)
- [ x] Firefox
- [x ] Safari (desktop)
- [ x] Safari (iOS)
- [ x] IE
- [ x] Edge