gdsl.org valid
Data to Science Engine Workshop
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-27T09:28:46.427Z. Cached copy · Source on gdsl.org
# Data to Science Engine Workshop
## Data to Science Engine Workshop
- [Overview](https://docs.gdsl.org/data-to-science-engine-workshop/overview.md)
- [Meet the instructors](https://docs.gdsl.org/data-to-science-engine-workshop/overview/meet-the-instructors.md)
- [Agenda](https://docs.gdsl.org/data-to-science-engine-workshop/overview/agenda.md): Agenda for NAPPN 2024 workshop
- [Docker 101](https://docs.gdsl.org/data-to-science-engine-workshop/deployment/docker-101.md): This section includes background information on Docker and instructions for installing Docker Desktop.
- [Getting Started](https://docs.gdsl.org/data-to-science-engine-workshop/deployment/docker-101/getting-started.md): Instructions for installing Docker Deskop.
- [Required software (Windows)](https://docs.gdsl.org/data-to-science-engine-workshop/deployment/docker-101/getting-started/required-software-windows.md): Instructions for installing prerequisite software in Windows.
- [Required software (macOS)](https://docs.gdsl.org/data-to-science-engine-workshop/deployment/docker-101/getting-started/required-software-macos.md): Instructions for installing prerequisite software in macOS.
- [Required software (Linux)](https://docs.gdsl.org/data-to-science-engine-workshop/deployment/docker-101/getting-started/required-software-linux.md): Instructions for installing prerequisite software in Linux.
- [Code editor (optional)](https://docs.gdsl.org/data-to-science-engine-workshop/deployment/docker-101/getting-started/code-editor-optional.md): Extra software you may like to install.
- [Building Docker images from source](https://docs.gdsl.org/data-to-science-engine-workshop/deployment/building-docker-images-from-source.md): This section contains instructions for building Docker images from the D2S source code.
- [Obtaining source code](https://docs.gdsl.org/data-to-science-engine-workshop/deployment/building-docker-images-from-source/obtaining-source-code.md): These steps will take you through the process of obtaining the D2S source code from GitHub.
- [Set up environment variables](https://docs.gdsl.org/data-to-science-engine-workshop/deployment/building-docker-images-from-source/set-up-environment-variables.md): These steps will take you through the process of setting up the required environment variables for running D2S.
- [Building the Docker images](https://docs.gdsl.org/data-to-science-engine-workshop/deployment/building-docker-images-from-source/building-the-docker-images.md): These steps will take you through the process of building Docker images for the frontend and backend application services locally.
- [Running Docker containers using local and remote images](https://docs.gdsl.org/data-to-science-engine-workshop/deployment/running-docker-containers-using-local-and-remote-images.md)
- [Using local and remote images](https://docs.gdsl.org/data-to-science-engine-workshop/deployment/running-docker-containers-using-local-and-remote-images/using-local-and-remote-images.md): These steps
…
Related sites
Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| docker.com | Docker Documentation | documentation DevOps and observability Developer tools +1 | US | 75 | ✓ | ✓ | |
| gaiodataos.com | Gaio DataOS | documentation Data and analytics | — | 46 | ✓ | ✓ | |
| ooos.top | Docker Documentation | documentation Documentation and reference Developer tools | — | 50 | ✓ | ✓ | |
| collabnix.com | Collabnix | documentation Infrastructure DevOps and observability +2 | DK | 56 | ✓ | ||
| coder.com | Coder | documentation AI agents and MCP Developer tools +1 | US | 64 | ✓ | ✓ | |
| inferless.com | Inferless | documentation AI and machine learning Developer tools +1 | US | 51 | ✓ | ✓ | |
| workshop.ai | Workshop | documentation AI agents and MCP Developer tools | US | 45 | ✓ | ✓ | |
| stagewise.io | stagewise Docs | documentation AI and machine learning AI agents and MCP +2 | — | 45 | ✓ | ✓ |
Machine-readable: GET /v1/resolve?q=gdsl.org · GET /v1/domain/gdsl.org · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage gdsl.org, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for gdsl.org:
1. POST https://agentwebmap.com/v1/sites/gdsl.org/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://gdsl.org/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/gdsl.org/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/gdsl.org).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.