Installation without docker?

[parszab]

Would it be possible to provide an install/upgrade quide without docker? I have a small VPS where I'd like to try Pinry, but would prefer to avoid using docker.

[jgwehr]

Related questions:

• Non docker（LXC Container） install documentation? #309
• intallation without docker #357

At the moment, it doesn't seem possible without familiarity with the underlying frameworks. There are several free hosting services which support Docker if you're just looking to try it out!

[parszab]

At the moment, it doesn't seem possible without familiarity with the underlying frameworks. There are several free hosting services which support Docker if you're just looking to try it out!

I honestly (and respectfully) don't understand how we got here. I (and I assume many) know how to set up a web-server, a database, deploy a framework. I have a VPS where I run a bunch of things and I don't want to containerize all the tools I install. I think this is a very bad direction, that some developers only provide docker images. A short but focused wiki could describe install instructions. Going always a "level higher" is really not what we should do.

[jimj316]

I would like to second the request for non-Docker installation. I have multiple services running on my server via NGINX, and want to serve Pinry as one of these services in a sub-directory, but this project seems to have been built with the assumption that it's the only service running on a system. It's very unclear how common sysadmin tasks (changing the subdirectory and port numbers) can be accomplished if everything's locked in the Docker black box.

[LPS-github]

I realize this is an old request, but I find myself in the same situation. My only access to self-hosting is by using #Yunhost which thankfully makes it accessible to people with less technical expertise https://yunohost.org/#/

Is there any chance that you could look in to packaging it as an app there? It has become such a popular platform that I'm sure it would greatly increase the project's adoption https://yunohost.org/ar/packaging_apps_intro

[Flamekebab]

At the moment, it doesn't seem possible without familiarity with the underlying frameworks. There are several free hosting services which support Docker if you're just looking to try it out!

I honestly (and respectfully) don't understand how we got here. I (and I assume many) know how to set up a web-server, a database, deploy a framework. I have a VPS where I run a bunch of things and I don't want to containerize all the tools I install. I think this is a very bad direction, that some developers only provide docker images. A short but focused wiki could describe install instructions. Going always a "level higher" is really not what we should do.

I'm running up against this too. I've messed about with Django and can debug that but I've never touched NodeJS and looking at the minimal instructions on https://docs.getpinry.com/development/ I'm not able to decipher how Pinry 2.x fits together. Running the Django server doesn't have a root URL for some reason, although things like /admin work. All the unit tests pass so nothing is obviously broken.

It looks like whatever the NodeJS code is for has to run in a separate process and it's bafflingly inconsistent (it runs just fine in one tab I have open and stubbornly errors out in all the others - no idea why, I'm even less familiar with Yarn than I am with NodeJS). I'm sure it all makes sense if one has all the knowledge of all the components already. I don't though and the documentation isn't helping in the slightest.

Whilst I'm sure running everything in Docker is convenient for some use cases I really don't want to have to fiddle about with reverse proxies and containerize all the different things on my server to shift to that. Django doesn't need to run that way at all so it's hardly fundamental to the concept.

[lapo-luchini]

I am using it without Docker (in a FreeBSD jail).
I don't really remember the exact procedure I used (I might try it again and document it) but I have a local patch because the old sass native implementation doesn't work on FreeBSD:

diff --git a/pinry-spa/package.json b/pinry-spa/package.json
index 75348ab..241ad5e 100644
--- a/pinry-spa/package.json
+++ b/pinry-spa/package.json
@@ -12,6 +12,7 @@
     "buefy": "^0.8.20",
     "core-js": "^3.3.2",
     "register-service-worker": "^1.6.2",
+    "sass": "^1.55.0",
     "vue": "^2.6.10",
     "vue-i18n": "8",
     "vue-masonry": "^0.11.8",