Deployment without docker possible?

[markthwain1797]

Hi everyone.
Since I use proxmox in my setup I'd like to install geopulse inside an LXC.
AFIK docker should not be installed inside an LXC and therefore I'm thinking about installing "manually" into an LXC.
Has anyone ever installed this way? Any help/recommendations is appreciated.

[tess1o]

Hello,

Technically you can deploy backend (java jar file or native app), frontend with "npm run dev" (from sources). What to do with Postgis database - it's a question, probably it can be also installed directly without Docker. For development I run backend and frontend without dockers, so it's possible to do. However, I don't have user-friendly instructions how do such setup

[codeicheck]

Hello,

I would also like to use it in a proxmox lxc and would love to install it natively instead of a docker container (actually I even tried to install it with docker in an lxc, but failed)

@markthwain1797 did you get it working and have any advices?

@tess1o any plans to add documentation how to setup and configure?

[tess1o]

Hello,

Ok, since there is higher demand than I expected I will check how to run everything without docker. I don't have proxmox so will do tests on Ubuntu machine. Most likely I will add CI steps to upload artifacts (like frontend html+css file, backend jar and native apps) to github and provide instructions how to run everything without docker). Alternative way is to manually extract required files from existing docker images but I feel it's not convenient for end users.

Expect some updates next week.

Thanks.

[markthwain1797]

Thank you very much. I didn't find the time yet to test an install myself.
I guess any install running on an (virtual) Ubuntu machine should be able to run on proxmox too.
I'll be happy to test.

[tess1o]

This request is still in progress. I'm trying to update CI/CD process to extract required files for backend/frontend and upload them to Github automatically. The instruction is ready but I need this CI/CD step completed first so I can test the instruction.

Stay tuned.

[tess1o]

Hello,

Here are the instructions: https://tess1o.github.io/geopulse/docs/getting-started/deployment/manual-installation

They work starting from the latest version: 1.16.1. I updated CI/CD actions to extract required artifacts so you can use them during bare metal deployment without docker.

I successfully tested the instructions on Ubuntu with ARM64 and AMD64.

Let me know if it works for you.

[markthwain1797]

Hi tess1o,

I really appreciate your work on Geopulse and your fast responses! I just finished setting it up in a Debian 12 LXC container (Proxmox) and the instructions were nearly perfect.

I have three small suggestions based on my experience with a minimal Debian template:

1. lsb-release Dependency: Standard Proxmox Debian templates don't come with lsb-release pre-installed. I had to manually define the release (bookworm) in pgdg.list. It might be worth mentioning apt install lsb-release as a prerequisite.

2. apt-key Deprecation: Since apt-key is now deprecated, I found it smoother to download the key directly to /usr/share/keyrings/.

3. Container Environments (No sudo): Minimal containers often don't have sudo by default. For users in a similar boat, I found that switching users with su - postgres or using runuser worked perfectly as a root alternative.

Thanks again for the great tool!

[tess1o]

Thank you for kind words and fast instruction verification. Just to confirm - did you manage to run it? I will check your comments and update the documentation accordingly.

[markthwain1797]

Yeah its running and currently importing the last 10+ years of Google location history.

[tess1o]

https://tess1o.github.io/geopulse/docs/getting-started/deployment/manual-installation

I have updated docs according to your comments (about lsb-release, apt-key, sudo).

[markthwain1797]

This is looking great 👍

[tess1o]

I'm going to close this discussion since looks like instructions are correct and good enough to get the app deployed without docker. Feel free to reopen it or create a new discussion/issue if anything else is needed.