#webservices — Public Fediverse posts

April 2026 WikiPathways update: 71 edits by 7 contributorsin and 2 new pathways the last month. More news at https://github.com/wikipathways/wikipathways-help/discussions/231 Accessible via #webservices, #rstats, #pathvisio and #cytoscape. https://www.wikipathways.org/index.php/Download_Pathways

#bioinformatics #openscience #opensource

Lucee in a Box: The Ultimate Guide to Containerized Dev Servers

2,726 words, 14 minutes read time.

The Modern ColdFusion Workspace: Transitioning to Lucee in a Box

The shift from traditional, monolithic server installations to containerized environments has fundamentally altered how we perceive modern development within the Lucee ecosystem. For years, the standard approach involved installing a heavy application server directly onto a local machine, often leading to a “polluted” operating system where various versions of Java and Lucee competed for resources and environment variables. By adopting a “Lucee in a Box” methodology, we decouple the application logic from the underlying hardware, allowing for a portable, reproducible, and lightweight development stack. This transition is not merely about convenience; it is a strategic move toward parity with production environments where high availability and rapid scaling are the norms. In this architecture, we utilize Docker to encapsulate the Lucee engine, the web server, and the necessary configuration files into a single unit that can be spun up or destroyed in seconds, ensuring that every member of a development team is working within an identical, script-driven environment.

However, the true complexity of this setup emerges when we move beyond simple “Hello World” examples and begin integrating with the existing corporate infrastructure. In my own workflow, I rely heavily on a network of internal web services that act as the primary conduit for data residing in our production databases. These services are vital because they provide a sanitized, governed layer of abstraction over raw SQL queries, ensuring that sensitive data is handled according to internal compliance standards. When we containerize Lucee, we aren’t just running a script; we are placing a small, isolated node into a complex network. The challenge then becomes ensuring this isolated container can “see” and communicate with those internal services as if it were a native part of the network, all while maintaining the security boundaries that containerization is designed to provide.

The Data Silo Crisis: Overcoming Networked Service Isolation

One of the most significant hurdles in modernizing a CFML stack is the inherent isolation of the Docker bridge network, which often creates what I call a “Data Silo” during local development. When a developer attempts to call an internal web service—perhaps a REST API that fetches real-time production metrics or user permissions—from within a container, the request often hits a wall because the container’s internal DNS does not naturally resolve local intranet addresses. This creates a frustrating disconnect where the application works perfectly in the legacy local install but fails within the containerized environment. This disconnect is more than a minor annoyance; it leads to significant delays in the development lifecycle as engineers struggle to pipe in the data necessary for testing complex business logic. Without a seamless connection to these internal services, the “Lucee in a Box” becomes an empty vessel, incapable of performing the data-intensive tasks required in a modern enterprise setting.

To resolve this, we must look at how the container perceives the outside world and how the host machine facilitates that visibility. In many corporate environments, production data is guarded behind strict firewall rules and SSL requirements that expect requests to originate from known entities. When I utilize internal web services to provide data from a production database, the Lucee container must be configured to pass through the host’s network or be explicitly granted access to the internal DNS suffixes. Failure to address this at the architectural level results in “unreachable host” errors or SSL handshake failures that can derail a project for days. By understanding that the container is a guest on your network, we can begin to implement the routing and trust certificates necessary to turn that siloed container into a fully integrated node capable of consuming live data streams securely and efficiently through modern CFScript syntax.

The Blueprint: Implementing Lucee and MariaDB via Docker Compose

To move from theory to implementation, we must define the orchestration layer that brings our environment to life. The docker-compose.yml file is the definitive source of truth for the development stack, eliminating the “it works on my machine” excuse by codifying the server version, database configuration, and network paths. In the professional workflow I advocate, this file sits at the root of your project. It defines a lucee service using the official Lucee image—optimized for performance—and a mariadb service to handle local data persistence. Crucially, we use volumes to map your local www folder directly into the container’s web root. This means that as you write your CFScript in your preferred IDE on your host machine, the changes are reflected instantly inside the container without requiring a rebuild or a manual file transfer.

The following configuration provides a professional-grade starting point. It establishes a dedicated network for our services and ensures that Lucee has the environment variables necessary to eventually automate its datasource connections. By mounting the ./www directory, we ensure our code remains on our host machine where it can be version-controlled, while the ./db_data volume ensures our MariaDB data persists even if the container is destroyed and recreated.

