BaseX Docker with BasexWeb file mount

100%

BaseX Docker with BasexWeb file mount

✓ Published0🌍 Public

Last edited Oct 20, 2016

Created on Oct 20, 2016

This example demonstrates how to launch a BaseX HTTP server within a Docker container, mounting local directories for both database storage and web application files. The `docker run` command configures the container with the `basex/basexhttp:latest` image, exposing ports 1984 and 8984 for client and HTTP access. It uses volume flags (`--volume`) to bind the host’s `~/BaseXData` and `~/BaseXWeb` directories to `/srv/BaseXData` and `/srv/BaseXWeb` inside the container, enabling persistent data storage and direct serving of web content. The setup runs interactively with the `-ti` flag, linking host filesystem paths to the server’s runtime environment.

AI-generated description

Similar vizzes

Loading thumbnail…

Files for Google Cloud Run

This example demonstrates a minimal HTTP service that returns the current time and date in JSON format, along with milliseconds since the Unix epoch. It uses BaseX’s RESTXQ module, specifically the `%rest:path` and `%output:method` annotations, to expose an XQuery function at the root path. The function formats the current time with `fn:format-time`, calculates epoch milliseconds by subtracting `xs:dateTime("1970-01-01T00:00:00-00:00")` from the current dateTime, and returns a JSON map. The included Dockerfile builds a container from `basex/basexhttp:latest`, copying the XQuery file into the webapp directory and launching BaseX HTTP on port 8080.

CCliffordAnderson

65% match

Loading thumbnail…

BaseX Server

This example shows a minimal RESTful web application built with BaseX, a native XML database, that serves XHTML pages for a poetry corpus. The code defines four GET endpoints—root, `/about`, `/credits`, and `/poem/{name}`—each returning a simple HTML page via the `view:display-contents` function. The implementation uses BaseX’s RESTXQ annotations (`%rest:path`, `%rest:GET`) and XQuery modules (`api.xqm`, `model.xqm`, `view.xqm`). The `model:credits` function supplies static HTML content, while the view module constructs the page skeleton. Data is hardcoded in XQuery, with no external datasets or JavaScript libraries involved.

CCliffordAnderson

65% match

Loading thumbnail…

Experiments with XQuery, RESTXQ, and MVC in BaseX

This example demonstrates a model-view-controller (MVC) architecture for serving a web-based corpus of Charles Baudelaire’s poems, with XQuery functions defining RESTful routes. It shows how BaseX’s RESTXQ annotations (`%rest:path`, `%rest:GET`) map URLs like `/`, `/about`, and `/contents` to controller functions, while a separate view module generates XHTML pages with Bootstrap styling. The model module queries the `fleurs-du-mal` collection to extract contributor names and poem titles for dynamic content. The code highlights XQuery’s role in both server-side logic and HTML templating, without any client-side JavaScript or charting libraries.

CCliffordAnderson

59% match

Loading thumbnail…

Docker Image for Neo4j with APOC and Spatial plugins

This example shows a Dockerfile that extends the official Neo4j image to include the APOC procedure library and the Neo4j Spatial plugin. The build process uses `curl` to download the APOC release JAR from GitHub and the spatial plugin from a Maven repository, then moves both into the plugins directory via shell commands. It relies on the `neo4j:latest` base image, configures symbolic links, and exposes ports 7474, 7473, and 7687 for HTTP, HTTPS, and Bolt access. The final `CMD` launches Neo4j directly.

CCliffordAnderson

55% match

Loading thumbnail…

docker compose sample

This example shows a multi-service Docker Compose setup for local development, defining a main application service along with MySQL and Adminer containers. The main service builds from a local context with a development target, mounts the current directory as a volume while preserving the container’s node_modules, exposes port 9229 for debugging, runs `npm run start:dev`, and loads environment variables from a `.env` file. The MySQL service uses the `mysql:latest` image with a native password authentication plugin, sets a root password, and persists data in a named volume. Adminer provides a web-based database client on port 8080, with all services connected via a custom `webnet` network.

66ewis

55% match

Loading thumbnail…

Gist 20b9219bcfa5ee87411a30118d3b6163

This example shows a shell script that automates the deployment of a Dockerized application on a fresh Ubuntu server. The script installs Docker and Docker Compose, creates a project directory, and copies a `docker-compose.yml` file into it. It then sets up a systemd service to run the compose file on boot and starts the application. The code uses `curl` to fetch remote files, `usermod` for user permissions, and `systemctl` to enable the service, with the actual container orchestration handled by `docker-compose` and `docker` commands.

CCliffordAnderson

54% match

Loading thumbnail…

Sample RestXQ

This example demonstrates how to route HTTP requests and return XML responses using the RESTXQ API in BaseX. It defines multiple endpoint paths, including dynamic segments like `hello/{$who}` and `post/{$post}`, alongside static routes for the root and about pages. A custom error handler returns a 404 status with an HTML page when a requested path does not match any defined route. The code imports a separate model module that provides a `say-hello` function, which is called by the hello endpoint to generate XML output.

CCliffordAnderson

53% match

Loading thumbnail…

Omeka-S on Debian w/Docker Compose

This example shows a complete setup for running Omeka-S, a digital-archive platform, on Debian using Docker Compose. The code first installs Docker and Docker Compose, then clones the `omeka-s-docker` repository and launches the containerized application with `sudo docker-compose up -d`. It relies on the Docker command-line interface and the Docker Compose tool, specifically using `docker-compose` to orchestrate the service. The gist does not include a data visualization; instead, it documents a server-deployment workflow, with the visible render being the terminal output from the install script and container startup. No charting or data-rendering libraries appear in this code.

CCliffordAnderson

53% match