Another question for the community. I've noticed that when using dynamic routes, the route is not f...

# kobweb

[Ryan Scott]

Another question for the community. I've noticed that when using dynamic routes, the route is not found when I directly access it (as in, I paste the full URL into the address bar), but when I use the relative link to access it, the route is found. Has anyone else had this issue?

[David Herman]

Are you talking about when developing locally? Or is this in production?

[Ryan Scott]

The specific example is this:

https://www.fsryan.com/people -> click on ryan

That routes you to https://www.fsryan.com/people/ryan

However, if you were to paste that in the address bar, the route is not found.

[Ryan Scott]

This is the signature of the composable function for the page:

@Page("/people/{personId}")
@Composable
fun PersonPage() {

[David Herman]

Are you running your own ktor server, a Kobweb server, or is it some third party solution?

[Ryan Scott]

I'm running my own.

[Ryan Scott]

It's running in a docker container on linode.

[David Herman]

Running your own custom server or a Kobweb server?

[Ryan Scott]

A kobweb server.

[David Herman]

Let me try later today, it could be a bug. The Kobweb server is definitely supposed to handle dynamic routes assuming it's not a static layout export

[Ryan Scott]

Here's my Dockerfile:

FROM azul/zulu-openjdk:17.0.11-jdk

# In order to use this, the site must be pre-built

RUN mkdir /app
WORKDIR /app

# curl is used to download the cobweb-cli tarball.
RUN apt-get update && apt-get install -y curl

# the URL is actually a redirect; -L enables curl to follow the redirect and download the actual file
RUN curl -L -s -O <https://github.com/varabyte/kobweb-cli/releases/download/v0.9.15/kobweb-0.9.15.tar>
RUN tar -xf kobweb-0.9.15.tar && rm kobweb-0.9.15.tar
ENV PATH /app/kobweb-0.9.15/bin:$PATH

# Copy the necessary files below to use gradle to build the site
COPY . .

# exports the site and exposes the port based upon the site's configuration
RUN export PORT=$(kobweb conf --path site server.port)
EXPOSE $PORT

# Removes the packages we installed (with their dependencies because they are no longer needed
RUN apt-get purge --auto-remove -y curl && rm -rf /var/lib/apt/lists/*

# Starts up the site in production mode
CMD kobweb run --path site --notty --env prod --foreground --layout static

[David Herman]

Oh yeah you're running a static layout. You probably want fullstack layout in your case

[David Herman]

The static layout is for mimicking dumb servers that don't have API endpoints

[Ryan Scott]

Well--it doesn't have an API endpoint--it's just that I have multiple people that have profiles.

[Ryan Scott]

But I think you're onto something with how this is hosted.

[David Herman]

If you have dynamic routes that's probably a good enough reason

[Ryan Scott]

because locally, just pasting in the url works.

[David Herman]

It should be an easy fix for you -- try exporting with the fullstack layout and run it in your Dockerfile

[Ryan Scott]

Sure.

[David Herman]

With Kobweb, once you successfully download and run the site, then everything works locally at that point, including dynamic routes

[David Herman]

However requesting the site in the first place is tricky with dynamic routes

[Ryan Scott]

Just a quick follow-up. That worked.

[Ryan Scott]

At least in the docker container I am running locally, it worked--which should mean it works the same way with the one I deploy.