version: '3.8'

services:
  # The Database Engine
  mariadb:
    image: mariadb:10.6
    container_name: lucee_db
    restart: always
    environment:
      MYSQL_ROOT_PASSWORD: root_password
      MYSQL_DATABASE: dev_db
      MYSQL_USER: dev_user
      MYSQL_PASSWORD: dev_password
    volumes:
      - ./db_data:/var/lib/mysql
    networks:
      - dev_network

  # The Lucee Application Server
  lucee:
    image: lucee/lucee:5.3
    container_name: lucee_app
    restart: always
    ports:
      - "8080:8888"
    environment:
      # Injecting DB credentials for CFConfig or Application.cfc
      - DB_HOST=mariadb
      - DB_NAME=dev_db
      - DB_USER=dev_user
      - DB_PASSWORD=dev_password
      - LUCEE_ADMIN_PASSWORD=server_admin_pass
    volumes:
      - ./www:/var/www
      - ./config:/opt/lucee/web
    depends_on:
      - mariadb
    networks:
      - dev_network

networks:
  dev_network:
    driver: bridge

Deployment Strategy: Running Your New Containerized Stack

Once the docker-compose.yml file is in place, initializing the environment is a matter of a single terminal command. By executing docker-compose up -d from the root of your project directory, the Docker engine pulls the specified images, creates the isolated virtual network, and establishes the volume mounts. This process ensures that your MariaDB instance is ready to receive connections before the Lucee server fully initializes. For developers who rely on internal web services, this is where the containerized approach proves its worth. Because Lucee is running in an isolated network but can be configured to have access to the host’s bridge or external DNS, it can safely consume external APIs while maintaining a clean, local database for session state or cached production data. This setup provides the exact same architectural “feel” as a high-traffic production cluster, but contained entirely within your local hardware.

The beauty of this system lies in its maintenance-free nature and the elimination of the “dependency hell” that often plagues legacy ColdFusion developers. If you need to test your CFScript against a different version of Lucee or a newer patch of MariaDB, you simply update the version tag in the YAML file and run the command again. There is no need to uninstall software, clear registry keys, or worry about Java version conflicts on your host machine. This modularity is why I utilize internal web services to provide data from production into this local box; the container acts as a secure, high-speed proxy. You can pull the data you need via an internal API call, store it in the MariaDB container, and work in an isolated state without ever risking the integrity of the actual production database.

Root Cause: Why Standard Containers Fail at Internal Service Integration

The primary reason most off-the-shelf Lucee container configurations fail when attempting to consume internal web services is a fundamental lack of trust—specifically, the absence of internal SSL certificates within the Java KeyStore. When I use web services hosted within my network to provide data from a production database, those services are almost always secured via an internal Certificate Authority (CA) that is not recognized by the default OpenJDK installation inside the Lucee container. This results in the dreaded “PKIX path building failed” error the moment a cfhttp call is initiated via CFScript to an internal endpoint. To solve this, the Dockerfile must be modified to perform a “copy and import” operation during the image build phase, where the internal CA certificate is added to the Java security folder and registered using the keytool utility. This ensures that the underlying Java Virtual Machine (JVM) trusts the internal network’s identity, allowing for encrypted, secure data transmission from the production-proxy services to the local development environment.

Beyond the cryptographic hurdles, there is the issue of routing and “Host-to-Container” communication that often stymies developers new to the Docker ecosystem. In a standard Docker setup, the container is wrapped in a layer of Network Address Translation (NAT) that makes it difficult to reach services sitting on the developer’s physical host or the wider corporate VPN. To bridge this gap, we often utilize the extra_hosts parameter within our docker-compose configuration, which effectively injects entries into the container’s /etc/hosts file. This allows us to map a friendly internal domain name, like services.internal.corp, directly to the IP address of the host machine or the VPN gateway. By explicitly defining these routes, we bypass the limitations of Docker’s isolated bridge and enable the Lucee engine to reach out to the web services that house our production data. This architectural “handshake” between the containerized Lucee instance and the physical network is the secret sauce that transforms a basic dev box into a high-fidelity replica of the production ecosystem.

Deep Dive: Consuming Internal Web Services via CFScript

