Typesense on Railway platform
aznian2g
HOBBYOP

3 months ago

Has anyone deployed TypeSense before?

If so is it possible through the hobby plan?

I'm trying to figure out how to set volumes, which is a requirement for TypeSense.

If all of this is possible, how can I customize TypeSense? Is there a login dashboard where you can configure the platform on Railway?

Solved$10 Bounty

Pinned Solution

xmphdalf
HOBBY

3 months ago

Yes, Typesense runs fine on Railway, including the Hobby plan.

  1. Easiest path: use a template. There are ready-made ones on the

    marketplace (search "Typesense" - e.g. railway.com/deploy/typesense-latest,

    or "typelens" if you also want a web dashboard bundled). One click gives

    you the service + volume + env vars preconfigured.

  2. Hobby plan: yes. Volumes are included on Hobby, up to 5 GB (resizable

    from service settings). That's plenty for most Typesense indexes.

  3. Volumes manually: deploy the typesense/typesense Docker image, then

    right-click the project canvas (or service settings -> volumes) ->

    Attach Volume -> mount path /data. Then set these variables:

    TYPESENSE_DATA_DIR=/data

    TYPESENSE_API_KEY=

    The volume is required because Typesense persists indexes and Raft

    state to disk - without it you lose all data on every redeploy.

  4. Customization / dashboard: Typesense has no built-in login UI - it's

    headless, configured entirely through env vars / CLI flags and its

    REST API (authenticated with TYPESENSE_API_KEY). If you want a UI,

    deploy a community dashboard alongside it (e.g. the typelens template

    above, or self-host typesense-dashboard as a second Railway service

    pointed at your Typesense URL).

2 Replies

Railway
BOT

3 months ago

This thread has been opened as a bounty so the community can help solve it.

Status changed to Open Railway • 3 months ago


xmphdalf
HOBBY

3 months ago

Yes, Typesense runs fine on Railway, including the Hobby plan.

  1. Easiest path: use a template. There are ready-made ones on the

    marketplace (search "Typesense" - e.g. railway.com/deploy/typesense-latest,

    or "typelens" if you also want a web dashboard bundled). One click gives

    you the service + volume + env vars preconfigured.

  2. Hobby plan: yes. Volumes are included on Hobby, up to 5 GB (resizable

    from service settings). That's plenty for most Typesense indexes.

  3. Volumes manually: deploy the typesense/typesense Docker image, then

    right-click the project canvas (or service settings -> volumes) ->

    Attach Volume -> mount path /data. Then set these variables:

    TYPESENSE_DATA_DIR=/data

    TYPESENSE_API_KEY=

    The volume is required because Typesense persists indexes and Raft

    state to disk - without it you lose all data on every redeploy.

  4. Customization / dashboard: Typesense has no built-in login UI - it's

    headless, configured entirely through env vars / CLI flags and its

    REST API (authenticated with TYPESENSE_API_KEY). If you want a UI,

    deploy a community dashboard alongside it (e.g. the typelens template

    above, or self-host typesense-dashboard as a second Railway service

    pointed at your Typesense URL).


xmphdalf

Yes, Typesense runs fine on Railway, including the Hobby plan. 1. Easiest path: use a template. There are ready-made ones on the marketplace (search "Typesense" - e.g. railway.com/deploy/typesense-latest, or "typelens" if you also want a web dashboard bundled). One click gives you the service + volume + env vars preconfigured. 2. Hobby plan: yes. Volumes are included on Hobby, up to 5 GB (resizable from service settings). That's plenty for most Typesense indexes. 3. Volumes manually: deploy the typesense/typesense Docker image, then right-click the project canvas (or service settings -> volumes) -> Attach Volume -> mount path /data. Then set these variables: TYPESENSE_DATA_DIR=/data TYPESENSE_API_KEY=<generate a long random string> The volume is required because Typesense persists indexes and Raft state to disk - without it you lose all data on every redeploy. 4. Customization / dashboard: Typesense has no built-in login UI - it's headless, configured entirely through env vars / CLI flags and its REST API (authenticated with TYPESENSE_API_KEY). If you want a UI, deploy a community dashboard alongside it (e.g. the typelens template above, or self-host typesense-dashboard as a second Railway service pointed at your Typesense URL).

aznian2g
HOBBYOP

3 months ago

Thank you so much!


Status changed to Solved uxuz • 3 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...