Select your target location close to your center of operation.
Select the size of your machine. At least 4GB or memory with 2 virtual cores are recommended.
Recommended server size
Step 3: Wait For the Server to Spin Up
It can take a while until your server is ready to be used.
Waiting for the server
Step 4: Create a DNS Record
Click your new server and wait until you get an IP address.
IP address is ready
Create a DNS A record to this IP address.
Step 5: Create the initial admin user
The server will pull all images now and start them in the right order. Furthermore caddy (the reverse proxy) will create a certificate for your domain. This can take a while, depending how fast your DNS record is propagated. If you use a domain that has not been used before, it takes only a few minutes.
Squidex is ready for use. If you visit your installation under https://mydomain.com you will see a simple setup guide where you can create the initial admin user. If you have configured an external authentication provider (for example Github or Google) you can just login and as the first user you will get admin permissions automatically.
Setup guide
Configuring Object Storage
Vultr Object Storage provides an option for cost-effective and scalable S3 compatible storage for Squidex assets. The following steps outline the process of configuring Squidex to use this Vultr product.
Click on the bucket you've just created and add a folder.
Vultr object storage bucket list
Step 3: Configure Asset Storage to Use S3
Navigate to the overview tab and make note of your S3 credentials.
Vultr object storage bucket list
Edit the /home/.env file using your editor of choice and add the following environment variables using the appropriate values for each (leave the S3_REGION variable empty for now):
Next, edit the /home/docker-compose.yml file to pass these environment variables onto the container:
In your command line shell, update your Squidex container to use the new asset storage settings:
S3_SERVICEURL=https://ewr1.vultrobjects.com
S3_BUCKET=squidex
S3_FOLDER=assets
S3_REGION=
S3_ACCESSKEY=9I2XHCLL43LKD2WLKDEN
S3_SECRETKEY=PUT_YOUR_SECRET_KEY_HERE
# the following variable is used to compartmentalize
# each app's assets in a separate folder
S3_FORCEPATHSTYLE=true