With the network and security infrastructure in place, we can finally focus on the implementation layer: the CFScript that handles the data exchange. In a modern Lucee in a Box setup, I favor a service-oriented architecture where a dedicated DataService.cfc handles all interactions with the internal network. Using the http service in CFScript, we can construct requests that include the necessary authentication headers, such as JWT tokens or API keys, required by the internal production data services. The beauty of this approach is that the CFScript remains agnostic of the container’s physical location; as long as the Docker networking layer is correctly mapping the service URL to the internal network, the cfhttp call proceeds as if it were running on a native server. This allows us to maintain a clean, readable codebase that utilizes the latest CFScript features, such as cfhttp(url=targetURL, method="GET", result="local.apiResponse"), while the heavy lifting of network routing is handled by the Docker daemon.

The real power of this integration is realized when we use these internal web services to populate our local MariaDB instance with a “snapshot” of production-like data. Rather than dealing with massive, cumbersome database dumps that can compromise data privacy, we can write an initialization script in CFScript that queries the internal web services for the specific datasets required for a given task. This script can then parse the returned JSON and perform a series of queryExecute() commands to populate the local MariaDB container. This “just-in-time” data strategy ensures that the developer is always working with relevant, fresh data without the security risks associated with a direct connection to the production database. By leveraging the containerized Lucee instance as a smart bridge between internal network services and local storage, we create a development environment that is not only isolated and secure but also incredibly data-rich and performant.

Environment Variable Injection: The CFConfig and CommandBox Synergy

To achieve a truly “hands-off” configuration within a Lucee in a Box environment, we must move away from the manual web-based administrator and toward a purely scripted setup. This is where the combination of CommandBox and the CFConfig module becomes indispensable. By using a .cfconfig.json file or environment variables prefixed with LUCEE_, we can define our MariaDB datasource connections, internal web service endpoints, and mail server settings without ever clicking a button in the Lucee UI. In a professional workflow, this means the docker-compose.yml file serves as the master controller, injecting credentials and network paths directly into the Lucee engine at runtime. For instance, by setting LUCEE_DATASOURCE_MYDB as an environment variable, the containerized engine automatically constructs the connection to the MariaDB container, ensuring that our CFScript-based queryExecute() calls have a reliable target the moment the server is healthy.

This approach is particularly powerful when dealing with the internal web services that provide our production data. Since these services often require specific API keys or internal proxy settings, we can store these sensitive values in an .env file that is excluded from our Git repository. When the container starts, these values are mapped into the Lucee process, allowing our CFScript logic to access them via system.getEnv(). This ensures that our local development environment remains a mirror of our production logic while maintaining a strict separation of concerns between the application code and the infrastructure-specific secrets. By automating the configuration layer, we eliminate the risk of manual setup errors and ensure that every developer on the team can spin up a fully functional, networked-aware Lucee instance in a single command.

Advanced Networking: Bridged Access to Production-Proxy Services

The final piece of the Lucee in a Box puzzle involves fine-tuning the Docker network to handle the high-latency or high-security requirements of internal web services. When our CFScript makes a request to a service that pulls from a production database, we are often traversing multiple layers of internal routing, including VPNs and load balancers. To optimize this, we can configure our Docker bridge network to use specific MTU (Maximum Transmission Unit) settings that match our corporate network’s infrastructure, preventing packet fragmentation that can lead to mysterious request timeouts. Furthermore, by utilizing Docker’s aliases within the network configuration, we can simulate the production URL structure locally. This means our CFScript can call https://api.internal.production/ both in the dev container and the live environment, with Docker handling the redirection to the appropriate internal service endpoint based on the environment context.

Beyond simple connectivity, we must also consider the performance of these data-heavy web service calls. In a containerized environment, I often implement a caching layer within Lucee that stores the JSON payloads returned from our internal services into the local MariaDB instance or a RAM-based cache. By using CFScript’s cachePut() and cacheGet() functions, we can significantly reduce the load on our internal network and the production database proxy. This “lazy-loading” strategy allows us to develop complex features with the speed of local data access while still maintaining the accuracy of production-sourced information. This architectural decision—balancing live service integration with local persistence—represents the pinnacle of the Lucee in a Box philosophy, providing a development experience that is as fast as it is faithful to the real-world environment.

Conclusion: The Future of Scalable CFML Development

