Serves content tree structures very quickly.
A Server written in GoLang to mix and resolve content from different content sources, e.g. CMS, Blog, Shop and many other more. The server provides a simple to use API for non blocking content repository updates, to resolve site content by an URI or to get deep-linking multilingual URIs for a given contentID.
It's up to you how you use it and which data you want to export to the server. Our intention was to write a fast and cache hazzle-free content server to mix different content sources.
All you have to do is to provide a tree of content nodes as a JSON encoded RepoNode.
| Attribute | Type | Usage |
|---|---|---|
| Id | string | unique id to identify the node |
| MimeType | string | mime-type of the node, e.g. text/html, image/png, ... |
| LinkId | string | (symbolic) link/alias to another node |
| Groups | []string | access control |
| URI | string | URI |
| Name | string | name |
| Hidden | bool | hide in menu |
| DestinationId | string | alias / symlink handling |
| Data | map[string]interface{} | payload data |
| Nodes | map[string]*RepoNode | child nodes |
| Index | []string | contains the order of of nodes |
- If you do not want to build a multi-market website define a generic market, e.g. call it universe
- keep it lean and do not export content which should not be accessible at all, e.g. you are working on a super secret fancy new category of your website
- Hidden nodes can be resolved by their uri, but are hidden on nodes
- To avoid duplicate content provide a DestinationId ( = ContentId of the node you want to reference) instead of URIs
There is a PHP Proxy implementation for foomo in Foomo.ContentServer. Feel free to use it or to implement your own proxy in the language you love. The API should be easily to implement in every other framework and language, too.
$ contentserver -h
Serves content tree structures very quickly
Usage:
contentserver [command]
Available Commands:
completion Generate the autocompletion script for the specified shell
help Help about any command
http Start http server
socket Start socket server
version Print version information
Flags:
-h, --help help for contentserver
--log-format string log format (default "json")
--log-level string log level (default "info")
Use "contentserver [command] --help" for more information about a command.The content server supports pluggable storage backends for persisting repository snapshots.
By default, the server stores snapshots on the local filesystem:
contentserver http --history-dir /var/lib/contentserver http://example.com/repo.jsonFor cloud deployments, blob storage supports multiple providers via URL schemes:
contentserver http \
--storage-type blob \
--storage-blob-bucket gs://my-bucket \
--storage-blob-prefix contentserver/snapshots/ \
http://example.com/repo.jsonUses Application Default Credentials (ADC) for authentication.
contentserver http \
--storage-type blob \
--storage-blob-bucket "s3://my-bucket?region=us-east-1" \
--storage-blob-prefix contentserver/snapshots/ \
http://example.com/repo.jsonUses AWS SDK v2 default credential chain (environment variables, shared credentials file, IAM role).
contentserver http \
--storage-type blob \
--storage-blob-bucket azblob://my-container \
--storage-blob-prefix contentserver/snapshots/ \
http://example.com/repo.jsonUses Azure SDK default credential chain (environment variables, managed identity).
| Variable | Description |
|---|---|
CONTENT_SERVER_STORAGE_TYPE |
Storage type: filesystem (default) or blob |
CONTENT_SERVER_STORAGE_BLOB_BUCKET |
Blob storage URL with scheme (gs://, s3://, azblob://) |
CONTENT_SERVER_STORAGE_BLOB_PREFIX |
Object key prefix |
See gocloud.dev/blob for detailed authentication configuration.
Please refer to the CONTRIBUTING details and follow the CODE_OF_CONDUCT and SECURITY guidelines.
Distributed under LGPL 3.0 License, please see license file within the code for more details.
