Squidex
  • Welcome to Squidex
  • Getting Started
    • Squidex Cloud
    • Installation Instructions
      • Platforms
        • Install on Kubernetes
        • Install on AWS (Deprecated)
        • Install on AWS EC2 using Docker
        • Install on Azure
        • Install on Azure using ARM
        • Install on Google Cloud Platform (GCP)
        • Install on Docker
        • Install on Heroku
        • Install on IIS
        • Install on Render
        • Install on Vultr
      • Configuration
        • Deploying the Image Resizer Service
      • Troubleshooting and Support
        • Diagnose Runtime Issues
        • Restoring Deleted Apps
      • Install Identity (Deprecated)
      • External Identity Providers
        • Azure AD (OAuth) with Squidex
    • Contributing and Developing
      • Building
      • Developing
      • Extensions
        • Custom Rule Action
      • Contributing
      • Architecture
      • Translating
      • Squidex Docs Program
    • Roadmap
    • Quick Start Guides
      • Vue.js Blog with Squidex
      • React.js Blog with Squidex
      • Angular Blog with Squidex
  • Documentation
    • Introduction and Use Case
    • Concepts
      • Apps
      • Teams
      • Schemas
        • Field Rules
      • Content
        • Scheduled Publishing
      • Assets
        • Querying Assets
      • Localization
      • Migrations
      • Roles & Permissions
      • Rules
        • Publish an Event to Azure Queues using Rules
        • Populate Elasticsearch Index
      • Backups
      • Subscriptions
        • App Subscriptions v/s Team Subscriptions
      • Notifications
      • Dashboard
      • Workflows
    • Software Development Kits
      • TypeScript
      • .NET
        • Version v14 (and Earlier)
        • Version v15 (and Later)
      • PHP
      • Java
    • Developer Guides
      • API
        • Authentication
        • Postman
        • Queries
        • Assets
      • Automation Tools (CLI)
      • Scripting
        • Scripting Helper Methods
      • Embed Content
      • Custom Workflows
      • Custom Editors
      • Custom Sidebars
      • Preview Content
      • Rule Formatting
        • Simple
        • Script
        • Liquid
      • Tutorials
        • Building a Blog with Squidex and Next.js
  • Next
    • Squidex 3.0: API Compatibility
Powered by GitBook
On this page
  • Why you Should Consider Vultr
  • When to Use Vultr
  • When Not to Use Vultr
  • Requirements
  • What is Included
  • Installation Guide
  • Step 1: Go to the Marketplace
  • Step 2: Deploy a New Server
  • Step 3: Wait For the Server to Spin Up
  • Step 4: Create a DNS Record
  • Step 5: Create the initial admin user
  • Configuring Object Storage
  • Step 1: Add Object storage
  • Step 2: Add a Bucket and a Folder
  • Step 3: Configure Asset Storage to Use S3

Was this helpful?

  1. Getting Started
  2. Installation Instructions
  3. Platforms

Install on Vultr

Vultr is a cheap provider of virtual or physical machines all over the world and is great if you need fast servers for low costs.

Why you Should Consider Vultr

When to Use Vultr

  • You want a server for low costs.

  • You do not need scalability.

  • You do not need integrated monitoring and logging.

  • You have a custom domain.

When Not to Use Vultr

  • You are already customer of another Cloud provider.

  • You need scalability for Squidex and the database.

Requirements

  • A custom domain or subdomain and the ability to create an A DNS record.

What is Included

This installation configures a Ubuntu 20.04 x64 machine with

  • Docker

  • Docker-Compose

Based on this setup 3 containers are installed:

  • Squidex

  • MongoDB for storing your data.

To work properly you need a DNS A record entry pointing to your machine, because caddy will issue a certificate using lets-encrypt.

Installation Guide

Step 1: Go to the Marketplace

Step 2: Deploy a New Server

  1. Select your target location close to your center of operation.

  2. Select the size of your machine. At least 4GB or memory with 2 virtual cores are recommended.

Step 3: Wait For the Server to Spin Up

It can take a while until your server is ready to be used.

Step 4: Create a DNS Record

Click your new server and wait until you get an IP address.

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.

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.

Step 1: Add Object storage

Step 2: Add a Bucket and a Folder

Navigate to the buckets tab and add a bucket.

Click on the bucket you've just created and add a folder.

Step 3: Configure Asset Storage to Use S3

Navigate to the overview tab and make note of your S3 credentials.

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):

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

Next, edit the /home/docker-compose.yml file to pass these environment variables onto the container:

squidex_squidex:
    image: "squidex/squidex:5"
    environment:
      ... previous variables are here
      - ASSETSTORE__TYPE=AmazonS3
      - ASSETSTORE__AMAZONS3__SERVICEURL=${S3_SERVICEURL}
      - ASSETSTORE__AMAZONS3__BUCKET=${S3_BUCKET}
      - ASSETSTORE__AMAZONS3__BUCKETFOLDER=${S3_FOLDER}
      - ASSETSTORE__AMAZONS3__REGIONNAME=${S3_REGION}
      - ASSETSTORE__AMAZONS3__ACCESSKEY=${S3_ACCESSKEY}
      - ASSETSTORE__AMAZONS3__SECRETKEY=${S3_SECRETKEY}
      - ASSETSTORE__AMAZONS3__FORCEPATHSTYLE=${S3_FORCEPATHSTYLE}

In your command line shell, update your Squidex container to use the new asset storage settings:

docker-compose up -d

Enjoy and have fun.

PreviousInstall on RenderNextConfiguration

Last updated 2 years ago

Was this helpful?

Caddy as reverse proxy and for https termination ().

Just follow the link:

Squidex is ready for use. If you visit your installation under 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.

Follow this link and proceed to add object storage to your account.

https://caddyserver.com/
https://www.vultr.com/marketplace/apps/squidex
https://mydomain.com
https://my.vultr.com/objectstorage/add/
Recommended server size
Waiting for the server
IP address is ready
Setup guide
Vultr object storage setup
Vultr object storage bucket list
Vultr object storage bucket list
Vultr object storage bucket list