Adopting a “Lucee in a Box” strategy is more than just a trend in containerization; it is a fundamental shift toward professional-grade, reproducible engineering. By strictly defining our environment through docker-compose.yml, automating our security through SSL injection in the Dockerfile, and utilizing CFScript to bridge the gap between internal web services and local MariaDB storage, we create a stack that is resilient to “configuration drift.” This setup allows us to treat our development servers as ephemeral, disposable assets that can be rebuilt at a moment’s notice to match evolving production requirements. As the Lucee ecosystem continues to mature, the ability to orchestrate these complex data flows within a containerized boundary will remain the hallmark of a high-performing development team, ensuring that we spend less time debugging infrastructure and more time writing the logic that drives our applications forward.

Call to Action

If this post sparked your creativity, don’t just scroll past. Join the community of makers and tinkerers—people turning ideas into reality with 3D printing. Subscribe for more 3D printing guides and projects, drop a comment sharing what you’re printing, or reach out and tell me about your latest project. Let’s build together.

D. Bryan King

Sources

• Lucee Official Documentation: Lucee Docker Images
• Ortus Solutions: CommandBox Docker Documentation
• NIST SP 800-190: Application Container Security Guide
• Docker Documentation: Bridge Network Driver and Architecture
• IANA: Service Name and Transport Protocol Port Number Registry
• MITRE CWE-601: URL Redirection to Untrusted Site (Internal Service Security)
• Docker Engine: Dockerfile Reference and Best Practices
• CFConfig: Environment Variable Integration for Lucee
• CIS Benchmarks: Docker Community Edition Benchmark
• IETF RFC 7519: JSON Web Token (JWT) for Internal Service Auth
• Wireshark User Guide: Analyzing Internal Network Traffic
• Oracle Java SE Security: Standard Algorithm Names (TLS Support for Lucee)

Disclaimer:

The views and opinions expressed in this post are solely those of the author. The information provided is based on personal research, experience, and understanding of the subject matter at the time of writing. Readers should consult relevant experts or authorities for specific guidance related to their unique situations.

Related Posts

Rate this:

March 2026 WikiPathways update: 45 edits by 5 contributors in the last month. More news at https://github.com/wikipathways/wikipathways-help/discussions/227

Accessible via #webservices, #rstats, #pathvisio and #cytoscape. Supported by #awsopen. https://www.wikipathways.org/index.php/Download_Pathways

#bioinformatics #openscience #opensource

Use Protocols, not Services : 100% aligné avec l'approche, mais dans la réalité, c'est parfois plus difficile à appliquer qu'on ne le pense (j'espère que #protonmail va ouvrir son utilisation et non se limiter à son bridge).

Quant à Discord, je suis ouvert aux suggestions d'un service similaire qui utilise un protocole officiel.

https://notnotp.com/notes/use-protocols-not-services/

#protocols #webservices

REST Webservices in Java klingen am Anfang gerne etwas abstrakt: HTTP, Ressourcen, JSON, Statuscodes, JAX-RS - ziemlich viele Begriffe auf einmal. In der Praxis ist das aber weniger Magie, als es aussieht. Wenn du Java schon ein bisschen kennst, kannst du mit ein paar Grundbausteinen sehr schnell de

https://magicmarcy.de/rest-webservices-in-java

#REST #JSON #HTTP #POST #Ressource #Webservices #MediaType #Path #WildFly #ApplicationPath #Programming

February 2026 WikiPathways update: 95 edits by 9 contributorsin the last month. More news at https://github.com/wikipathways/wikipathways-help/discussions/221 Accessible via #webservices, #rstats, #pathvisio and #cytoscape. Supported by #awsopen. https://www.wikipathways.org/index.php/Download_Pathways

#bioinformatics #openscience #opensource

FYI: EzEsri, a public #GIS #data directory of #government #ArcGIS feature services https://ezesri.com/directory

#GISchat #geospatial #resources #WebServices #govtech #esri #mapping @esri @esrifederalgovt @esrislgov @arcgispro @arcgisonline @esritraining @urisa

January 2026 WikiPathways update: 134 edits by 3 contributorsin the last month. More news at https://github.com/wikipathways/wikipathways-help/discussions/213 Accessible via #webservices, #rstats, #pathvisio and #cytoscape. Supported by #awsopen. https://www.wikipathways.org/index.php/Download_Pathways

#bioinformatics #openscience #opensource

December 2025 WikiPathways release: 840 edits by 8 contributors and 9 new pathways (4 in screenshots). Accessible via #webservices, #rstats, #pathvisio and #cytoscape.

https://www.wikipathways.org/#download

#bioinformatics #elixirnl

