You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This tutorial provides a comprehensive guide on using [Docling](https://docling-project.github.io/docling/) to convert PDFs into Markdown format using serverless fleets. It leverages cloud object storage for managing both the input PDFs and the resulting Markdown files. The process is streamlined using IBM’s Code Engine to build the Docling container, which is then pushed to a container registry. Users can run a serverless fleet, which autonomously spawns workers to run the Docling container for efficient, scalable conversion tasks.
This tutorial provides a comprehensive guide on using Serverless GPUs to perform batch inferencing which illustrates a generally applicable pattern where AI helps to extract information out of a set of unstructed data.
99
99
100
100
-[Metrics Collector](metrics-collector)<br>
101
101
Re-usable asset that helps to gain insights on the CPU and memory consumption of apps, jobs and builds.
102
102
103
+
-[Fotobox](fotobox)
104
+
Deploy your own Fotobox straight to the IBM Cloud access it directly from any device with browser and camera. Take pictures and view them all from your device.
105
+
106
+
103
107
## Samples
104
108
105
109
The samples are grouped by the main category of functionality that it
106
110
is demonstrating.
107
111
108
112
#### Apps
109
-
-[hello](hello)<br>
110
-
Very basic "hello world!" type of application written in Node.js. Start here!
111
113
-[helloworld](helloworld)<br>
112
-
Similar to [hello](hello) except this is written in golang and adds a few
113
-
bells-n-whistles to allow you to control what it does when invoked.
114
-
-[auth](auth)<br>
115
-
This shows how to setup an nginx proxy in-front of a private application
116
-
to ensure that only authorized people can access it.
117
-
-[bind-app](bind-app)<br>
118
-
This will create an instance of Event Streams in the IBM Cloud and then ask
119
-
Code Engine to bind it to an Application so we can access it from the App.
120
-
The credentials, etc. will be injected into the App via environment variables.
121
-
-[cecli](cecli)<br>
122
-
Show how to invoke the Code Engine CLI from within an App. This can be used
123
-
to then start additional Code Engine resources (Apps/Jobs) dynamically.
124
-
Same logic could be used in Batch Jobs.
125
-
-[sessions](sessions)<br>
126
-
Starts a stateful application that scales based on load. The state is kept
127
-
in an instance of Redis, also running within Code Engine. Demonstrates the
128
-
use of non-http components and private networking between components.
129
-
-[websocket](websocket)<nr>
130
-
Shows how to interact with an Application via WebSockets.
114
+
Very basic "hello world!" type of application writtin in golang. Start here!
115
+
-[auth-oidc-proxy](auth-oidc-proxy)<br>
116
+
This sample demonstrates how to configure an authentication/authorization layer that fronts any arbitrary Code Engine application. In principal, this pattern is pretty generic. To demonstrate it, we chose to implement it with OpenID Connect (OIDC), an authentication framework that is built on top of the OAuth 2.0 protocol.
117
+
118
+
#### Fleets
119
+
-[serverless-fleets](serverless-fleets)<br>
120
+
To learn how to simplify and optimize large-scale parallel computation with Serverless Fleets, you should start here!
131
121
132
122
#### Batch Jobs
133
123
-[helloworld](helloworld)<br>
134
124
This is another simple Batch Job sample, similar to the previous one, but
135
125
shows how to use environment variables to modify the behavior of the runtime
136
126
of the job.
127
+
-[Trusted Profiles](trusted-profiles)<br>
128
+
In the IBM Cloud, when authenticating with other services such as Cloud
129
+
Object Storage or Secrets Manager, using trusted profiles is a way to
130
+
authenticate without any API keys being used. This eliminates the risk of
131
+
those being leaked or stolen by a malicious user who uses them to access your
132
+
IBM Cloud resources.
137
133
-[cronjob](cronjob)<br>
138
134
This will create a Batch Job that will be invoked based on a cron
139
135
event. Meaning, it'll be executed based on a timer.
140
-
-[app2job](app2job)<br>
141
-
This will show how to submit a Job from an Application based on an incoming
142
-
HTTP request to the Application.
143
-
-[function2job](function2job)<br>
144
-
This will show how to submit a Job from a Function based on an incoming
145
-
HTTP request to the Function.
146
-
-[bind-job](bind-job)<br>
147
-
This will create an instance of Event Streams in the IBM Cloud and then ask
148
-
Code Engine to bind it to a Batch Job so we can access it from the Job. The
149
-
credentials, etc. will be injected into the Job via environment variables.
150
-
-[job2app](job2app)<br>
151
-
This will demostrate how to create a simple Batch Job and how to have it
152
-
communicate with an Application running within the same project.
153
-
-[job2vsi](job2vsi)<br>
154
-
The sample shows how a job can be used to spawn
155
-
[Virtual Server Instances (VSIs)]((https://www.ibm.com/cloud/virtual-servers))
156
-
in your IBM Cloud account and run workload on them.
0 commit comments