#Amazon #WebServices #AWS a dévoilé mardi de nouvelles fonctionnalités pour #AgentCore, sa #plateforme d' #agents #IA #AI. Des #contrôles de #sécurité et d'évaluation facilitent enfin le déploiement d' #agents #autonomes en #production.

https://www.clubic.com/actualite-589843-amazon-revele-comment-rendre-les-agents-ia-totalement-fiables-en-production.html

My PikaPod is stuck loading. Feeling like I'm waiting centuries for the service to start up! It's the little IT moments that test your patience the most.

#PikaPods #SelfHosting #TechHumour #PodLoading #ServerLife #IT #OpenSource #AppHosting #TechStruggles #WaitingGame #Computers #DigitalAutonomy #Web #Technology #Troubleshooting #Patience #Humour #GeekLife #WebServices #Infra

November 2025 WikiPathways update: 686 edits by 6 contributors and 10 new pathways in the last month. Accessible via #webservices, #rstats, #pathvisio and #cytoscape.

Supported by #awsopen. https://www.wikipathways.org/index.php/Download_Pathways

#bioinformatics #openscience #opensource

This is my November Fedi reminder that I am a talented #Java developer looking for a developer position either remote, or based in Tampa, FL. I have some neat skills, like #CoreJava, #JavaEE, #Spring Frameworks, #WebServices, #Kafka, and many others. If you want to set up a call, I promise I will respond. (And I only ask you apply the same rule.)

Oh yeah, something-something-pumpkin-spice; now it's a November post.

#FediHire #fedijob #PumpkinSpice

‪🎙️ Python Bytes 455: Gilded Python and Beyond
https://pythonbytes.fm/episodes/show/455/gilded-python-and-beyond
with @brianokken and @mkennedy
#Python #CLIs #webservices #GC #Pets #Agentic #AI #TDD

⏳ Implementare un WebService SOAP con PHP
Come creare un servizio SOAP utilizzando esclusivamente PHP...

👉 https://www.selectallfromdual.com/blog/1656

#php #soap #webservices

October 2025 WikiPathways update: 129 edits by 10 contributors and 5 new pathways in the last month. Accessible via #webservices, #rstats, #pathvisio and #cytoscape. Supported by #awsopen. https://www.wikipathways.org/index.php/Download_Pathways

#bioinformatics #openscience #opensource

🤓 Oh, the joys of reading about how technology should be a festering mess of warts! Apparently, watching a #YouTube video is now the pinnacle of intellectual endeavor for those pondering the eternal mysteries of web services. 🤦‍♂️ The talk promises #insights on "htmx," but delivers a sermon on bridge-building instead—because what coder doesn't need architectural advice? 🏗️
https://entropicthoughts.com/you-want-technology-with-warts #techdebate #webservices #htmx #architecture #HackerNews #ngated

I'm busy finishing my presentation about my websites on geospatial webservices with data for Belgium. If you want to come and hear me talk about what that is and how and why I make these websites, you can hear me tell me all about it at FOSS4G Belgium this thursday in Brussels at 15h50 in the "Qleur Café" room. You can still get tickets on https://www.foss4g.be.

#FOSS4G #Belgium #GIS #Geospatial #webservices

Unlock Odoo 18 Web Services for ultimate integration! Our guide reveals 5 secrets to mastering XML-RPC & JSON-RPC. Connect apps seamlessly. #Odoo18 #WebServices #APIIntegration #OdooTutorial #TechGuide #ERPIntegration

https://teguhteja.id/odoo-18-web-services-ultimate-integration-secrets/?utm_source=mastodon&utm_medium=jetpack_social

September 2025 WikiPathways update: 261 edits by 6 contributors and 13 new pathways in the last month. Accessible via #webservices, #rstats, #pathvisio and #cytoscape. Supported by #awsopen. https://www.wikipathways.org/index.php/Download_Pathways

#bioinformatics #openscience #opensource

The first copies of Mastering #RESTful #webservices with #Java have just arrived! (See more at love2integrate.com)

June 2025 WikiPathways release: 338 edits by 15 contributors and 9 new pathways. https://data.wikipathways.org/

Accessible via #webservices, #rstats, Pathvisio, and Cytoscape.

🧠 L’Inist était à la #JDLS2025 !
Hier, lors de la Journée Deep Learning pour la Science, Léo Gaillard & Lucas Anki (Istex TDM, Inist) ont présenté un poster sur des web services de deep learning pour enrichir des métadonnées 📊
👉 services.istex.fr
#JDLS2025 #IA #DeepLearning #ScienceOuverte #Inist #ISTEX #WebServices

If you’re in the mood for web services today, check out @frontenddogma’s web services archives! 😬

https://frontenddogma.com/topics/web-services/

#webdev #webservices

May 2025 WikiPathways release: 491 edits by 9 contributors and 8 new pathways.

Accessible via #webservices, #rstats, Pathvisio, and Cytoscape.

#biology #bioinformatics

Follow-up questions:

➡️ Aside from “work on the website” what did that person do? What else was their responsibility?

➡️ If you had to write a description for that title today in 2025, what responsibilities would you include?

#WebDevelopment #WebsiteManagement #Webmaster #JobTitles #AskFedi #WebServices #SysAdmin #AskFediverse

Once upon a time, working on a website granted you the title of "Webmaster". As the Web evolved, more specialized roles took over and the title fell out of favor.

Searching for it now, I don't find many job listings for "Webmaster". So now I'm curious: how far removed from that job title are we?

When was the last time you heard of someone with “webmaster” as their actual job title?

#WebDevelopment #WebsiteManagement #Webmaster #JobTitles #Poll #AskFedi #WebServices #SysAdmin #AskFediverse

Thunderbird kündigt iOS-Mailing-App an – eine aufregende Erweiterung für das Projekt

https://techupdate.io/dienste/thunderbird-kuendigt-ios-mailing-app-an-eine-aufregende-erweiterung-fuer-das-projekt/50263/

#technews #opensource #thunderbird #thunderbirdpro #iosapp #mailclient #emailapp #webservices

October 2024 WikiPathways update: 167 edits by 4 contributors and 2 new pathways in the last month. Accessible via #webservices, #rstats, #pathvisio and #Cytoscape Supported by #AWSOpen

https://wikipathways.org/index.php/Download_Pathways

#bioinformatics #openscience #opensource

Пример создания Full Stack проекта, используя функциональное тестирование как инструмент дизайна(продолжение)

Пример создания Full Stack проекта, используя функциональное тестирование как инструмент дизайна(продолжение) API часть и релиз проекта Продолжение...

https://habr.com/ru/articles/849770/

#python #functional_testing #architecture #api #backendразработка #backend_as_a_service #fullstack #automation_testing #webservices #web_developer

September 2024 WikiPathways update: 179 edits by 6 contributors and 4 new pathways in the last month. Accessible via #webservices, #rstats, #pathvisio and #cytoscape. Supported by #awsopen . https://wikipathways.org/index.php/Download_Pathways

#bioinformatics #openscience #opensource

Google is going to disable ‘goo.gl’ shortened URLs in 2025

https://stackdiary.com/google-is-going-to-disable-goo-gl-shortened-urls-in-2025/

#Google #goo #shortener #URL #links #shutdown #discontinue #deprecated #web #tech #developers #marketers #digital #internet #linkrot #Firebase #adaptation #transition #technews #webtools #SEO #analytics #redirects #brokenlinks #update #evolution #techgiants #webservices #innovation #disruption #dependency

GoDaddy slapped with an antitrust lawsuit by a DNS company

https://stackdiary.com/godaddy-slapped-with-an-antitrust-lawsuit-by-a-dns-company/

#Antitrust #Lawsuit #GoDaddy #Entri #DNS #DomainConnect #Competition #Monopoly #Innovation #TechNews #LegalBattle #ConsumerRights #MarketFairness #DigitalEconomy #Internet #Technology #CourtCase #BusinessEthics #Software #SaaS #Regulation #Controversy #LegalAction #OpenSource #MarketPower #CustomerChoice #WebServices #TechIndustry #LegalIssues #DomainNames

May 2024 WikiPathways release: 110 edits by 10 contributors and 6 new pathways. Accessible via #webservices and in PathVisio, Cytoscape. Supported by #AWSOpen https://wikipathways.org/#download #bioinformatics #openscience #opensource

March 2024 WikiPathways release: 542 edits by 9 contributors and 10 new pathways. Accessible via #webservices and in #PathVisio, #Cytoscape. Supported by AWSOpen. https://wikipathways.org/#download #bioinformatics #openscience #opensource

REST reconsidered: A lament on how the distributed systems term REST has gotten watered down
https://htmx.org/essays/how-did-rest-come-to-mean-the-opposite-of-rest/
#webservices #programming #xmlrpc #soap #rest #http #rpc #api #+

Py3DEP [hydroclimate analysis]
--
https://pypi.org/project/py3dep/ <-- link to app / resources
--
“Py3DEP is a part of [PyGeoUtils] HyRiver software stack that is designed to aid in hydroclimate analysis through web services. This package provides access to the 3DEP database which is a part of the National Map services. The 3DEP service has multi-resolution sources and depending on the user-provided resolution, the data is resampled on the server-side based on all the available data sources. Py3DEP returns the requests as xarray dataset…”
#GIS #spatial #mapping #Py3DEP #PyGeoUtils #HyRiver #softwarestack #elevation #3DEP #USGS #NationalMap #opendata #processing #spatialanalysis #hydroclimate #water #hydrology #webservices #xarray
@HyRiver @USGS

[FEMA] National Flood Hazard Layer [open spatial data]
--
https://www.fema.gov/flood-maps/national-flood-hazard-layer <-- shared spatial data resource
--
#GIS #spatial #mapping #gischat #water #hydrology #flood #flooding #extremeweather #opendata #FEMA #risk #hazard #NationalFloodHazardLayer #NFHL #spatialdata #floodrisk #webmap #datadownloader #FIRM #insurance #FloodInsuranceRateMap #webservices #MSC #KMZ
@FEMA

@b0rk @randomgeek @hbuchel It’s funny how most “#RESTful” #WebServices have similarly missed the full point of @fielding’s actual #REST “just normal web things” style by not using hypertext as the engine of application state (#HATEOAS).

They’re just replaying all of #SOAP’s and #CORBA’s sins by relying on a fixed interface that is either revealed through documentation or an #InterfaceDescriptionLanguage like #OpenAPI.

July 2023 WikiPathways release: 232 edits by 32 contributors and 12 new pathways. Accessible via #webservices and in #PathVisio, #Cytoscape Supported by AWSOpen. https://wikipathways.org/#download #bioinformatics #openscience #opensource

@fuzzix I have bad news for you: #SOAP came out of that same era. It was an over-engineered adaptation by #Microsoft and @w3c of @davew’s #XMLRPC

Mind you, the entire #XML-based #WebServices stack of standards is being re-accreted on top of #JSON with efforts like #OpenAPI and JSON Schema. The final and once-again neglected piece is automated service discovery à la #UDDI

@fuzzix I have bad news for you: #SOAP came out of that same era. It was an over-engineered adaptation by #Microsoft and @w3c of @davew’s #XMLRPC

Mind you, the entire #XML-based #WebServices stack of standards is being re-accreted on top of #JSON with efforts like #OpenAPI and JSON Schema. The final and once-again neglected piece is automated service discovery à la #UDDI

@fuzzix I have bad news for you: #SOAP came out of that same era. It was an over-engineered adaptation by #Microsoft and @w3c of @davew’s #XMLRPC

Mind you, the entire #XML-based #WebServices stack of standards is being re-accreted on top of #JSON with efforts like #OpenAPI and JSON Schema. The final and once-again neglected piece is automated service discovery à la #UDDI

@fuzzix I have bad news for you: #SOAP came out of that same era. It was an over-engineered adaptation by #Microsoft and @w3c of @davew’s #XMLRPC

Mind you, the entire #XML-based #WebServices stack of standards is being re-accreted on top of #JSON with efforts like #OpenAPI and JSON Schema. The final and once-again neglected piece is automated service discovery à la #UDDI

@fuzzix I have bad news for you: #SOAP came out of that same era. It was an over-engineered adaptation by #Microsoft and @w3c of @davew’s #XMLRPC

Mind you, the entire #XML-based #WebServices stack of standards is being re-accreted on top of #JSON with efforts like #OpenAPI and JSON Schema. The final and once-again neglected piece is automated service discovery à la #UDDI

@greener77176
Seule vraie solution, un #oslibre type #gnulinux (ex: #trisquellinux ) et des #logicielslibres (UNIQUEMENT #libre) sur un pc équipé de #Libreboot
Et utiliser des #webservices respectueux de la #vieprivee (en plus des #gafam il y en a d'autres)
Et sur votre #webbrowser préféré (#firefox pour moi ou #abrowser sur #trisquel) j'ai ajouté #privacybadger et #ublockorigin

Reste à trouver un #librephone digne de ce nom.

@cpolitic @Grrr
@nitot